Teams and roles

Data is organised in three levels: the platform, organisations (a client company), and accounts inside an organisation (for example one per country or brand). All data lives in an account.

Roles inside an account

Role	Can do
Admin	Everything in the account: settings, team, connecting a store, all data
Editor	Create and edit contacts, campaigns, segments and imports
Viewer	Read contacts, segments and analytics, and change nothing

An organisation owner can reach every account in the organisation and manage the organisation itself.

Platform operators

The people who run the platform itself have a separate console, Platform Administration, for work that spans every organisation. It appears in the account switcher only for platform operators, and is also served on its own admin. address. Anyone else who opens it sees a message that it is for platform operators. Organisation owners manage their own organisation under Organisation Management, not here.

Under Organisations an operator can:

• Create an organisation. You name it and its first owner; the owner is emailed an invitation, and the organisation starts with one account named after it.
• Suspend an organisation. Everyone in it, including its API keys, is turned away from their next request with a message that the organisation is suspended, until you Restore it. Nothing is deleted.
• Impersonate an account: open any account of an organisation that is not suspended, as yourself, for a few minutes. A banner on every page says so and has a Stop impersonating button. Impersonating is available from the main app's Platform Administration, not from the admin. address.

Under Platform settings an operator can:

• Turn maintenance mode on or off. While it is on, everyone except platform operators is turned away with a "down for maintenance" message, API keys and connectors included, and your optional note is shown with it. Operators can still sign in and use the console. Health checks, contact-facing pages such as unsubscribe links, and incoming store webhooks keep working. People who are turned away are not signed out: they can carry on once you turn it off. The switch asks you to confirm before it turns on.
• Turn a feature on or off for everyone, such as the MCP server. A global flag applies to every account that has no setting of its own.
• Set a feature for one account on its organisation's Accounts page. An account's own setting wins over the global flag, so Off keeps a feature off while it is on for everyone else, and Follow the global flag removes the account's own setting.

Every one of these is written to the platform audit log, and what you change in an account while impersonating is marked in that account's activity as done by a platform operator. Under Users an operator can search everyone on the platform, across organisations, by name or email, and filter by status. Each row shows the person's organisations and whether they are an owner or still invited. From a row you can:

• Force reset: end every session the person has and email them a link to choose a new password. Their current password keeps working until they do. Not offered to someone who has not set a password yet, and not on yourself.
• Deactivate: sign the person out everywhere and turn them away from their next request, API keys included, in every organisation. Nothing is deleted. You cannot deactivate yourself or another platform operator.
• Reactivate: let a deactivated person sign in again with their current password.

Each asks you to confirm first. Every one of these is written to the platform audit log, and what you change in an account while impersonating is marked in that account's activity as done by a platform operator.

Inviting people

An organisation owner invites people under Organisation Management → Users (open it from the account switcher at the top of the menu). Enter the person's email address and full name and press Send invitation. The link is valid for 72 hours, and Resend sends a new one. The person sets a password on opening it.

An invitation makes someone a member of the organisation, not of an account. On the same page, pick an account and a role (Admin, Editor or Viewer) next to their name and press Assign, or Change role later, otherwise they sign in to an empty app.

Switching account

Use the account switcher at the top of the menu. Each account is a separate set of contacts, campaigns, senders and store connections.

Quotas

An organisation has allowances, such as the trial email pool, shared by all of its accounts. When an allowance is nearly used, owners get an email warning.

API keys

An Admin creates API keys under Settings → API Keys. A key has a scope, read, write or admin, and acts as a Viewer, Editor or Admin respectively. The secret is shown once, when the key is created. Some actions, such as managing templates, webhooks or the store connection, are closed to keys and need a signed-in person. The API itself is described in API and webhooks.

If you cannot sign in

After ten wrong passwords for the same email address within fifteen minutes, Shoovoo stops accepting sign-ins for that address and tells you how long to wait; even the right password is refused until the wait is over. Use Forgot password on the sign-in page if you do not remember it, which is not affected.