Oracle Cloud Infrastructure Documentation

API-Level Permissions for Routing Profiles

This page provides access and authorization information for the OCI Generative AI routing profile resource type.

For specific permissions for this resource type, review this page. For a list of all resource types available in OCI Generative AI, see User Access to Individual Resources.

Note

When an inference request uses a routing-profile OCID as the model, it also requires GENERATIVE_AI_ROUTING_PROFILE_READ in addition to the permission for the inference operation.

Resource Type

Resource Type for IAM Permissions Documentation Reference API Reference
generative-ai-routing-profile Managing Routing Profiles RoutingProfile

Inspect Permission

Grant user groups inspect permission to run the following operations:

  • GET ListRoutingProfiles

Read Permission

Grant user groups read permission to run the following operations:

  • GET ListRoutingProfiles
  • GET GetRoutingProfile

Use Permission

Grant user groups use permission to run the following operations:

  • GET ListRoutingProfiles
  • GET GetRoutingProfile
  • PUT UpdateRoutingProfile

Manage Permission

Grant user groups manage permission to run the following operations:

  • GET ListRoutingProfiles
  • GET GetRoutingProfile
  • PUT UpdateRoutingProfile
  • POST ChangeRoutingProfileCompartment
  • POST CreateRoutingProfile
  • DELETE DeleteRoutingProfile
Note

  • The manage permission includes all actions allowed by use, read, and inspect.
  • The use permission includes all actions allowed by read and inspect.
  • The read permission includes all actions allowed by inspect.
Tip

The generative-ai-routing-profile resource type is part of generative-ai-family. If you have permission to the family, you have the same permission for this resource type. For example: 
allow group <your-group-name> to manage generative-ai-family
in compartment <your-compartment-name>

1-1 Permissions for APIs

Note

We recommend using the higher-level IAM verbs, manage, use, read, and inspect, for a better user experience. For example, you might grant a user group permission to delete a resource, but if you don't also grant permission to list that resource, users might not find it.

If a use case requires access to only a specific API operation, you can use the individual permissions listed here.

generative-ai-routing-profile

Permission API Operation Operation Type Verb
GENERATIVE_AI_ROUTING_PROFILE_INSPECT ListRoutingProfiles GET inspect
GENERATIVE_AI_ROUTING_PROFILE_READ GetRoutingProfile GET read
GENERATIVE_AI_ROUTING_PROFILE_UPDATE UpdateRoutingProfile PUT use
GENERATIVE_AI_ROUTING_PROFILE_MOVE ChangeRoutingProfileCompartment POST manage
GENERATIVE_AI_ROUTING_PROFILE_CREATE CreateRoutingProfile POST manage
GENERATIVE_AI_ROUTING_PROFILE_DELETE DeleteRoutingProfile DELETE manage

For example, the following two policies are the same:

allow group <your-user-group> to manage generative-ai-routing-profile
in compartment <your-compartment-name>
allow group <your-user-group> to
{GENERATIVE_AI_ROUTING_PROFILE_INSPECT, GENERATIVE_AI_ROUTING_PROFILE_READ, GENERATIVE_AI_ROUTING_PROFILE_UPDATE, GENERATIVE_AI_ROUTING_PROFILE_MOVE, GENERATIVE_AI_ROUTING_PROFILE_CREATE, GENERATIVE_AI_ROUTING_PROFILE_DELETE}
in compartment <your-compartment-name>