Team access
Not everyone on the sales team should hold the workspace API key. Klozeo seats let you invite colleagues to the dashboard with a clear role, while n8n, SDKs, and scripts keep working exactly as before.
Invitations
Section titled “Invitations”The owner or an admin invites people from Dashboard → Team: enter their email, pick a role, and send. The owner can pick Admin, Editor or Viewer. An admin can pick Editor or Viewer: only the owner can invite an admin. The invitee receives an email with a link to accept, and the email names the person who invited them.
If you do not have an account, the invitation takes you to sign in or create one when sign-ups are open. After you verify your email, the invitation opens again by itself: accept it there. During a sign-up pause, invitations do not bypass the pause: existing accounts can still sign in and accept.
Invitation links expire after 7 days. Only the invited email address can accept a link, and each link can be used once. Removing an invitation or member revokes access. The owner can remove any member. An admin can remove editors and viewers and cancel their invitations, but not another admin. Removing a member also cuts their assistants’ access to that workspace (Claude, ChatGPT and other MCP clients), whether the owner or an admin removes them. Removing a member or an invitation asks for confirmation first. A revoked link cannot be reused.
Free has one user: inviting members requires Pro or Scale, including during the 14-day Pro trial. On Free, an admin has a viewer’s rights and cannot manage the team. Anti-abuse limits are 25 members for Pro and 100 for Scale (active members plus unexpired pending invitations, excluding the owner), and 20 invitation sends per workspace over 24 hours, whoever sends them. These limits belong to the workspace: an admin’s invitations count against them like the owner’s. Separate network and recipient email limits may return 429 with Retry-After. Revoking an invitation frees a member slot, but does not reset the email budget. Exceeding a limit returns 403 with an explicit error. Seats remain included in the plan price.
When a workspace moves to Free (end of the trial or of its subscription), nobody is removed: members keep read-only access, whatever their role, and pending invitations can still be accepted as read-only. When the owner subscribes to Pro or Scale, each member gets their role back.
The permissions below remain subject to the workspace’s plan and read-only state.
| Role | Dashboard & API | Typical use |
|---|---|---|
| Owner | Full access, including the team, billing and the account export | Founder or manager who owns the workspace |
| Admin | Everything an editor can do, plus API keys, webhooks, batch deletion, global score recalculation, and inviting and managing editors and viewers. Not admins, billing, the account export, ownership transfer or workspace deletion. Sees leads only when the owner gives access | Consultant or agency who wires the workspace’s automations |
| Editor | Can create, update, and delete individual leads and related data; batch create/update allowed | Ops, SDRs, enrichment workflows via the UI |
| Viewer | Read-only: any mutation returns 403 |
Managers who need visibility without write access |
Everyone in the workspace, in any role and on any plan, sees the email of the owner and of every active member. The dashboard shows it wherever it names a person, such as the Do not contact panel. The API, the MCP server and exports return the email of a lead’s assignee and of a note’s author. An assistant or app that a member connects receives what that member reads, so it receives those emails too. Webhooks carry neither the assignee nor the note author.
A removed member appears as a former member in the dashboard. Their email stays in the API, the MCP server and exports on the leads assigned to them, on the notes they wrote and on the assigned entries of the history, until their account is deleted or, for a deleted lead, until its history values are erased. Other members do not see pending invitations. No account outside the workspace sees these emails.
API key and webhook endpoints (/api-keys, /webhooks), batch deletion (DELETE /leads/batch), and global score recalculation (POST /leads/score/batch) are reserved to the owner or an admin, in both the dashboard proxy and the API. Editors can still create/update leads in batches and recalculate a single lead’s score. An invited editor or viewer receives:
{ "error": "forbidden", "message": "Only the workspace owner or an admin can perform this action", "code": "forbidden"}A viewer calling a mutating method outside these endpoints (POST, PUT, DELETE, …) receives:
{ "error": "forbidden", "message": "Viewer role cannot modify data", "code": "forbidden"}In a read-only workspace, the read-only check blocks changes to leads, scoring rules, the status list and the lock policy with 403 workspace_read_only, including writes made with API keys. Earlier scope and access checks can return a different error.
Lead access
Section titled “Lead access”An admin sees no leads unless the workspace owner gives lead access. In Team, the owner selects Give access on the admin’s row and picks 24 hours, 7 days or No limit. Access ends by itself, or earlier when the owner selects End access.
An admin without access can select Request access. The owner gets an email and a notice in Team, and selects Give access or Decline. A request expires after 7 days, and the admin can cancel it with Withdraw.
Lead access resets when an admin is invited, changes role, is removed or leaves, and when ownership is transferred. Only the owner sees the access and the requests of other admins.
Lead access governs what the person sees in the dashboard and in their own AI assistant. API keys and webhooks keep working, including the ones the admin created. Without lead access, an admin can still manage API keys, webhooks, scoring rules and the lock policy. These permissions remain subject to the workspace’s plan and read-only state.
Assign leads
Section titled “Assign leads”A lead has one assignee: the workspace owner or an active member. The dashboard shows a person by their email.
Owners, admins and editors can assign leads. Viewers cannot. On an editable Free workspace, only the owner can assign leads, because every other member has read-only access. In a read-only workspace, nobody can. You can assign a lead to the owner or to any active member, whatever their role or plan. A viewer can hold leads, and a pending invitation cannot be picked.
- In the list, the Assignee column shows the person’s email, Unassigned, or Former member.
- Above the list, All leads shows every lead, My leads the leads assigned to you, and Unassigned the leads assigned to nobody. The scope combines with your filters and applies to the export.
- In the filters, choose the field Assignee, then me or a member’s email as the value. me is you. The operators are equals, not equals, is empty and is not empty. not equals also returns unassigned leads.
- On a lead, the Assigned to row holds a button: Choose a person when nobody is assigned, the email otherwise. It opens a list you can search by email, with you first as Me ([email protected]). Remove assignment takes the lead back to Unassigned. Members who cannot assign see the email as text.
- In the list, check the leads you want, choose Assign, pick one person and confirm with Assign. All the checked leads go to that person. The dashboard cannot unassign in bulk: remove the assignment on one lead at a time, or send
"assignee": nulltoPUT /leads/batch.
When a member is removed or leaves, their leads stay assigned to them until you assign someone else. The dashboard shows Former member in place of their email, and that person cannot be picked.
A merge never changes the assignee of the lead it updates, whether it comes from the API or from an import.
In the API, send assignee on Create Lead or Update Lead, and filter leads with assignee (filter operators).
Note authors and the history tab
Section titled “Note authors and the history tab”Every member of the workspace sees who wrote a note. A note carries a byline, by {actor} · {date}. {actor} is the member’s email, or a former member for someone who is no longer in the workspace. For your own notes it reads by you. A note written with an API key reads via {key} · {date}, for example via the key “Make prod”. A revoked key keeps its name, followed by (revoked). Some older notes, and notes whose author deleted their account, show no byline.
The history tab of a lead lists its 50 most recent changes. Each line gives the change, its date and who made it: by {actor} for a member, via {key} for an API key. Automatic score updates are not listed, so a score can change without a line. The API lists them: see the audit trail.
Change a member’s role
Section titled “Change a member’s role”In Dashboard → Team, the workspace owner can use the role selector next to a member to switch between Admin, Editor and Viewer. An admin can switch a member between Editor and Viewer only: granting, changing or removing the admin role stays with the owner. The change is saved immediately, without removing the member or sending another invitation. An unexpired pending invitation can also be updated; revoked and expired invitations cannot. The owner’s role cannot be changed.
Changing a member’s role cuts their assistants’ access to that workspace. The member must authorize each assistant again for it, even after a promotion. Their assistants’ access to other workspaces is not affected.
Leave a workspace
Section titled “Leave a workspace”Any member except the owner can leave a workspace. Select it in the Workspace selector, open Dashboard → Team and choose Leave workspace. Your access to its leads stops at once, as if you had been removed, and your assistants lose access to that workspace only. Their access to your other workspaces is not affected. To come back, you need a new invitation.
API keys and webhooks belong to the workspace, not to the person who created them, so leaving does not remove them. When an admin leaves, the dialog lists the keys and webhooks they created, unselected: select the ones to revoke (keys) or delete (webhooks) now. The same list appears when an owner or an admin removes a member.
The owner cannot leave: Klozeo refuses with 403 and the code team_owner_leave. Transfer the workspace to an active member first, as Hand a workspace to your client describes. You stay on as an admin and can then leave. The other ways out are Delete workspace, where Settings offers it, and Delete account in Dashboard → Settings, which deletes all its data, team members included.
Choose a workspace
Section titled “Choose a workspace”Accepting an invitation opens the workspace you joined. Otherwise your first workspace opens by default, including when you own several workspaces or belong to several teams. The dashboard sidebar always shows the selected workspace; use the Workspace selector to switch to another one you own or were invited to. The selection is saved in a cookie, and ownership or active membership is checked on every request. A revoked or unavailable selection falls back to your first workspace.
When you belong to two or more workspaces, the selector adds All workspaces. It opens Your workspaces: one row for every workspace you belong to, in any role, with a link that opens it and a Current badge on the selected one. Each row shows your role, the plan (with the end date of a Pro trial or of a period already paid), the number of leads, the date and time of the last change in the lead history (automatic score updates do not count) and the webhook deliveries that failed in the last 7 days, linked to that workspace’s Webhooks page. In the last column, rows where you are an owner or an admin show the count; other rows show Owner or admin only (an admin on a Free workspace counts as a viewer). Workspaces with an end date come first, soonest first, then the others by name. The page only shows state. Billing stays with each workspace’s owner.
Create and rename workspaces
Section titled “Create and rename workspaces”Use New workspace in the sidebar to create a separate workspace, for example one per client. You own it, and it has its own leads, members, API keys, webhooks and assistant connections: nothing is shared with your other workspaces. A new workspace starts on the Free plan, without a trial.
Each workspace has its own plan and its own subscription. As the owner, select the workspace and subscribe it to Pro or Scale from Settings, or to Pro from the sidebar. Every subscription is billed to you, and Manage billing lists all of them. Every workspace except your first pays the standard price: founder pricing, while the offer is open, is for your first workspace only. Admins, editors and viewers cannot change a workspace’s plan. You can own any number of paid workspaces.
You can create a Free workspace only if you own no other Free workspace, your first workspace included. If your first workspace is on the Free plan, upgrade it before creating another one.
The owner can rename a workspace with Rename in the sidebar. Names are 1 to 100 characters.
CSV and XLSX exports use the selected workspace, preserve the downloaded file, and remain available to every role.
When a Free workspace becomes read-only
Section titled “When a Free workspace becomes read-only”Only one Free workspace you own stays editable: your first workspace if it is on Free, otherwise the oldest of your Free workspaces. Every other Free workspace you own becomes read-only for every member, the owner included. This can happen when your Pro trial ends, when a subscription ends, or when a paid period ends after a transfer. Nothing is deleted: reading, export, members, API keys, webhooks and assistant connections keep working, but changes to leads, scoring rules, the status list and the lock policy are refused, including with API keys. They return 403 workspace_read_only, unless an earlier scope or access check returns its own error first. A banner explains it in the dashboard. Subscribing a read-only workspace to Pro or Scale restores editing in it. If you own exactly two Free workspaces, subscribing the other one also restores editing.
Delete a workspace
Section titled “Delete a workspace”Only the owner of a workspace can delete it. Admins, editors and viewers cannot.
Select the workspace in the Workspace selector, open Settings, and find the Delete workspace card, above Delete account. Select Delete this workspace, type the workspace name to confirm, then select Permanently delete this workspace. The dashboard reloads in another workspace you can access.
The deletion is permanent. It removes the workspace and everything in it: leads, notes, attributes and history, scoring rules, API keys, webhooks, members and invitations. Automations that use its API keys stop working. Assistants (Claude, ChatGPT and other MCP clients) lose the workspace and keep their other workspaces. Your other workspaces are not affected. Encrypted backups are kept for at most 90 days.
Klozeo refuses the deletion when:
- the workspace has a subscription that has not ended. Cancel it with Manage billing in Settings, then delete the workspace once the subscription has ended;
- the workspace is paid until a date, after a paid transfer. Delete it after that date;
- a payment for it is in progress. Try again once it is completed or has expired, within 25 hours;
- a transfer offer is pending. Cancel it with Cancel offer on the Team page, or let it expire after 7 days;
- it is the only workspace you can access. Delete your account instead.
The workspace created when an account signs up cannot be deleted on its own, even after it is transferred: transfer it again to an active member, or delete the account that owns it.
How the API sees the role
Section titled “How the API sees the role”When a member works in the dashboard, Klozeo knows who they are and which role they hold: you never pass a role yourself. Each change they make is recorded in the audit trail with their own actor id.
What an API key can do
Section titled “What an API key can do”n8n, the SDKs, cURL, and any client that authenticates with X-API-Key act as the workspace owner when the key has full access, the default when you create a key in the dashboard. Existing automations do not break when you invite team members: roles apply to dashboard access, not to API keys. An admin can create and revoke the workspace’s API keys. A full-access key acts as the owner, except that a key created by an admin cannot export the account. A read key acts as a viewer, and a write key can only create and update leads, notes and custom attribute values.
A request cannot choose its own role. The X-Member-Role and X-Actor-Id headers are no longer accepted: a request that sends either one is refused with 401 Unauthorized. Remove them from older scripts.
What to share with your team
Section titled “What to share with your team”- Editors / viewers: the owner or an admin invites them from the dashboard; they sign in and work in the UI.
- Consultants: invite them as admin; they create the API keys and webhooks your automations need, without your password, and they can invite and manage your editors and viewers.
- Automations: keep using the owner’s API key, or create keys as the owner or an admin. Do not put member session cookies into n8n.
- Audit: when a member changes a lead in the dashboard,
actor_idonGET /leads/{id}/changesshows who did it.