Team and roles
A workspace can be shared. Everyone in it works on the same accounts, posts and credits; a role decides who can also manage money, accounts, keys and people.
Roles
| Member | Admin | Owner | |
|---|---|---|---|
| Create, schedule and publish posts; dub, lip sync, clips, automations (uses the workspace's credits) | Yes | Yes | Yes |
| Choose a plan, buy credits, automatic top-up, billing | No | Yes | Yes |
| Connect or remove social accounts | No | Yes | Yes |
| Create and revoke API keys | No | Yes | Yes |
| Invite people, change roles, remove members | No | Yes | Yes |
| Change or remove an owner, make someone an owner | No | No | Yes |
A workspace always keeps at least one owner: the last owner can't leave, be removed or step down until someone else is an owner. Anyone else can leave from the Team page.
Invite someone
- In the console, open Team, enter the person's email and choose Member or Admin.
- Copy the invitation link and send it to them yourself (chat, email, however you like). Fifty Eight does not email it for you.
- They open the link, sign in or create an account with that email address, and join. The workspace then appears in their workspace switcher.
- A link works once, for 7 days, and only for the invited email address.
- The link is shown only when it is created. Inviting the same email again makes a new link and the previous one stops working.
- Pending invitations can be revoked at any time from the Team page.
- An invitation never makes someone an owner; an owner can promote a member afterwards.
API keys and the team
The team is managed in the console only. An API key belongs to the workspace, not to a person: it can do what the API offers (publish, dub, read credits...), but it can't invite, remove or change anyone. Those calls answer 403. GET /v1/workspace returns the role of the caller.
Removing someone does not revoke the API keys they created, since keys act for the workspace. If a person who leaves had a key on their machine, revoke it in API & MCP.