Roles and single sign-on
There are no per-person roles yet: everyone who signs in to an account can do everything that account can do. You control access three ways: how people sign in, which workspace a key belongs to, and which scopes each key carries.
Sign in to the shared service
| Method | How it works |
|---|---|
| Continue with Google on the sign-in page. | |
| Enter your email, then the code we send it: 8 digits to sign in, or 6 to confirm a new account. | |
| Email and password | A site with emailed codes turned off asks for a password instead, with Forgot password? to reset it. Where the sign-in requires an authenticator app, you enter its code after the password; the first time, the page shows the key to add to the app. |
A wrong password reads "Incorrect email or password." Too many tries in a row lock sign-in for a few minutes, which reads "Too many attempts. Wait a few minutes, then try again." (after a password, "Too many attempts. Wait a few minutes, or reset your password.").
Signing in to the Platform does not authenticate API calls: every integration needs its own API key. See Auth and scopes. Signing out revokes the session's refresh token, so that session cannot be renewed.
Linked sign-ins
A linked sign-in opens the same account as your main one, with the same keys, data and plan. Today you can link a school email: Settings, Linked sign-ins, Add a school email. A linked sign-in can unlink only itself; the main sign-in can unlink any of them.
Linking, unlinking and deleting a sign-in change who can open the account, so each needs a sign-in from the last 10 minutes. Settings asks you to confirm yours when it is older.
Company sign-in on Enterprise
An Enterprise deployment has its own Platform site and its own sign-in. People enter the company's code name, then either choose Continue with your company's sign-in, one button for each identity provider Constellation has connected to your site, or enter the shared team password.
- There is no sign-up, password reset or emailed code. Your Constellation contact sets up access and connects your identity provider.
- Everyone who signs in, by either route, works in one shared account: the same keys, data and plan. The deployment owns its keys, so anyone signed in can create and revoke any of them.
- Repeated wrong team passwords lock sign-in for a while.
See Constellation for Enterprise for the first sign-in.
What controls access
| Control | What it decides | Where you set it |
|---|---|---|
| Account | Keys, data, plan and billing. On the shared service each main sign-in has its own account; an Enterprise deployment is one account. | Sign-in |
| Workspace | Keys and data. A key works only in the workspace it was made in; usage and billing are shared across the account. | The workspace switcher in the account menu, and Settings, Workspaces |
| Key scopes | What each key may call, such as telemetry:write, workflows:write or act:approve. See Scopes. | Integrations, API and MCP |
| Plan | What the account may use, such as sending recommendations to your mission control system (MCS). | Settings, Billing |
Every account starts with one workspace. Add another in Settings, Workspaces, with + New workspace.
The Platform acts with a short-lived session made from your sign-in, scoped to the workspace you are in, so a person signed in to the account can read, run and approve without a key of their own. A disabled account gets no session. See Deciding one.
Until roles exist
Team members, invitations and per-person roles are not available yet. Until they are:
- Give each integration its own key with only the scopes it needs, and revoke it on its own when it is retired. Each key shows when it was last used.
- Keep
act:approveoff keys that only read or write data. - Put work that needs its own keys and data in its own workspace.
- On Enterprise, ask your Constellation contact to remove access for someone who leaves, and rotate the team password and any keys they held.
See The audit log for what is recorded about who changed what.