Skip to main content
Use integration capabilities to see what Oleria can read and manage in a connection, which actions are ready, and what you may need to change. To view capability details, go to Integrations -> Connected, select an integration, and select View details.
Capability details describe the connected integration instance in your workspace. They can change after you update connection permissions or Oleria evaluates the integration again.

​
How to read the capability details

Capability details have two sections:
  • Integration depth shows the integration’s Depth, a Description of that depth, the Granted permissions Oleria can confirm for this connection, and when the details were Last evaluated.
  • Capabilities and operation readiness is a table of the read coverage and actions reported for this connection, with each one’s Status, Required permissions, and Customer guidance.
Depth describes the integration’s maximum coverage. It does not mean every action is ready for every connection. Readiness is specific to the connection and can depend on permissions or integration configuration.

​
Integration depth

The depth label summarizes the type of governance coverage Oleria can provide through the integration. The depth label does not describe the permissions currently granted to Oleria. An integration with Resource-level governance can still have actions that aren’t ready for a specific connection.

​
Operation status

The table shows the read coverage and actions the integration reports as supported. Their status tells you whether they are ready for this connection. Oleria doesn’t list actions that an integration doesn’t support. If an expected action is missing, don’t assume that granting more permissions will make it available.

​
Read and write operations

Labels vary by integration. Common read-coverage and action labels include: Some integrations also report other actions, such as disabling user accounts or revoking resource access. Read coverage does not imply that related actions are available for the same integration.

​
Required and granted permissions

Required and granted permissions answer different questions:
  • Required permissions are permissions the integration reports for an action. Some integrations don’t report this information, so a blank table cell doesn’t mean no permissions are required.
  • Granted permissions are permissions Oleria can confirm for the connected integration.
  • Missing permissions are required permissions that Oleria can confirm aren’t granted. When Oleria can compare required and granted permissions, the Customer guidance column can list what is missing.
If an integration reports granted permissions but none are granted, Oleria shows No permissions granted. If an integration doesn’t report granted permissions, Oleria shows Permission status not available for this integration. This means Oleria can’t confirm which permissions the connection has; it doesn’t mean that no permissions are granted.
When permission status is unavailable, Oleria can’t identify which required permissions are missing. Follow Customer guidance to verify required permissions or enable the action in the integration configuration.

​
Empty states

The capability section uses different messages for different situations: If you recently changed permissions in the source system, follow the Customer guidance in the table. Reconnect the integration when prompted, then check the details after the next sync. If you see We couldn’t load capability data for this integration. Please try again later., retry later. This message indicates a loading error, not that the integration has no capabilities.

​
Contact us

For questions about the capabilities shown for your integration, contact support@oleria.com.