Coalesce users can be created and managed directly in Coalesce, or via your single-sign on (SSO) provider.
- 📧 Email as Unique Username. In Coalesce, a user's email serves as their username. A single email cannot be active across multiple Coalesce accounts. If you need a single email address to access multiple Coalesce accounts, you will need to use plus addressing (also known as subaddressing); for example, email@example.com and firstname.lastname@example.org both route and can successfully send emails to email@example.com.
- ✌️ Multiple User Records. A single email may end up with multiple active user records, each with a unique User ID, within a given Coalesce account if the user has been configured both directly in Coalesce as well as with your SSO provider. In these instances, the user will be able to authenticate via both SSO as well as via username/password-based authentication. If you do not wish to allow username/password-based authentication, you will need to disable and/or delete the Coalesce native User records. The User ID can be used to identify SSO records vs. native Coalesce records, as the SSO records will be prefixed with your SSO provider name.
- 📖 Read-Only Users. You are able to add an unlimited number of Read-Only users in your Coalesce organization. Read-Only users can access the project documentation auto-generated by Coalesce, but cannot develop within the platform. For more information, see our FAQ: How do I create a Read-Only User in my Coalesce organization?
- 🔄 Regular User Record Review. It is a good practice to regularly review your User records to ensure user roles are correctly configured and that users that need to be deprovisioned are disabled and/or deleted.