A workspace owns everything you build: agents, tools, phone numbers, provider keys, secrets, calls and credit. The dashboard calls it your organization. Your first sign-in creates one for you; you can belong to several and switch between them. Workspaces, members and invites are managed in the dashboard (Organization → Settings → General) and are not part of the published API, SDKs or MCP server.

​
What each role can do

Membership and role are re-read on every request, so a change takes effect on that person’s next call, including through every personal access token they already hold. A write by a VIEWER answers 403 your role is view-only — ask an organization admin for editor access. An admin-only action by an EDITOR answers 403 only an organization admin can do this. A VIEWER cannot start a test call. A call token can carry a whole inline agent run on the workspace’s provider keys, so it needs EDITOR; the agent editor’s test panel is disabled for a VIEWER. The EDITOR/ADMIN line is credentials and money. An EDITOR can write {{secrets.NAME}} in a tool but cannot create, read or delete the secret, store a provider key, or buy credit. See secrets and provider keys.

​
Inviting someone

An ADMIN invites an email address with a role under Organization → Settings → General.
No email is sent, and there is no invite link or accept step. Signing in with Google as that address is the acceptance. Tell the person yourself.
  • The address already has a Talqing account: they are added immediately with the role you chose and see the workspace in their switcher.
  • It does not: the invite waits, and they join with that role on their first Google sign-in.
Pending invites are listed until accepted; withdrawing one stops that address from joining. Inviting an existing member (… is already a member of this organization (EDITOR)) or an address with a pending invite (… has already been invited) is refused with 400.

​
Changing a role and removing someone

Only an ADMIN can change a role or remove a member. Removal ends access on their next request and deletes their personal access tokens for this workspace. Nothing they built is deleted; agents, tools and calls belong to the workspace. You cannot remove yourself; you leave instead, and any member may leave.

​
The two invariants

Both are refused with 400: An ADMIN can still remove someone whose only workspace this is; their next sign-in creates them a new one.

​
Creating and switching workspaces

Any member can create another workspace, named 1–100 characters, and becomes its ADMIN. A workspace you create yourself starts with $0 credit; the signup grant applies only to the workspace created at your first sign-in. The switcher lists your workspaces newest membership first, so one an admin added you to without asking is at the top. Switching re-issues your session, so the dashboard reloads.

​
Workspace settings

ADMIN only, under Organization → Settings → General. Omitted fields are left unchanged.

​
Next

Authentication

Tokens, the Bearer header, and 401 versus 403.

Data retention and privacy

What a retention purge deletes and what survives.