> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.alephant.io/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.alephant.io/_mcp/server.

# Enterprise Integrations

> Configure available service accounts, enterprise chat bots, and Hook extensions without expanding access beyond the approved deployment boundary.

Enterprise integrations are conditional capabilities. Configure an integration only when the current deployment exposes it, the service owner has approved it, and its authentication and data scope are understood.

## Integration map

| Integration type     | Purpose                                                                              | Availability boundary                                                    |
| -------------------- | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------ |
| Service Accounts     | Authenticate an approved connector or service without using an individual's account. | Requires the relevant integration and deployment configuration.          |
| Enterprise chat bots | Make an approved OpenCore experience available in an enterprise chat service.        | Requires the specific bot integration and its service-side setup.        |
| Hook extensions      | Extend an approved workflow with Hook behavior.                                      | Available only when Hooks are enabled and configured for the deployment. |

## Service Accounts

Use a Service Account only for the approved integration and the smallest source scope it needs. Keep its credentials in the approved secret store, document the account owner and purpose, and rotate or revoke access when the integration changes.

An integration using a Service Account does not bypass source permissions, deployment access controls, or Administrator review.

## Enterprise chat bots

Configure an enterprise chat bot only after the deployment and chat-service administrators have approved its audience, data flow, and authorization model.

| Chat service | Verification focus                                                                                        |
| ------------ | --------------------------------------------------------------------------------------------------------- |
| 企业微信         | Confirm the bot is available only to the approved audience and follows the configured authorization flow. |
| 飞书           | Confirm the bot's permissions, intended audience, and representative conversation flow.                   |
| 钉钉           | Confirm the bot's access scope and the authorized user experience.                                        |
| Mattermost   | Confirm the integration configuration, channel scope, and authorized interaction flow.                    |

## Hook extensions

Hooks are conditional extensions, not a capability guaranteed in every deployment. When Hooks are available, configure only an approved extension, define its authorization and data boundary, and test its behavior with representative non-sensitive input.

If Hooks are absent or disabled, review deployment configuration and administrator settings instead of assuming that an extension can be enabled by a user or Curator.

## Authentication and secret handling

Use the service's approved authentication method and store credentials only in the deployment's approved secret-management location. Never place tokens, passwords, private keys, or client secrets in chat messages, Agent instructions, source control, screenshots, or shared documents.

Grant the minimum required scope, use distinct credentials for distinct integrations where possible, and revoke or rotate credentials when ownership, scope, or service configuration changes.

## Verify an integration

Before sharing an integration, test it with an approved account and representative request. Confirm that authentication succeeds, only the intended audience can use it, it reaches only the approved service scope, and errors reveal no secret values.

## Related pages

* [Users, Groups & Roles](/opencore/governance/users-and-groups) explains how access boundaries apply to people and groups.
* [Connectors & Indexing](/opencore/knowledge/connectors) explains how approved content connections are configured.
* [Usage, Identity & Security](/opencore/governance/usage-and-security) explains conditional identity and security controls.