Hive Teamshiveteams
Platform · Integrations

Connected to the tools your teams already use.

Sign-in and the LLM are the same for every team. Each team connects the tools its work needs, and this page says plainly what is connected today and what we set up on request.

Connected to Hive Teams
GitHubTodayHubSpotTodaySalesforceTodayLogoTodayPersonioTodayMicrosoft Entra IDTodayClaudeTodayJiraOn requestAzure DevOpsOn requestSAPOn request
Three ways to connect: our team apps, work-queue sync, or working inside your tool.

Work in your own tools

Keep the tools your teams already use. Agents work with them; approvals and the record stay in Hive Teams.

AOur team appsHT Software Delivery, HT Sales, HT CRM, HT Accounting and the other team apps: agents work there directly, with the approval gate and the record built in.Today
BWork-queue syncJira Cloud, Jira Data Center and Azure DevOps sync with HT Boards: requests come from your tool, status and comments go back. Enterprise, set up with an integration project.On request
CWork inside your toolIn HubSpot, Salesforce, Logo or Personio, agents read and write your records over the API, with no copy; every write passes the approval gate. SAP, Oracle and self-hosted systems are Enterprise, with an integration project.Today · enterprise systems on request

For every team

IDMicrosoft Entra IDConnected todaySSO with Microsoft Entra ID on Pro and Enterprise; organization SSO and SCIM on Enterprise.
AIClaudeConnected todayAgent work uses Hive credits included with every seat. On Pro and Enterprise you can connect your own LLM key.
TSMicrosoft Teams and SlackOn requestApproval and question cards from Messenger can also arrive in your Teams or Slack channel and be answered there. On request.
By team

What each team connects

GHGitHubConnected todayRepositories, branches and pull requests
ADAzure DevOpsOn requestTwo-way sync with HT Boards · Enterprise, with an integration project
GLGitLabConnected todayRepositories and merge requests
MCMCPConnected todayConnect your own agents to project memory over MCP
MEMicrosoft Entra IDConnected todaySSO on Pro and Enterprise
CLClaudeConnected todayThe model agents work with
JCJira CloudOn requestTwo-way sync with HT Boards · Enterprise, with an integration project
JDJira Data CenterOn requestTwo-way sync with HT Boards · Enterprise, with an integration project
ARAzure ReposConnected todayRepositories, branches and pull requests
BBBitbucketConnected todayRepositories, branches and pull requests
Every connection runs under the same approval gates and is recorded.

How a connection is set up

  1. 1YouAn owner connects the toolWith OAuth or a service account you create. No passwords are shared.
  2. 2YouYou choose the accessRead, draft or write, per tool and per agent role.
  3. 3TogetherGate rules applyWhat leaves or changes waits for a person, the same as in our own apps.
  4. 4Hive TeamsThe first job is on the recordEvery call the agent makes is logged on the work item.

Security and access

Least accessAgents get only the scope their role needs, per tool.
Your keysTokens and service accounts stay under your control and can be revoked anytime.
Every call on the recordWhat the agent read and wrote, on which item, approved by whom.
Export to your SIEMSession records and approvals export over an API.
See Trust →
ENTERPRISE

Enterprise integration projects

For self-hosted and enterprise systems such as SAP, Oracle, Workday and Jira Data Center. Fixed scope; price by quote.

  1. 01DiscoverySystems, data, access and what the agents should do.
  2. 02DesignThe connection, the scopes and the gate rules, in writing.
  3. 03BuildThe connector is set up and tested on a copy.
  4. 04Go liveThe first team works through it; we watch the first weeks.
HIVE TEAMS ON HIVE TEAMS

We run Hive Teams on itself

Our own teams work through GitHub, Microsoft Entra ID and Claude, with the same gates and records you get.

Build an integration with us

Technology partners build and maintain connectors to Hive Teams.

Become a partner →

Questions

No. In mode C the agents work inside your tool over its API; only the record of what they did and who approved it stays in Hive Teams.

Don't see your tool?Tell us the tool, whether it's cloud or self-hosted, and which team needs it.

See your tools connected to one team.

A 30-minute walkthrough on your own setup.