> For the complete documentation index, see [llms.txt](https://docs.prismacloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.prismacloud.io/content-collections/connect/connect-cloud-accounts/onboard-your-oci-account/permissions-required-for-oci-tenant-on-prisma-cloud.md).

# Permissions Required for OCI Tenant on Prisma Cloud

In order to monitor your OCI resources, Prisma Cloud requires access to an OCI tenant that enables authentication between Prisma Cloud and OCI.

You must have administrator access to an OCI tenant to enable read permission for Prisma Cloud.

Prisma Cloud uses the Terraform file to create a group and add a user to the group. It also creates a policy and applies the policy to that group. Prisma Cloud needs read permissions for all the supported services.

OCI has a limit of 50 policy statements that can be added to a single IAM policy, but Prisma Cloud supports over 100 policy statements. To successfully ingest all of the OCI APIs, you do not need to request a [service limit increase](https://docs.oracle.com/en-us/iaas/Content/General/Concepts/servicelimits.htm) from OCI on the policy statements. However, you must update your existing Terraform file as outlined in [Update Permissions on an Onboarded OCI Account](https://docs.prismacloud.io/content-collections/connect/connect-cloud-accounts/onboard-your-oci-account/update-oci-permissions.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.prismacloud.io/content-collections/connect/connect-cloud-accounts/onboard-your-oci-account/permissions-required-for-oci-tenant-on-prisma-cloud.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
