Permission Model: Roles in Kinfolk

Last updated: October 15, 2026

All

Kinfolk uses a role-based permission model to control access to conversations, content, configuration, and system settings.

There are three primary roles:

Role Description

Superadmin

System owners have full access to all data, settings, and configurations across the platform.

Admin

Team managers who can manage work, knowledge, and AI training for their teams.

Member

Team members who can create and manage requests but have limited configuration permissions.

Conversations

Action

SuperAdmin

Admin

Member

View / Update

All conversations

Their team's conversations, ones they create, and where tagged in Notes.

Their team's conversations, ones they create, and where tagged in Notes

Create internal request

✅

✅

✅

Archive

All conversations

Their team's conversations and the ones they create

❌

Playground conversations

✅

✅

✅

Categories

Action

SuperAdmin

Admin

Member

Create

✅

✅

❌

Archive

✅

Only categories assigned to their team/they're created

❌

Edit

✅

Only categories assigned to their team/they're created

❌

Knowledge

Action

SuperAdmin

Admin

Member

View, Add, Edit, Delete

✅

Knowledge assigned to their team

❌

Workflows and Assistants

Action

SuperAdmin

Admin

Member

Delete

✅

Only workflows and assistants their team created and owns

❌

Create

✅

✅

❌

View

✅

Only workflows and assistants their team created and owns

❌

Set access rule (who can start a workflow)

✅

Only workflows their team created and owns

❌

Set owning teams (who can view and edit a workflow)

✅

❌

❌

Set both in Workflow settings: in the Workflow Builder, click the settings button in the toolbar, or choose Settings from the ⋯ menu on a workflow in the workflows list. Review & publish shows both settings before a workflow goes live.

Runbooks

Action

SuperAdmin

Admin

Member

Create

✅

✅

❌

Delete

✅

Those they created or are on the 'owning team' of

❌

Edit

✅

Those they created or are on the 'owning team' of

❌

Set owning Teams

✅

Those they created or are on the 'owning team' of

❌

View

✅

Those they created or are on the 'owning team' of

Those who are on the 'owning team' of

Create microsites

✅

✅

❌

Create Forms

✅

✅

❌

Request analytics

Action

SuperAdmin

Admin

Member

View dashboards & use category filters

All teams and categories

Only their teams and categories

Only their teams and categories

Export conversations

✅

❌

❌

Runbook analytics

Action

SuperAdmin

Admin

Member

View dashboards

All teams and categories

Only Runbooks owned by their team(s)

Only Runbooks owned by their team(s)

Forms analytics

Action

SuperAdmin

Admin

Member

View form charts

All linear form charts

Linear forms charts used in runbooks owned by their team(s)

Linear forms charts used in runbooks owned by their team(s)

Export conversations

All form responses

All forms responses used in runbooks owned by their team(s)

❌

Training Center

Action

SuperAdmin

Admin

Member

Train AI (correct mistakes)

✅

Only for their team and categories

❌

Custom instructions

✅

Only for their team and categories

❌

Kin Settings

Action

SuperAdmin

Admin

Member

SLA configuration

✅

❌

❌

Guardrails configuration

✅

❌

❌

Daily digest preferences

✅

Runbook and request digests (not collaborator digest)

Runbook and request agent digests (not collaborator digest)

General Settings

Action

SuperAdmin

Admin

AdminMember

User management

✅

❌

❌

Technical integrations

✅

❌

❌

Timezone settings

✅

❌

❌

Saved filters

✅

✅

❌

Slack customization (name/image)

✅

❌

❌

Manage teams (users and categories)

✅

❌

❌

Key Takeaways

  • SuperAdmins have full system access.

  • Admins manage their teams, categories, knowledge, and AI training.

  • Members focus on handling requests and conversations.

This structure ensures teams can operate independently while maintaining centralized system control.