Getting started
Inviting team members
Create a user from Users & Access, send the built-in email invitation, and give the new account an appropriate starting role. Use the labels and controls described below to complete this workflow in the current TankActive web app.
Published Last updated
How do I open the user directory?
Open Admin, then select Users & access. The page lists each user's name, email, Access, Groups, and Status. You need user management access to create a user; read-only access can show the directory without enabling Add User. The demo organization also disables edits.
Before creating a duplicate, use Search name or email and the Active or Inactive filters to check whether the person already has an account.
How do I add the team member?
- 1Select Add User.
- 2Enter the required First Name and Last Name.
- 3Enter the required Email address. TankActive validates the email format and reports when an account already uses that address.
- 4Choose a Starting role if you also have permission to manage roles. The list contains the organization-wide roles the current administrator is allowed to grant. You may select No role yet — assign later, but that user will not have product visibility until access is assigned.
- 5Select Create & open.
What happens to the invitation and starting access?
TankActive creates the user and sends the built-in email invitation. After creation, the new user's access panel opens when the refreshed directory returns the account. If the invitation service reports a failure, refresh the user list before retrying so you do not create the same account twice.
When a Starting role is selected, TankActive attempts to assign that organization-wide role after the user is created. If role assignment fails, the user still exists and the page reports that the starting role could not be assigned. Open that user's panel and add the role separately after confirming your permission to grant it.
How do I refine access after creation?
Use the opened user panel to review Roles, Groups, and Permission overrides. Starting roles are intentionally broad at the organization level; if the person should work only with a particular Group or Location, replace or supplement the starting access with the smallest role and scope that covers the job.
An account can be Active while still having no role. The directory explicitly marks that state as No role, and the panel explains that the user cannot see anything yet. Finish the access assignment before asking the person to sign in.
Which help articles are related?
Continue with the product workflows most closely connected to this task.