| Specification | Details |
|---|---|
| Repository type | Cloud |
| Supported content | Stories |
| RACL support | Yes |
| Content filtering | No |
| Auto permission resolution | Yes |
Prerequisites
Search AI fetches story content from Shortcut using its APIs. Authentication requires an API token generated in the Shortcut application.Generate an API Token in Shortcut
- Access your user profile.
- Click Settings.
- Go to API Tokens.
- Enter a name for the new token.
- Generate the token.
- Save the token — it is required to configure the connector in Search AI.
Configure the Shortcut Connector in Search AI
- Go to the Shortcut connector in Search AI.
- Provide the following details and click Connect:
| Field | Description |
|---|---|
| Name | Unique name for the connector |
| API Key | API token generated in the Shortcut app |
Content Ingestion
On sync, the connector ingests Stories from all Spaces accessible to the configured account. For each story, the following is ingested:- Content field — Story description plus metadata including epic name, status, team, owner, requester, due date, priority, and skill set.
- Metadata fields — Each metadata attribute is also captured in its own individual field.
RACL Support
In Shortcut, access to stories is controlled at the group level. All members of a group automatically have access to stories associated with that group. When content is ingested into Search AI, the group ID is stored in thesys_racl field of the indexed chunks. These group IDs act as Permission Entities that control access.
Search AI supports automatic resolution of Permission Entities for Shortcut stories. It identifies users who have access to each group and automatically associates them with the corresponding group ID Permission Entity.