How-To Guides / Admin
Govern Integration Access
Set the default rule for how new integration access gets granted, scope access for one integration specifically, and track your organization's connection readiness.
Governance policy
Set the default and per-integration rules
From Integrations, open the Governance section and the Policy tab. Two settings control what happens when a user asks for access to an integration: a policy mode (how strictly requests are evaluated) and a provisioning mode (whether access can be granted automatically or always needs a review). Both have an organization-wide default.
Review the defaults
Add an integration-specific rule (optional)
Confirm it saved
Scoped access setup
Set up access for one integration
Opened from a connected integration, this wizard scopes exactly which tools and groups that integration exposes — walk the Tools step to choose which actions are allowed, then Groups to scope which of the integration's own groups (discovered through its connection) Telara can see and use.
Custom sources
Register a custom MCP server
If your organization runs its own MCP server — internal tooling not in the standard catalog — register it from Integrations so it goes through the same governance path as every other connected source, rather than sitting outside Telara's policy and audit coverage.
Collectors may also list observed MCP servers as candidates. An observed identity is not a connected Integration: confirm or enter the endpoint and supply auth. Laptop stdio commands are review items, not one-click Register. Host Admin APIs that cannot list connectors report that gap; they do not report an empty MCP estate.
Checklist
Track connection readiness
The Integration Checklist lists outstanding setup items across your connected integrations — things worth reviewing before you'd call an integration fully configured. Dismiss an item once you've addressed it, or once you've decided it doesn't apply.
Related guides

