IAM Policies for OCI Generative AI
You can get permission to access OCI Generative AI resources through OCI Identity and Access Management (IAM) policies.
If you're not member of the Administrators group, ask your administrator to assign you the least privileges that are required to perform your responsibilities by reviewing the following sections.
If you need help writing IAM policies, see IAM Policies and Policy Syntax.
Give User Groups Access to All Generative AI Resources
To give user groups permission to all Generative AI resource types, you can use the aggregate generative-ai-family resource types in an IAM policy permissions.
We recommend giving permission to all Generative AI resources only to administrators or user groups working on sandbox environments.
-
Grant access to
manageall the Generative AI resources in the tenancy with the following IAM policy:allow group <your-group-name> to manage generative-ai-family in tenancy - Grant access to
manageall the Generative AI resources in a specified compartment with the following IAM policy:allow group <your-group-name> to manage generative-ai-family in compartment <your-compartment-name>
Generative AI Individual Resource Types
Instead of giving a group of users access to all Generative AI resources, you can fine grain the access to the resource-type level. The following table lists all the resource-types included in the generative-ai-family resource type. Select the topics in the next section for the types of permissions for each resource type.
| Aggregate Resource Type | Included Individual Resource Types |
|---|---|
generative-ai-family
|
|
User Access to Individual Resources
Model Inference and Management
- Limiting Model Inference Access with IAM Policies
- API-Level Permissions for Chat
- API-Level Permissions for Embeddings
- API-Level Permissions for Custom Models
- API-Level Permissions for Imported Models
- API-Level Permissions for Dedicated AI Clusters
- API-Level Permissions for Endpoints
- API-Level Permissions for Private Endpoints
- API-Level Permissions for API Keys
- API-Level Permissions for Work Requests
- Object Storage Permissions
Data and Project Resources
- Permissions for Using and Managing Semantic Stores for NL2SQL
- API-Level Permissions for Semantic Stores
- API-Level Permissions for Projects
- API-Level Permissions for Vector Stores
- API-Level Permissions for Vector Store Connectors
- API-Level Permissions for Enterprise AI NL2SQL
- API-Level Permissions for Containers
- API-Level Permissions for Files