Custom Model Policies
Before using Language for custom model training, have your tenancy administrator set up the following policies:
Give Users Access to Language
Administrators can create a group and add users to this group for accessing Language resources.
Type of access: Any user added to this group can list, create, update, and delete all Language resources in the specified compartment:
allow group <group-name> to manage ai-service-language-family in compartment <some-compartment>
To allow users to manage Language resources in all compartments in the tenancy, replace compartment name with tenancy:
allow group <group-name> to manage ai-service-language-family in tenancy
To allow all users in the tenancy to use Language resources in the tenancy:
allow any-user to use ai-service-language-family in tenancy
To allow all users in the compartment to use Language resources in the compartment:
allow group <group-name> to manage ai-service-language-family in compartment <compartment-name>
To restrict users access to specific Language resources, see Language Policies.
Ensure that any policy that you create complies with your company guidelines. Your policies remain when Language resources are deleted. As a best practice, delete associated policies when deleting the Language resources.
Required Object Storage Policies
To give custom models access to Object Storage, first include your Language resources in a dynamic group. Then, create policies to grant the dynamic group access to Object Storage resources.
To use with a dynamic group set a name:
ALL {resource.type='ailanguagemodel'}
Then use a dynamic group policy:
allow dynamic-group <dynamic-group-name> to manage objects in tenancy