Knowledge access control
Limit each source to chosen resources and teams. Check sync health or indexed documents when results look wrong.
Knowledge access has two gates. First, choose what enters the index; then grant the source to specific teams. Without a grant, a team's agents get no results from that source.
Access follows the team
Sources belong to teams, not individual sessions. Every agent uses the sources granted to its team, which keeps one access boundary in place for all agents working there.
- 01
Source scope
Sets the repositories, pages, Slack channels, Linear teams, or website URLs that enter the index.
- 02
Team grant
Gives one team's agents permission to search the source.
- 03
Agent
Uses its team's approved sources in every session.
Image placeholder
Capture Edit source with the provider, selected resources, and Teams field in the same frame. Use demo names that show one narrowly scoped source granted to a single team; keep every label readable.
Limit what enters the index
A connection may read far more than an agent needs. Keep each source to the smallest useful set of repositories, Notion pages and databases, Slack channels, Linear teams, or website URLs because everything in one source shares the same team grants.
If an admin removes a resource from the scope, Hivy deletes that resource from the index. Hivy reads newly added resources from the beginning before agents can search them.
Grant access by team
Open the source, choose Edit source, then update the Teams field. A grant makes the source searchable in every session owned by that team, while revoking it leaves other teams unchanged.
On every search, Hivy checks the active session's team and its grants. The agent cannot switch teams behind the search or cross that boundary.
Open Knowledge settingsVideo placeholder
Capture an admin opening Edit source, removing one resource, adding another team, and saving. Open View documents to check the remaining index. Finish with a session in a team that has no grant and show a search that returns nothing from this source.
Treat team grants as the access switch
Pause ingestion and Disable sourcestop scheduled indexing; neither action revokes a team grant. Remove the team from Teams when its agents must lose search access. Use Remove source when the workspace should no longer keep its indexed documents.
Read how teams control resourcesCheck sync health before trusting an answer
- Indexing
- Hivy is processing documents from the first sync or a later update.
- Up to date
- Agents can search the indexed content, and the latest sync succeeded.
- Paused
- Hivy will not run scheduled indexing until an admin resumes the source.
- Disabled
- Hivy skips this source during scheduled indexing until an admin enables it.
- Last sync failed
- Hivy could not finish the latest sync. Check the connection and source scope before trying again.
Connected sources refresh on a schedule. If indexing still runs or the latest sync failed, search may use an incomplete or older index. For current provider data, use its live connection.
Inspect what Hivy indexed
Choose View documents from the source menu. Search the document titles, links, and update dates to find anything missing or outside the intended scope.
Audit a source before agents use it
- Check the content the connection can read.
- Cut the source scope down to what agents need.
- Grant the source only to teams that own this work.
- Inspect View documents, then test a search from one granted team and one ungranted team.