Skip to main content

Updating Email Domains for Internal Users

The process of managing team members and updating email domains in Vitally, whether you use Single Sign-On (SSO) or not.

Written by Ethan Patrick

Updating Email Domains and Managing Team Members in Vitally

Inviting Team Members and Auto-Created Users

  • Missing "Invite a Teammate" Button?
    If the option to invite a new team member is missing, SSO is enabled. Team members can only be added via the SSO provider.

  • Invitation Expiry
    When a new team member is invited, the invite link expires after a certain period. If they don't accept it in time, an admin must resend the invitation.

  • Auto-Created Users
    Vitally may automatically create team members due to Key Role trait mapping. If an email address in the mapping doesn't belong to an existing Vitally user, a placeholder account is created. If the person is later invited, this placeholder is converted into an active user, transferring all associated data (accounts, tasks, projects, etc.).


Updating a Team Member's Name or Email

Admins can update a team member's name or email address directly from Settings > Team Members > Manage.

To update a name: Hover over the name and click the pencil icon to edit it, the same way trait cells are editable.

To update an email address: Click the email field. A confirmation modal appears before the change is saved.

  • If SAML SSO is not enabled: a warning advises you to notify the team member of the change, as it may affect their ability to log in.

  • If SAML SSO is enabled: a stronger warning indicates that if the email is not also updated in your identity provider, the team member will lose access to Vitally. The confirm button is styled as a destructive action.

If the email you enter is already in use by another Vitally user, an error is shown inline.

Edit a Team Member's name by hovering over the name and clicking the Edit pencil

Note: Integrations that use email for matching (such as Salesforce) will reflect the updated email. Because emails must be unique in both systems, duplicate conflicts are unlikely but worth verifying after making the change.

Did this answer your question?