Roles and scopes
Keystone separates who can administer the product (roles) from whose memory is visible (scopes).
Roles
| Role | Typical use | Can |
|---|---|---|
| Viewer | Most employees | Ask, browse memory they can see |
| Operator | Knowledge / IT ops | Ingest sources, sync connectors, resolve conflicts and merges |
| Owner | Tenant admins | Everything operators can, plus members, API keys, org settings |
Roles do not replace scopes. An owner still only recalls facts their principals and scopes allow—except that operators and owners can browse all scopes when reviewing Sources and connectors.
What a scope is
Recall layers from narrow to wide:
- Private notes (your user scope)
- Project (optional)
- Team
- Organization (everyone in the tenant)
A value set in a narrower scope overrides a wider one for people in that scope.
Organization
Default for company-wide knowledge. Members are effectively everyone in the tenant. Use for handbook-style facts that should be visible firm-wide.
Team
Best home for department libraries (Accounting, Engineering, HR). Add people or groups as members when you create the scope (Settings → Scopes, or + New team scope while connecting SharePoint).
Project
Optional child under org or team for a time-bounded initiative.
When to create a team scope
Create a team scope when:
- The library should not be visible to the whole company
- You will bind department AI agents to that scope
- Multiple departments each have their own SharePoint (or Drive) site
Do not put department SharePoint on Organization “just for now”—moving it later is harder than creating the scope first.
Members
Scope members are principals such as:
- A person in your tenant roster (shown by name/email in the picker)
- A group that matches how you organize people in Keystone (Settings → Members → Groups)
People only see team memory if they are in that scope (or are an operator/owner browsing for admin work).
Best practices
- One team scope per department that owns a connector
- Name scopes after the department, not the tool (“Engineering”, not “SharePoint 2”)
- Keep Organization for truly company-wide material
- For agents, bind API keys to the team scope—see Connect AI tools