Grant a Kisi user access to a door by assigning them a role within a group
domain: docs.kisi.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Identify the group_id associated with the door(s) you want to grant access to
Create or locate the target user_id, inviting the user first if they don't already exist
Assign a role such as group_basic by submitting a role assignment request with user_id, role_id, and group_id
Alternatively, use the dashboard's 'Share Access' flow to invite a user and add them to the relevant group in one step
List the user's roles/groups afterward to confirm the assignment took effect
Known gotchas
Assigning a role at the organization/place level grants access far broader than a single door — use group-scoped roles like group_basic for door-specific sharing
The API role-assignment flow and the dashboard's 'Share Access' wizard produce the same underlying result through different UI paths, so confirm which one an automated process actually triggered
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?