StatusDashboard

User Accounts

Invite teammates and manage roles for your organization.

View Markdown

User accounts control who can sign in to your organization and what they can do in the admin console. Manage members from Users. Each person holds one or more roles (Admin, Event, Subscriber) that determine access to events, status dashboards, subscribers, billing, and security settings.

Only organization admins can invite, edit, and remove users. The sections below cover the invite flow, role assignment, password and SSO sign-in options, and account lifecycle actions.


Inviting users

Every person who accesses your StatusDashboard organization has a user account. Accounts are tied to your organization (tenant) and carry one or more roles that determine what that person can do.

Only admins can invite new users. To invite someone:

  1. Go to Users.
  2. Click Invite user.
  3. Enter their email address and select one or more roles (Admin, Event, and/or Subscriber).
  4. Toggle Allow password login to control how this user can sign in.
    • On (default): the user can sign in with an email address and password. An invitation email with a temporary password is sent unless you uncheck Send invitation email.
    • Off: the user must sign in with Google or a configured SSO provider. No temporary password is created and no invitation email is sent. If the user does not complete the Google or SSO sign-in flow, they will have no way to access their account — disable password login only when you are confident the user has a working alternative sign-in path. See Break Glass Access for guidance on maintaining emergency access.
  5. If Allow password login is on, you can uncheck Send invitation email to create the account silently — the user won't receive any email until you're ready. This option is hidden when password login is off.
  6. Click Invite.

StatusDashboard creates the account immediately. If Send invitation email is checked (the default when password login is on), the user also receives a temporary password by email and will be prompted to choose a permanent password on first sign-in.

What happens after the invite email

The invited user receives an email from StatusDashboard with a temporary password and a link to the login page. They sign in with their email address and that temporary password, then choose a permanent password on first sign-in. Temporary passwords expire — if the user does not log in promptly, an admin can resend or reset their access by deleting and re-inviting them.

If Send invitation email was unchecked, no email is sent and the user cannot log in with a password until an admin deletes and re-invites them with the option checked.

Editing users

Admins can edit any user's role or password login setting at any time from the Users list. Click the edit icon on any row to open the edit form.

Role and access changes take effect immediately. If a user's roles are reduced or their account is disabled, their current session is ended and they must sign in again to continue.

At least one admin is required. Every organization must have at least one user with the admin role at all times. If you try to remove the admin role from the only remaining admin, the save will be rejected with an error. Assign the admin role to another user first, then demote the original admin.

Disabling users

Admins can temporarily block a user from signing in without deleting their account. On the edit form, use the Account enabled toggle in the Account access section.

When a user is disabled:

  • They cannot sign in by any method (password, Google, or SSO).
  • Their roles, history, and organization data are preserved.
  • They still count toward your seat limit — disabling does not free a seat.
  • Their active session ends immediately — they are signed out and cannot call the API with an existing token.

You cannot disable your own account. The only admin in an organization cannot be disabled — assign another admin first.

To restore access, open the edit form, turn Account enabled back on, and save.

Removing a user (see below) is permanent and frees their seat. Disabling is reversible and keeps the account intact.

Email addresses

Each user's email address is their sign-in identity and cannot be changed after the account is created. This applies to password, Google, and SSO sign-in alike.

If someone needs to use a different email:

  1. Go to Users.
  2. Remove the user at their current address (see Removing users below).
  3. Invite them again using the new email address, with the same roles and sign-in options they had before.

The new invite creates a fresh account at the new address. The person will sign in with the new email going forward.

What to expect

  • Roles and access — Set these again on the new invite; they are not copied automatically from the old account.
  • API keys — Any keys the user created are revoked when their old account is removed. They must create new keys after signing in with the new address.
  • Sign-in history — Activity tied to the old email stays in your organization's history; new activity appears under the new address.
  • SSO users — If the person signs in through your company's identity provider, their login email is usually managed there first. If their IdP email already matches what you need, you may not need to remove and re-invite them on StatusDashboard.

Typo at invite time? If you invited someone to the wrong address before they ever signed in, remove that account and send a new invite to the correct email — no support ticket required.

You cannot change your own email from the admin console. If you are the only admin and need a different address, assign another admin first, then remove and re-invite yourself — or reach out to support.

Removing users

To remove a user:

  1. Go to Users.
  2. Click the delete (trash) icon on the user's row.
  3. Confirm the deletion in the dialog.

Removal is permanent. The user's StatusDashboard account is deleted and they will no longer be able to sign in. Their historical activity data (referrals, etc.) is retained at the organization level. If you need to restore access, re-invite them as a new user.

You cannot delete your own account from the admin console. Reach out to support if you need to remove the account you are currently signed in with.

The last admin cannot be removed. If the user you are trying to delete is the only admin in the organization, the deletion will be rejected. Assign the admin role to another user before removing them.

Seat limits

Your account includes a maximum number of user seats. The current count is shown on the Users page beneath the heading.

ConditionDisplay
Below the seat limitShown in gray — no action needed
At or over the seat limitShown in red — the Invite button is disabled

When you reach your seat limit, the Invite user button is disabled and no new users can be added. To increase your seat limit, visit the Billing page or reach out to support.

Deleting a user immediately frees their seat, making it available for a new invite.

Product email list

When you create or join a StatusDashboard account, your email address is added to our product mailing list. We use this list to announce important new features, improvements, and bug fixes. You can unsubscribe at any time using the link at the bottom of any email we send.

Frequently asked questions

Can I change a user's email address? No — see Email addresses above for the remove-and-re-invite process.

Can a user belong to multiple roles at once? Yes, technically. A user can hold both admin and event simultaneously. The effective permissions are the union of all assigned roles.

What happens to a user's API keys when they are deleted? API keys are user-scoped, not organization-scoped. When a user is deleted, all of their API keys are automatically revoked as part of the deletion process. The next API request with a revoked key returns 403 Forbidden.

Can I see when a user last signed in? Yes. The Users table shows a Last Login column for every member. This timestamp is recorded for all login methods so it is always accurate regardless of how the user authenticates.

On this page

We use cookies

We use essential cookies to keep the site working, and optional analytics cookies to understand how it's used. Read our Privacy Policy.