DocumentationWorkspace and access

Teams

A team keeps its members and agents on the same work while limiting which tools and knowledge they can reach.

Teams separate one group's work from another. Give Sales or Support its own people, agents, connections, skills, knowledge, and secrets without opening the rest of the workspace.

What a team controls

A team draws the boundary around daily work: membership controls who gets in, while team settings control what its agents can use.

  1. 01

    People

    A member sees work from their teams, not every team in the workspace.

  2. 02

    Agents and sessions

    Agents and their sessions stay within one team.

  3. 03

    Shared resources

    Connections, skills, knowledge sources, and environment variables are granted or saved at the team boundary.

  4. 04

    External routing

    A connected provider resource can route new conversations to one agent in the team.

Image placeholder

Team details and resource access

Take this screenshot from the team details page at 4K and 100% browser zoom. Include members, environment variables, external routing, and granted resources; use demo values and hide every email address and secret.

Create a team for durable ownership

Workspace owners and admins create teams under Settings > Teams > New team. Use the name people already use for the group, such as Sales or Engineering.

Hivy adds the default Hivy agent and puts the creator on the team. There's nothing else to prepare before the first session.

Open team settings

Add the people who own the work

Add a current workspace member from the team page. For someone new, choose Invite member, enter their email, then set their workspace role and team membership before sending the invite.

Once the person accepts, Hivy puts them on the selected teams. Their team membership can change later without changing their workspace role.

Learn about access control

Grant shared resources once

Owners and admins grant workspace connections, skills, and knowledge sources on the team page. Team-owned skills appear automatically; workspace skills require an explicit team grant.

Connections become available to every agent on the team, but one agent may switch off an optional connection. Catalog requirements stay on for the agent that requires them.

Manage knowledge access

Add secrets and external routes deliberately

Team environment variables are encrypted and write-only after you save them. Sessions for that team receive the values, while agents see only each variable's name and description in their context.

External routing assigns a provider resource, such as a Slack channel, to one team agent. A conversation already tied to an agent keeps that affinity even after the route changes.

Configure context and environments

Give the team agents for its jobs

Build agents for the jobs a team handles, then run them in any of that team's sessions. Every agent belongs to one team, so Hivy won't let an agent from another team run its work.

Create and configure an agent

Video placeholder

Create a team and set its access

Record a 60 to 90 second walkthrough at 4K and 100% browser zoom. Create a team, add one member, grant a connection and skill, add a masked demo environment variable, and route one provider resource; hide email addresses and real secrets.

Keep team boundaries stable

Make teams match groups that will still own the work next quarter. Projects and customer accounts usually belong in sessions, since a new team for every task makes access harder to follow.