Hive Connector¶
Hive is a project management and collaboration tool designed to help teams efficiently organize tasks, projects, and workflows. The Hive Connector allows for the seamless integration of Hive Actions into the Search AI application, facilitating easy search operations on these actions.
Hive Connector Specifications
Type of Repository | Cloud |
Content Supported | Actions and Sub-Actions |
RACL Support | Yes |
Automatic Permission Entities Resolution | Yes |
Content Filtering | Yes |
Prerequisites¶
- Hive Account
- API Key
Generate API Key on Hive¶
Search AI interacts with Hive via APIs. To authorize the Search AI API requests, generate an API key in the Hive application. To create an API Key, follow the steps listed below.
- Go to Edit profile on the Hive application.
- Go to API Info and copy the API Key and workspace ID.
Configure Hive Connector in Search AI¶
On the Auth page of the connector, enter the following details and click Connect.
- Name- Unique name of the connector
- API Key - The API Key generated in Hive.
- Workspace ID- Workspace ID for which actions are to be ingested.
Content Ingestion¶
Search AI supports the ingestion of Actions from designated projects within your Workspace. It also includes any sub-actions that may exist under the main Actions.
To start content ingestion,
- Navigate to the Configuration tab of the connector and select the Sync Specific Content.
- Click configure, and then select the projects to ingest actions from. Currently, only actions within a project are ingested. Actions from subprojects are not ingested.
- To ingest content from both a project and its sub-projects, select all relevant projects within the hierarchy.
- Click Save.
- Click Sync Now to start the ingestion process immediately. Alternatively, schedule sync at regular intervals using the scheduler.
You can view the ingested content under the Content tab.
Each Action and Sub Action in Hive is ingested as a separate individual document in Search AI. For each action, the description, comments, status, priority, deadline, milestones, assignees, and checked date are added to the content field of the ingested document. Other details are captured as metadata.
RACL Support¶
- SearchAI supports access control for content ingested from Hive.
- In Hive, each action is associated with a project and can have specific roles assigned, such as creator, follower, or assignee. SearchAI adds all users in these roles to the sys_racl field for the ingested content.
- SearchAI also supports automatic resolution of permission entities for Hive content. It identifies users who have access to the associated project and automatically associates them with the corresponding permission entities in SearchAI. Manual mapping through APIs is not required.
Permission entities are determined based on the project type and sharing type, as shown below:
Type of Project | Sharing Type | sys_racl (added as permission entities) |
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.