Department isolation
Keep Accounting and Engineering (or any two departments) in the same Keystone organization while preventing their agents—and everyday Ask—from mixing private libraries.
Isolation works best when you use all four layers:
Accounting site → connector → Accounting team scope → facts
Engineering site → connector → Engineering team scope → facts
Accounting agent key (bound) → only Accounting
Engineering agent key (bound) → only Engineering
Why one layer is not enough
| If you only… | What goes wrong |
|---|---|
| Filter the site | Facts still land on Organization → everyone can recall them |
| Use a team scope | Org-wide SharePoint links can still widen access inside that scope |
| Trust file ACLs alone | Agents with org-wide keys still walk every scope they can see |
| Bind the key alone | People can still see org-scoped content in the console |
Recommended setup
1. Groups and people
Put people in clear groups under Settings → Members (or your identity sync). Mirror how you think about departments.
2. Team scopes
Settings → Scopes (or create inline when connecting SharePoint):
| Scope | Members |
|---|---|
| Accounting | Accounting group / people |
| Engineering | Engineering group / people |
Do not target department libraries at Organization.
3. One connector per department site
For each site:
- Connect SharePoint (or add the site) with that department’s team scope.
- Limit to a folder if only part of the library should sync.
- Avoid “anyone in the organization” sharing on those libraries.
Plan limits: Free includes one connector; Team allows many. Multi-department usually needs Team or higher.
4. Bound agent keys
Mint a separate workspace key per department under Settings → Keys or Connect:
- Bind the key to that department’s team scope
- Give recall/retain (and reflect/feedback if the agent uses them)
- Do not paste one unbound org-wide key into every department bot
Details: Connect AI tools.
Prove it works
- Sync both connectors.
- As a normal Accounting member (or Accounting-bound key), ask something only Engineering should know—expect no answer from Engineering docs.
- Repeat the other way.
- Confirm operators can still open Sources for both when troubleshooting.
Checklist
- Team scopes exist with the right members
- Each department site has its own connector on that scope
- Org-wide SharePoint links avoided on department libraries
- Separate bound keys for department agents
- Isolation test passed both directions