Accounts
An account is the business that pays. Workspaces sit inside it. Agents, phone numbers, calls, campaigns, contacts, and connections belong to a workspace. The wallet, plan, invoices, payment methods, and account members belong to the account.
Signing up creates an account, its primary workspace, and an Owner membership for you. The account id is that primary workspace's id. The account holds the wallet, the plan and the free monthly credit, and every workspace in it draws on them. You can own at most 20 accounts. An account can hold at most 100 workspaces.
One login can belong to several accounts. In a workspace, your effective role is the higher of your workspace role and the role your account role implies. Owner and Admin are Admin in every workspace of the account. Billing implies no workspace role. If you are Billing on the account and Viewer in one workspace, you are Viewer there.
See Workspaces for switching, and the accounts API for the routes.
Account roles
| Role | You can |
|---|---|
owner | Rename the account, invite Owners, Admins, and Billing, delete an empty workspace, and manage payment methods and top-ups in Studio. |
admin | Create workspaces, manage account members except Owners, manage account keys, and act as Admin in every workspace. Payment methods, top-ups, and deleting a workspace stay with the Owner. |
billing | Open the balance, top-ups, payment methods, invoices, and spend alerts. You have no workspace access unless someone also gives you a workspace role. |
Account settings live at /account. Owner and Admin see General, Members, Workspaces, Billing, API keys, and Usage. Billing sees Billing and Usage.
Workspace roles
A workspace Admin, or an account Owner or Admin, invites people to one workspace. The role on the invite is admin, editor, client, or viewer. The API default is client.
| Role | You can |
|---|---|
admin | Run the workspace: agents, numbers, connections, campaigns, contacts, knowledge, compliance, webhooks, workspace keys, and invites. Billing stays on the account. |
editor | Build and test agents, campaigns, contacts, and knowledge, and use connections that are already there. Buying numbers, adding connections, managing webhooks, inviting people, and creating keys are closed. |
client | See calls, recordings, transcripts, and the dashboard. Edit knowledge, an agent's transfer number, contacts, the do-not-call list, and compliance settings. |
viewer | Read the dashboard, calls, recordings, transcripts, and usage. |
Client and Viewer receive minutes. Credits, revenue, cost, and margin are omitted from their responses, including GET /v1/analytics/spend and GET /v1/workspaces/:id/usage. Studio hides the money cards for those roles.
In a workspace where your role is Client or Viewer, Studio shows: "You're viewing {workspace}, managed by {account}."
A request your role cannot make returns 403 with code role_forbidden. That response does not sign you out of Studio. A 401 does.
Add a workspace
- Open the workspace switcher, or
/workspaces. - Click New workspace. You need to be Owner or Admin of that account.
- Type a name, up to 80 characters, and create it.
The new workspace lands in the current account. Its calls draw on the account wallet. On the API, POST /v1/workspaces does the same. parent is still accepted for one release: it must name a workspace in that account, and it selects the account. See Create a workspace.
Invite someone
- For the account, open Account settings → Members and choose Owner, Admin, or Billing.
- For one workspace, open Settings → Members and choose Admin, Editor, Client, or Viewer.
An Admin cannot add, change, or remove an Owner. The last Owner stays: the API returns 400 last_owner. Only an Owner can delete a workspace, and the primary workspace returns 400 cannot_delete_primary.
Someone without a Rymi account gets an email to set up their sign-in. Someone who already has an account gets no email. Tell them to open Studio: the account or workspace shows up in the switcher.
Notification email for a workspace goes to that account's first Owner.
Money
Top up, payment methods, and the billing country are Studio actions under Account → Billing. A secret key cannot call those writes. See API keys and scopes.