| Specification | Details |
|---|---|
| Repository type | Cloud |
| Supported content | Actions and Sub-Actions |
| RACL support | Yes |
| Content filtering | Yes |
| Auto permission resolution | Yes |
Prerequisites
- Hive account
- Hive API Key and Workspace ID
Generate an API Key on Hive
- Open Edit Profile in the Hive application.
- Go to API Info.
- Copy the API Key and Workspace ID.
Configure the Hive Connector
- Navigate to Content > Connectors in Search AI and select Hive.
- On the Auth tab, enter the following details:
| Field | Description |
|---|---|
| Name | Unique name for the connector |
| API Key | API Key from Hive |
| Workspace ID | Workspace ID from Hive |
- Click Connect.
Content Ingestion
The connector ingests Actions and Sub-Actions from selected projects within your workspace. Actions from sub-projects are not ingested unless those sub-projects are explicitly selected. To configure content ingestion:- Go to the Configuration tab of the connector.
- Select Sync Specific Content and click Configure.
- Select the projects to ingest actions from.
- To include both a project and its sub-projects, select all relevant projects in the hierarchy.
- Click Save.
- Click Sync Now to start ingestion immediately, or configure a scheduled sync.
RACL Support
Search AI controls access to Hive content based on project membership and assigned roles. For each action, all users with roles of creator, follower, or assignee are added to thesys_racl field.
Search AI automatically resolves permission entities for Hive — no manual API mapping is required. Permission entities are determined by project type and sharing type:
| Project Type | Sharing Type | sys_racl |
|---|---|---|
| Public | Everyone | Workspace ID |
| Public | Custom | projectID, Workspace ID |
| Private | Everyone | Workspace ID |
| Private | Custom | projectID |
| Private | Me | projectID |
Note: Client mode is not supported via Search AI.