Integrations connect the tools your team already uses, such as ServiceNow, Jira, Dynatrace, and Confluence, to Luumen. Once connected, LuumenAI can pull context from those systems into a session and (where you allow it) act in them. Tickets, logs, and documentation are all available in one place, alongside the servers you manage.
Every integration is governed: administrators control what LuumenAI can and cannot do in each system, actions are attributed to the person they were performed for, and activity is recorded in the audit log.
How Integrations Governance Works
These rules apply to every integration:
Permissions are set per tool, not per integration. Every tool inside an integration is set to:
Full access
Ask for approval
Not enabled
For example: ServiceNow reads can be open while ServiceNow writes require approval.
Policies enforce checks beyond tool permissions. A policy is a rule that must be satisfied before LuumenAI carries out an action, such as requiring an approved change ticket before a change is made. If the condition is not met, LuumenAI rejects the request and states why.
Members act through their own accounts. Each member connects their own account, and actions carry that person's identity into the external system. Luumen stores an opaque reference to the connection, not the credential itself.
When LuumenAI reaches a tool that is set to Ask for approval, the conversation shows a card with the exact call it wants to make, the supporting evidence, and a risk level. The action waits until it is approved.
Where Enabled Integrations Live
Enabled integrations can be found in Integrations in the left navigation.
Owners and Admins enable integrations from Settings then Integrations. That is where the full library lives: browse or search the catalog, choose which workspaces an integration is available in, and set what each of its tools can do.
Requests from members appear there under Pending Requests when there is a request waiting.
Enabling Integrations
To enable integrations Admin and Owner roles can go to Settings then Integrations to choose which integrations to enable, and set tool permissions and workspace scope. They can also review member requests for integrations under Pending Requests
Integrations Actions by Role
Action | Member | Admin | Owner |
Browse the directory | Yes | Yes | Yes |
Connect your own account to an enabled integration | Yes | Yes | Yes |
Request an integration that is not enabled | Yes | Yes | Yes |
Enable an integration for the organization or specific workspaces | No | Yes | Yes |
Set tool permissions | No | Yes | Yes |
Review and enable member requests | No | Yes | Yes |
Disable an integration | No | Yes | Yes |
Integration Availability by Plan
Most integrations are available on every plan including Free.
A small set of connectors and integrations are available only on Enterprise plans:
The SAP connectors (SAP BTP and SAP BTP Admin)
Dynatrace
ServiceNow
For more information see Enterprise connectors.
Integrations Scope and Limitations
Integrations do not discover servers. Hosts come from Add a host or Import hosts from a CSV, never from a monitoring or ticketing tool.
A tool with no permission set is off. If an integration adds a new tool after you enabled it, LuumenAI cannot use that tool until an Admin gives it a permission.