Roles & permissions
Who can do what in Kasimir — the three company roles Owner, Administrator and Member, plus project roles and Kasimir staff.
Kasimir is multi-tenant: each company is an isolated area with its own members, data and settings. What someone may do follows from three levels: the company role, the configurable permissions per role and the roles in teams and projects.
The three company roles
Role | Summary |
|---|---|
Owner | All permissions, plus the final and legally binding actions: remove members from the company and sign the DPA. |
Admin | Administration area: invite members and change roles, create teams, configure models, budgets, policies, integrations and security. |
Member | Works with Kasimir: chat, files, notebook, agents, workflows, meetings, teams and projects – within the permissions below. |
Assigning and changing roles
When inviting, you choose Admin or Member.
Under Administration → Members, owners and admins can switch a person’s role between Admin and Member. Your own role and the owner’s role cannot be changed there.
Only the owner can remove a member from the company. All agents, workflows and skills the person created are handed over to the owner. The person also loses their team and project memberships, API keys, scheduled tasks and shared chat links in this company, their connections are paused, and they are signed out everywhere.
An ownership transfer and deleting the company are done via Kasimir support.
Roles and permissions
Under Administration → Roles and permissions you decide which actions admins and members may perform. The owner always has every permission. In this list, agents are called “assistants”. Defaults:
Permission | Admin | Member |
|---|---|---|
Manage workspace settings | Yes | No |
Create assistants | Yes | Yes |
Share assistants with teams, projects and the whole company | Yes | No |
Create projects | Yes | Yes |
Share projects (add members) | Yes | Yes |
Create workflows | Yes | Yes |
Share workflows with teams, projects and the whole company | Yes | No |
Run workflows | Yes | Yes |
Upload company knowledge | Yes | Yes |
Manage company knowledge (e.g. connect folders company-wide) | Yes | No |
Install skills | Yes | No |
Create skills | Yes | Yes |
Share skills with teams, projects and the whole company | Yes | No |
Connect integrations | Yes | No |
Create artifacts | Yes | Yes |
Sharing with an individual person needs no permission – only shares with teams, projects or the whole company do. That keeps sharing between colleagues simple while broad publication stays controlled.
Roles in teams and projects
Area | Role | Can |
|---|---|---|
Team | Member | See and use the team’s content, create own content |
Team | Editor | additionally change and remove other people’s team files, meetings, chats and prompts |
Team | Lead | additionally manage members and roles, rename and delete the team; counts as project manager in the team’s projects |
Project | Owner | Manage and delete the project; cannot be removed |
Project | Manager | Manage members and settings, change other people’s project content |
Project | Member | See and use the project’s content, create own content |
If a project belongs to a team (home team), all team members have access automatically. More under Teams and Projects.
Private content and admins
Admins manage the workspace but do not read other people’s private content: private chats, artifacts and prompts are visible only to their owner. Other people’s private agents, workflows and skills appear in administration only as structure (name, cost, delete) – they cannot be opened, used or edited. Team and project content is visible only to their members.
Kasimir staff (platform level)
Above the company roles sits a platform-wide special role: Kasimir staff. These are not members of your company but the operator team.
Kasimir staff:
Handle the support tickets you send to the Kasimir team.
Can sign in to an account for support purposes (“Sign in as”). Every such sign-in appears in your company’s audit log.
This role is reserved for the Kasimir operations team and cannot be assigned through member management.