Organisations and members
Who can see and do what in the console. Admins and members, invites, and what happens when someone is removed.
Everything in the console belongs to an organisation: its API keys, usage, limits, wallet, invoices, tax profile and members. API keys belong to your organisation; there are no sub-groups inside it. You can belong to up to 10 organisations and switch between them from the account menu at the top left. Nothing is shared between organisations.
Inviting people
Admins invite people from Members by email, as a Member or as an Admin. The invite link is valid for 7 days and works only for a verified account with the invited email address. Inviting an address that already has a pending invite sends it again with a fresh 7 days and the role you picked now. Invites older than 7 days expire and drop off the list; inviting that address again sends a new invite. Admins can cancel a pending invite.
Roles and permissions
There are two roles: Admin and Member. The person who creates an organisation is its admin. An organisation can have several admins, and every admin has the same powers; there is always at least one.
Admin means your organisation's admin
An organisation Admin manages your organisation in the console. Admins are your own people, not Sieve staff.
| Area | Admin | Member |
|---|---|---|
| Home (usage dashboard and setup steps) | Balance and low-balance hint, usage, all setup steps | Usage; no balance, no "Add credits" or "Invite your team" step |
| Playground | Yes | Yes |
| API keys: personal keys | Creates own; sees, rotates and revokes everyone's keys in the organisation | Creates own; sees, rotates and revokes only their own |
| API keys: service accounts | Creates, sees, rotates and revokes | Can't create, see or change them |
| Revoke all keys | Yes (Organisation settings) | No |
| Usage on Home and CSV export | Whole organisation; breakdown by every API key | Whole organisation; key breakdown lists only their own keys and the playground |
| Limits: view, request an increase | Yes | Yes |
| Assurance | Yes | Yes |
| Foundry: view datasets, jobs and deployed models | Yes | Yes |
| Foundry: upload datasets, train, deploy and revoke | Yes | No |
| Contracts and licences | Yes | No |
| Billing: wallet, top-ups, history, invoices | Yes | No |
| Tax profile (GSTIN / VAT, billing address) | Yes | No |
| Organisation settings (name, legal entity, max key lifetime) | Yes | No |
| Members: list, invite (as Member or Admin), cancel invites, remove | Yes, including other admins | No |
| Leave the organisation | Yes, while another admin remains | Yes |
| Change a role (make admin / make member) | Yes, including their own while another admin remains | No |
| Support tickets | Opens tickets; sees every ticket in the organisation | Opens tickets; sees only their own |
| Account and security (password, 2FA, passkeys, sessions) | Own account | Own account |
| Notifications (bell, email preferences) | Own notifications | Own notifications |
| Create another organisation | Yes (becomes its admin) | Yes (becomes its admin) |
These rules are enforced on the server, not only by hiding buttons. If a member opens an admin-only page directly (for example /settings/billing), the console takes them to Home with an "Only admins can …" notice. An admin-only action called by a member is refused with "Only admins can do this. Ask an admin of your organisation."
Changing roles
Admins can make a member an admin, or an admin a member, from Members (each change asks you to confirm). The last admin can't be made a member: make someone else an admin first. A former admin keeps their keys, but from then on sees only their own personal keys.
Removing someone
An admin can remove any other member or admin from Members. You can't remove yourself; to go, use Leave organisation under Account & security. Members can always leave; an admin can leave only while another admin remains. Removals, leaving and role changes are checked together, so an organisation always keeps at least one admin.
- Whether removed or leaving, the person loses access to the organisation straight away.
- Their personal keys in that organisation are revoked, including keys an admin rotated for them.
- Service-account keys keep working, whoever created them.
- If it was their only organisation, they are taken to "Let's create your org" the next time they open the console.
To hand an organisation over, make the new person an admin and then make yourself a member. To delete an organisation, write to support@sthanika.ai.
Next steps
Last updated