User Roles

The three Kimchi organization roles (Owner, Member, Viewer), what each role can do in the console, and the full permission matrix.

Every member of your Kimchi organization has a role that controls what they can see and do in the console. Roles are assigned and changed from the Members page under Account → Members.

The Members page has two tabs: Members and Invitations. The Members tab lists every person with access, along with their role, join date, and last sign-in. The Invitations tab lists pending invites. You can search the Members table by name or email.

Kimchi has three roles: Owner, Member, and Viewer. The permission matrix below shows every console capability and which roles can use it.

Roles

RoleWhat it can do
OwnerFull access to every capability: member and Service Key management, organization settings, billing and credit top-up, teams, budgets, all model types, agents, integrations, coding tools, and batch jobs.
MemberBroad operational access. Can manage providers, self-hosted deployments, teams, agents, integrations, code reviewer, batch jobs, and settings, and can top up credits. Cannot invite, edit, or remove members, and cannot manage organization settings.
ViewerView-only on every product feature. The only writes available are creating and deleting the member's own API keys.

Permission matrix

Each table below covers one area of the console. A ✓ means the role can perform the action; a ✗ means it cannot.

📘

This matrix reflects the default role definitions. If a role binding has been customized for your organization, the effective access may differ.

Overview and analytics

CapabilityActionOwnerMemberViewer
AnalyticsView analytics✓✓✓
OverviewView overview page✓✓✓

Coding

CapabilityActionOwnerMemberViewer
Code ReviewerView code reviewer✓✓✓
Code ReviewerAdd repository✓✓✗
Code ReviewerEdit code reviewer item✓✓✗
Code ReviewerDelete code reviewer item✓✓✗
AdoptionView adoption report✓✓✓
UsageView usage report✓✓✓
ProductivityView productivity report✓✓✓
OpsView findings / ops✓✓✓
OpsCreate finding / runbook item✓✓✗
OpsUpdate finding / runbook item✓✓✗
OpsDelete finding / runbook item✓✓✗
OpsExecute remediation✓✓✗

Models

CapabilityActionOwnerMemberViewer
Serverless ModelsView serverless models✓✓✓
External ProvidersView providers✓✓✓
External ProvidersAdd provider✓✓✗
External ProvidersEdit provider✓✓✗
External ProvidersDelete provider✓✓✗
Self-Hosted ModelsView deployments✓✓✓
Self-Hosted ModelsCreate deployment✓✓✗
Self-Hosted ModelsEdit deployment✓✓✗
Self-Hosted ModelsDelete deployment✓✓✗
Model AccessView model access✓✓✓

Tools

CapabilityActionOwnerMemberViewer
Batch JobsView batch jobs✓✓✓
Batch JobsRun / manage batch job✓✓✗

Remote

CapabilityActionOwnerMemberViewer
Remote SessionsView remote sessions✓✓✓
Remote CredentialsView remote credentials✓✓✓

Agents

CapabilityActionOwnerMemberViewer
AgentsView agents✓✓✓
AgentsCreate agent✓✓✗
AgentsRun agent✓✓✗
AgentsDelete agent✓✓✗
AgentsModify schedule✓✓✗
IntegrationsView integrations✓✓✓
IntegrationsAdd integration✓✓✗
IntegrationsEdit integration✓✓✗
IntegrationsDisconnect integration✓✓✗

Governance

CapabilityActionOwnerMemberViewer
BudgetsView budgets✓✓✓
BudgetsEdit/delete budget✓✓✗

Account

CapabilityActionOwnerMemberViewer
SettingsView settings✓✓✓
SettingsEdit settings✓✓✗
MembersView members✓✓✓
MembersInvite member✓✗✗
MembersEdit member✓✗✗
MembersRemove member✓✗✗
Organization SettingsView organization settings✓✓✓
Organization SettingsEdit organization settings✓✗✗
TeamsView teams✓✓✓
TeamsCreate team✓✓✗
TeamsEdit team✓✓✗
TeamsDelete team✓✓✗
Pricing & BillingTop up credits✓✓✗

Settings

CapabilityActionOwnerMemberViewer
API KeysView API keys✓✓✓
API KeysCreate API key✓✓✓
API KeysSet API key budget✓✓✗
API KeysDelete API key✓✓✓
Service KeysView service keys✓✓✓
Service KeysCreate service key✓✗✗
Service KeysSet service key budget✓✓✗
Service KeysDelete service key✓✗✗

Special cases

A few capabilities do not follow the standard role pattern:

  • API keys are not role-gated. Any member can create an API key from the API Keys page, and each member can delete only the keys they created. Setting an API key's budget does require the Owner or Member role.
  • Service Keys follow member management. Creating and deleting Service Keys uses the same permissions as inviting and removing members, so only Owners can do it. Setting a Service Key budget requires Owner or Member.
  • Some pages are available to every role. The Overview page, Model Access, Remote Sessions, and Remote Credentials are not gated by role; every member of the organization can open them.

Edit a user's role

  1. Go to Account → Members, find the member in the table, click the ⋯ button in the Actions column, and choose Edit role.
  2. Pick the new role from the dropdown. The dialog shows the member's name and email.
  3. Click Save. The change applies immediately.

What you can and can't do

The row menu on the Members page enforces the following rules:

  • Only Owners can use the Edit role and Remove member actions. If those actions are disabled in the row menu, your current role is not Owner; ask another Owner to make the change for you.
  • You can't change your own role. The Edit role action is disabled on your own row; ask another Owner to change it for you.
  • You can't remove yourself if you are the last Owner. The Remove member action is disabled on your own row when you are the only Owner in the organization; add another Owner first, or ask another Owner to remove you.

Audit

⚠️

Role changes are not currently recorded in an audit log.

See also


Did this page help you?