The problem:

Clarity now uses single sign-on through Auth0, so staff sign in with their email address. The Username field on Staff Accounts is no longer used to log in, but it's still required and must be unique. System administrators across organizations still have to make up and type a unique username every time they create a staff account.

For most organizations, the username shows up in only a few reports and doesn't affect end users. Admins still spend time making up and tracking a value that's rarely used. The cost adds up for organizations that create many accounts, onboard staff often, or manage large networks of agencies.

What organizations are asking for:

Organizations would like Clarity to stop requiring admins to enter a Username by hand when they create a Staff Account. Any of these would meet the need:

-Fill in the Username automatically from the staff member's email address, adding a number if that name is already taken. For example, jdoe@agency.org would become jdoeagencyorg.

-Hide the Username field on the Staff Account form, or make it optional for admins, while the system keeps a value in the background.

-Show a more useful field in reports that currently display the Username (such as the staff member's email or full name), so admins don't need to keep up a separate ID.

Who benefits:

-System administrators at any organization that creates or manages Staff Accounts

-Large or multi-agency organizations that manage many staff accounts

-Organizations with frequent onboarding or staff turnover

Impact:

-Faster, simpler staff account setup across organizations

-Fewer errors and less confusion from making up usernames by hand

-Consistent with the email-based sign-in that Clarity already uses