In Omi Studio, each member of your organization can have personalized access to the studio’s features. Whether you want to grant full access to certain users or restrict the actions of others, managing permissions allows you to control who can do what in the studio.
⚠️ To access these settings, you must be an Owner or Administrator of your organization (For more information on the different roles: User roles and permissions in Omi).
Managing access and permissions for your organization’s members:
1. Go to the Organization settings by clicking on the name of your organization at the top left of the Omi page.
2. Then, go to the “Members” tab.
3. The settings will be made in the “Studio access” column.
There are two default levels of access permissions to the studio:
Full Access (Full): The user has access to all studio features.
Read-Only Access (View): The user can open the studio, but cannot modify anything in the scenes.
By default, all users will have access to all studio features.
If you want to restrict a user’s access to certain features:
You can create a “Role” by clicking on the dropdown menu and selecting “Create custom studio access”.
This will give you access to a list of all the options you can enable for this new role.
Les options suivantes peuvent être configurées :
Template: The type of templates the user can use.
Products: Actions the user can perform on private products.
Assets: Actions the user can perform on public assets.
Texturable assets: Which visual modifications can be applied to texturable assets.
Camera: Actions the user can perform on the camera.
Ratio: Allow or restrict the modification of the scene’s format.
Lights: Actions the user can perform on the scene’s lighting.
Scene Background: Which visual modifications can be made to the background.
Once a new role is created, you can assign it to other users with just one click!
💡Omi Tips💡
You can modify the permissions of an existing role without having to create a new one. The changes will be automatically applied to all members with that role.
If a member does not have the necessary rights to use a feature, it will appear to them as either missing or disabled (grayed out) when they attempt to access it.