Members and roles
Access in Kumkuat is scoped to a workspace. A person can belong to several workspaces with a different role in each.
Roles
| Role | Summary |
|---|---|
| Owner | Full control including workspace deletion |
| Admin | Manages members, sources, audiences, models, toggles and integrations |
| Member | Uses every enabled feature; creation rights are governed by permissions |
| Viewer | Read-only |
Permissions
The Permissions tab lets admins grant or withhold specific rights per role, for example:
- create and edit personas (the persona-write permission);
- add or change sources and schedules;
- create and edit alerts and scheduled reports;
- manage API keys;
- install from the Marketplace.
Writes are checked on every request, so a permission removed in settings takes effect immediately.
API keys and members
A workspace API key acts with the rights of the workspace, not of the person who created it. Keep keys in a secret store and rotate them when a member with key access leaves. See REST API.