Roles and permissions
What Owners, Admins, and Members can see and do.
Every Knosy account belongs to a team, and in this version each account belongs to one team. Inside it, people hold one of three roles: Owner, Admin, or Member.
Two things in a team are shared and therefore governed by permissions:
- Shared context: the team's and each space's instructions and reference files, which give sessions their working context.
- Shared memories: the useful things Knosy learns from everyone's sessions and keeps for the team.
What each role can do
| Ability | Owner | Admin | Member |
|---|---|---|---|
| Use shared context and search shared memories | Yes | Yes | Yes |
| Contribute memory suggestions | Yes | Yes | Yes |
| Edit or archive their own published memories | Yes | Yes | Yes |
| Publish changes to shared context | Yes | Yes | With Editor permission |
| Review everyone's pending memory suggestions | Yes | Yes | Own only |
| Manage all published memories, including curated ones | Yes | Yes | No |
| Invite people and manage roles and permissions | Yes | Yes | No |
Viewer and Editor
A Member starts as a Viewer of shared context: they can read everything shared with them and keep local copies, but their changes stay local until someone with permission publishes them.
An Owner or Admin can grant a Member Editor permission for the shared context they help maintain. Editors publish their changes directly.
Pending memory suggestions stay private
When Knosy suggests a new shared memory, only its author sees it while it's pending, plus the team's Owner and Admins, who can review everyone's suggestions. Other members never see someone else's pending suggestions; they only see what gets published.
Private is always yours
No role reaches into your Private scope. Your personal context and personal memories belong to you alone, on every team, and no Owner or Admin can see or manage them.