Invite your team
Staff accounts in UpAll come in two roles: Admin and Engineer. Admins can do everything, including managing the team, billing, and workspace settings; Engineers do the day-to-day monitoring work without any of those.
Admin vs Engineer
| Area | Admin | Engineer |
|---|---|---|
| Day-to-day work — monitors, incidents, clients, sites | Yes | Yes |
| Team management and invites | Yes | No |
| Billing and plan changes | Yes | No |
| Workspace settings and branding | Yes | No |
Both roles receive every alert email: UpAll emails all active staff when any incident opens or resolves, each person in their own language, and there is no per-monitor recipient routing — worth knowing before you invite the whole company. See Email alerts.
The practical rule: give Admin only to people who genuinely need to touch billing or settings, and Engineer to everyone else. Fewer Admins means fewer accounts that can change what clients see.
Two ways to add staff
Directly — you create the account yourself with a name, email, role, password, and language. Fastest when you're onboarding someone in the same room. The language you pick sets their console language and the language their alert emails arrive in; they can change it themselves at any time — see Switch language and theme.
With an invite link — you generate a link that carries a preset role, can optionally be locked to one email address, and expires after 7 days. The person opens it and creates their own account, so no passwords change hands. Lock the link to an email whenever you're sending it over a channel you don't fully control.
Note that these are staff invites for the console. Client users — your customers' read-only portal accounts — are invited through a separate flow on the client's page; see Inviting client users.
Deactivating staff
When someone leaves, deactivate their account: they can no longer sign in, and alert emails stop going to them immediately.
The last-admin protection
A workspace must always keep at least one active Admin — otherwise nobody could ever manage the team, billing, or settings again. The console therefore refuses any action that would remove the last one: you can't deactivate the final active Admin or strip their role until another Admin exists. If that person is you and you're leaving, promote your successor first.
Same person, several workspaces
An account belongs to exactly one workspace, but the same email address can exist in several. At sign-in, the person picks which workspace to enter, and can move between them afterwards. See Workspaces and multiple accounts.