How Hivy organizes work
See where a session lives and who can reach it. The same boundaries stop agents from roaming across the workspace.
Hivy stores agent work with the team that owns it. Team members can find the session later, and access controls decide which tools, knowledge, connections, and context its agents can use.
Where a session lives
Every session belongs to a team and an agent. People can find the work without opening the whole workspace to every member or agent.
- 01
Workspace
The company home for everyone and the work they share.
- 02
Team
People and agents assigned to the same area of work.
- 03
Agent
One specialist, owned by a team, with a saved job and tools.
- 04
Session
One agent task with its context, cost, result, and artifacts.
Image placeholder
Capture the workspace at 100% zoom with one expanded team in the left sidebar, named sessions, and one session open in the main area.
Agents belong to teams
Each agent belongs to one team. That team can create specialists for any work it owns, and Hivy offers those agents only inside the team.
Workspace and team controls set the tools, connections, knowledge, and context available to agents. Other company resources stay out of reach. Learn how to create and configure an agent.
Teams organize related work
Teams own their agents, sessions, and shared resources. Team members can read the request and result, then continue where someone stopped without searching through one person’s private history.
Use teams to define shared access, then keep each task in its own session.
Useful results outlive the session
Hivy keeps generated files and artifacts with their source session. Agent Drive preserves useful files across one agent's sessions; Sheets store shared team data, and each app binds to one Sheet.
Automations use the same structure
A schedule, connected-app event, or HTTP webhook can start an agent. During setup, you choose the team and agent; the team will find each run there afterward.
Read the automations overview.