Workspace roles
Owners and admins set up the workspace. Members work inside the teams they join.
Group people and agents by team, choose the connections, knowledge, and skills each team can use, and let Hivy enforce the same boundary in every session.
Roles, teams, and grants
Owners and admins manage the workspace. Members work through the teams they belong to. Each team carries the agents and resources its job calls for.
Owners and admins set up the workspace. Members work inside the teams they join.
Group people and agents around a function such as Product, Support, or Operations.
Grant the connections, knowledge sources, and skills that team needs, once.
One boundary for every session
Switch on the exact accounts, indexed sources, and published skills a team can use. Hivy resolves those grants again whenever an agent starts work.
Product team access
Connected company accounts the team’s agents can use.
Slack · Atlas
Approved channels and threads
Linear · Product
Issues, projects, and comments
Notion · Product
Team pages and databases
GitHub · atlas-web
Repositories, issues, and pull requests
Choose the connected accounts an agent may act through instead of exposing every provider in the workspace.
Limit search to the repositories, channels, pages, and sites approved for that team.
Make approved procedures available to the agents that need them while keeping other teams separate.
Create a free workspace, add a team, and assign only the connections, knowledge, and skills its work calls for.