Skip to content
Trust center

Access policy

Who can reach what in kanman: your people, kanman itself, and the people who operate kanman.

Version 1.0 Updated November 15, 2026

Purpose

Access to customer data is granted only where the work needs it, is tied to a person or a single run, and leaves a trace.

Your people

  • Roles per workspace: owner, admin, member and viewer. Only owners and admins change model access, policies, members, API tokens, runners and the audit export.
  • Sign-in: password, email link or single sign-on. With single sign-on (Enterprise) your identity provider decides who signs in; enforcing it for everyone needs a passing sign-in test first.
  • Leavers: removing a member ends access immediately. Revoked API tokens stop working immediately.
  • Isolation: every table checks workspace membership per row, so no query returns another workspace’s data.

kanman itself

  • Each run gets a token that works for that run only and expires with it.
  • The coding tool never holds a code host token, a model key or a secret’s value; a proxy on the run’s host adds them on the way out.
  • kanman reaches only the repositories and paths your team’s policy allows, and only the hosts the run’s network rules allow.
  • Every action kanman takes on your behalf is in the audit log.

People who operate kanman

  • Administrative access to production systems is limited to kanman’s operators, with personal accounts.
  • Operators look at customer data only to run the service, to fix a fault or to answer a support request.
  • Support access to a self-hosted instance exists only when the customer grants it on the instance, with a reason and a time limit.

Review

This policy is reviewed when the product’s access model changes, and at least once a year.