Permissions |
|
Related readings |
Policies allow to create groups of users with specific rights: write or read.
They can be applied on projects, presets, repositories and collections to facilitate collaboration within the platform.
TABLE OF CONTENTS
Find the policies management tab
You can access the Policies tab from the settings, which are available at the bottom left of the screen.
Manage existing policies
On the Policies tab you will be able to see and manage existing policies.
If you are a sys admin, you will have access to all policies; if you are a user, you will have access to your own policies only.
For each policy, you have access to its name, description (if any), owner and creation date.
View a policy
You can access the details of a policy by clicking on it.
A modal will appear and you will be able to access the users and the permissions they were given through this policy.
Edit a policy
From the view, you can click on 'Edit' to unlock the modal.
You will be able to modify everything in the policy: its name, description, the users and their permissions.
You can add new users to your policy (those users need to be at least invited to the platform).
To be able to save your changes, you must have at least a policy name and one user with a permission.
Create a new policy
Policies can be created from general settings or objects settings (project, preset, provider, collection).
To create a policy on an object, you need to own the object or be a sys admin.
When creating a new policy, you will need to:
- add a name
- add a description (optional)
- add at least one user and set its permission
You have two levels of permissions:
- read: user will only have a read access to the object and won't be able to edit it
- write: user will have access to the object and will be able to edit it
Please be aware that once your policy is created, it's not effective yet.
It has to be applied on existing objects.
Apply a policy
You can access an object setting by clicking on the cogwheel at the right of the screen.
From there, you will be able to apply a policy, by creating one or selecting an existing one.
Once the policy is applied, users from the policies will have access to the object within the limitations of their permissions.
Without policy, only sys admins have access to objects, regular users won't be able to collaborate.
Action | Sys admin | User ‘write’ | User ‘read’ | User |
Can edit owned object | YES | YES | YES | YES |
Can edit owned object’s settings | YES | YES | YES | YES |
Can access not owned object | YES | YES | YES | NO |
Can edit not owned object | YES | YES | NO | NO |
Can edit not owned object’s settings | YES | NO | NO | NO |
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article