Workspaces, members & tenancy
The workspace is the tenancy boundary of Klient. Contacts, invoices, documents, workflows, keys and webhooks all belong to exactly one workspace, and only the workspace owner and its active members can see them.
The workspace modellink
- check_circleOne account can own or belong to multiple workspaces; you pick the active workspace inside the app.
- check_circleThe owner controls destructive and sensitive operations — API keys, workspace settings, member removal.
- check_circleMembers are invited with a role (owner / admin / member); admin-level actions like webhook registration require owner or admin.
- check_circleInvitees receive an email with an acceptance link and must sign in with the invited email address to join — an invite link alone grants nothing (2026-07-24).
- check_circleWorkspace tenancy is enforced server-side (2026-07-23): reads and writes are rejected unless your account is the owner or an active member — not just hidden in the UI.
- check_circleEvery meaningful action lands in the workspace audit log (who did what, on which resource, when).
White-label portal settingslink
Workspace settings carry your client-facing identity: workspace name, portal branding, and the portal slug your clients visit. What your clients see in the portal is your brand, not Kariant’s.
Frequently asked questions
Can a member of my workspace see another workspace’s data?expand_more
No. Tenancy is enforced per workspace on the server. A member sees only the workspaces they were explicitly added to.
Who can mint API keys?expand_more
Only the workspace owner. Webhooks can be managed by the owner or an admin member.