Skip to content
Ukkora

Roles & Permissions

User types in Ukkora — what each role can see and do in a workspace.

Overview

Every member of a workspace has exactly one role. Roles control what a member can see, create, and manage. There are four member types in Ukkora:

TypeDescription
OwnerFull control over the workspace, billing, and all members
AdminCan manage members, tasks, and workspace settings
MemberCan create and complete tasks within the workspace
Virtual memberA placeholder for people without a Ukkora account

Roles

Owner

The workspace creator is automatically the owner. There must always be at least one owner per workspace — you cannot demote or remove the last owner.

Owners can transfer ownership to another member by changing their role to owner via PATCH /api/v1/workspaces/:id/members/:memberId.

Admin

Admins have the same day-to-day access as owners, but they cannot manage billing or delete the workspace itself. Use this role for team leads and project managers.

Member

The default role for all invited users. Members can create tasks, assign them to themselves or the shared pool, and mark tasks as complete. They cannot invite others or change workspace settings.

Virtual member

Virtual members are special placeholders — they don't have a Ukkora account and cannot log in. They're useful for representing contractors, clients, or teammates who haven't signed up yet. Tasks can be assigned to virtual members and appear attributed to them in the UI.


Permissions reference

Workspace

ActionOwnerAdminMember
View workspace✓✓✓
Rename workspace✓✓—
Delete workspace✓——
View billing & subscription✓——

Members

ActionOwnerAdminMember
View member list✓✓✓
Invite members✓✓—
Resend / revoke invites✓✓—
Change member role✓——
Remove members✓✓—
Add virtual members✓✓—

Note: Admins can invite and remove members, but only owners can change roles.

Tasks

ActionOwnerAdminMember
View all tasks✓✓✓
Create tasks✓✓✓
Assign tasks✓✓✓
Edit any task✓✓—
Edit own tasks✓✓✓
Delete any task✓✓—
Delete own tasks✓✓✓
Complete tasks✓✓✓
Create recurring tasks✓✓✓

API tokens

ActionOwnerAdminMember
Create personal API tokens✓✓✓
Revoke own tokens✓✓✓

API tokens are always personal — they act on behalf of the creating user and inherit their workspace permissions. An admin's token cannot perform owner-only actions.


Role in API responses

The current token owner's role is returned in the role field of workspace objects:

{
  "data": [
    {
      "id": "550e8400-e29b-41d4-a716-446655440000",
      "name": "My Team",
      "role": "admin"
    }
  ]
}

Endpoints that require elevated permissions return 403 forbidden when the token owner's role is insufficient. The error body explains what role is required:

{
  "error": "Insufficient permissions. This action requires the admin or owner role.",
  "code": "forbidden"
}

Changing roles via API

Use PATCH /api/v1/workspaces/:workspaceId/members/:memberId to update a member's role. This endpoint requires the owner role.

PATCH /api/v1/workspaces/550e8400-e29b-41d4-a716-446655440000/members/member-uuid
Authorization: Bearer ukkora_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Content-Type: application/json

{
  "role": "admin"
}

See Members for the full endpoint reference.

Usage measurement

We would like to measure how Ukkora gets used — it helps us fix what does not work. We use Google Analytics and Microsoft Clarity, which store cookies in your browser. Without your consent they are not loaded.