How do you use Chosen vs Legal Names for Team Members in Square?

[lbicheese]

The title of this thread has been edited by a Square Moderator from the original: "Chosen vs legal names"

I have requested this as a new feature but would like to know from other owners how they have handled chosen names vs legal names of transgender employees.  

It would be good to have the ability to enter a chosen name and have that shown as the name in the different team-facing applications and would make it a lot easier for transgender employees to establish themselves under their new names.  This is such a simple and basic adjustment to the software that it should have already been there but since it is not, how have you handled that situation?

[MJD]

I agree this is an incredibly important feature!

Hopefully this can be shared with the product team and they can consider introducing it to the software.

One thing I would suggest here from a developer's perspective is no matter how simple something seems to the user there can be thousands of lines of code put into it to make sure it works as intended so do be patient, but I do completely agree that this feature should be made available!

[PartyManiaMD]

I know it's off topic but I totally get how difficult coding is. I used to have a software company and even rolling out one thing was insanely difficult, especially in today's world where the software has to work on a million different phones, tablets, laptops, desktops,etc.  I remember having 30-40 phones just to check that the software updates played nice on mobile.  That said I'm sure some of their code is modular in case they need another field.

Certain things I'm sure would be a painful experience for their team to code, but adding a preferred name and stuff like cost per case for items fields shouldn't be too hard.

[Thevioletfox]

Just chiming in to say I agree as well and lend my vote to this! A person's dead name can trigger all kinds of nasty things so the less it has to be used, the better! 

[Donnie-M]

@lbicheese I would use the team member ID under the employee information to record the person's legal/given name.  This information will be easily accessible on labor reports you export.  It is a handy feature for internal reporting and coding.  Avoiding the entire inclusivity/political part of this, people have used given/nick names ever since I could remember.  The only problem comes with payroll and legal reporting (IRS, taxes, garnishments, etc.), but it shouldn't be a problem with your payroll provider to map these.

I don't go by my government name  in day to day business, but you can use the team member ID field for letters not just numbers.  So this should effectively solve the problem for you, until a more elegant solution could be implemented.  Everything in the system will show the name you put for the employee but you will still have the legal name associated with the person.

[lbicheese]

Thank you, Are you able to make the user ID's the default that other team members see when they look at the schedule in the team app?

[Donnie-M]

@lbicheese I don't think so, you would want to use the name field for the name the team member wants to show on schedule and the register and the id would be for internal use only so to speak.

[lbicheese]

Thank you