> ## Documentation Index > Fetch the complete documentation index at: https://docs.oleria.com/llms.txt > Use this file to discover all available pages before exploring further. # Integration capabilities > See what Oleria can read and manage in a connected integration, which actions are ready, and what permissions may be missing. 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**. > [!NOTE] > > 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. | Depth | What it means | | :- | :- | | **Resource-level governance** | Oleria can read and manage this integration's resources, users, groups, and roles, and can read audit logs. Resources can include objects such as files, repositories, buckets, or records, depending on the integration. | | **Identity governance** | Oleria can read and manage users, groups, and roles for this integration, and can read audit logs. | | **Identity governance (no audit logs)** | This level applies to integrations that use System for Cross-domain Identity Management (SCIM) only. Oleria can read and manage users, groups, and roles. Audit logs aren't available for this integration type. | | **Coming soon** | Capability details aren't available for this integration type yet. This status describes capability reporting, not a missing permission. | 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. | Status | Meaning | What you can do | | :- | :- | :- | | **Available** | The integration supports the action, and it is enabled for this connection. | No change is needed. | | **Needs permission** | The integration supports the action, but it isn't ready for this connection. | Follow the **Customer guidance** in the table. It may ask you to grant missing permissions or enable the action in the integration configuration. | 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: | Operation | What it covers | | :- | :- | | **Read users** | Read user accounts from the integration. | | **Read groups** | Read groups and their membership from the integration. | | **Add / remove group membership** | Add a user to a group or remove a user from a group. | | **Read roles** | Read roles and role assignments from the integration. | | **Assign / unassign role** | Assign a role to a user or remove a role assignment. | | **Read applications** | Read applications exposed by an identity provider or a resource-level integration. | 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. > [!NOTE] > > 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: | Message | What it means | | :- | :- | | **Oleria hasn't finished evaluating this integration yet, check back after the next sync.** | Oleria hasn't produced capability details for this connection yet. Check again after the next sync. | | **No actions have been defined for this integration yet.** | Oleria has no supported operation rows to show for this integration. This is different from capability details that haven't been evaluated yet. | 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. ## Related documentation * [Integrations overview](https://docs.oleria.com/integrations/overview.md) * Find setup and permission instructions in [All integrations](https://docs.oleria.com/integrations/directory.md). ## Contact us For questions about the capabilities shown for your integration, contact [support@oleria.com](mailto:support@oleria.com). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.