Permissions
Display a list of permissions that letting a user read or write a record.
Last updated
Display a list of permissions that letting a user read or write a record.
Last updated
Permission is the act of letting a user read or write a record in Labii and .
. With top-down permission, the administrator or PI determines everyone's permissions in the company. As for the bottom-up, everyone controls the permissions of their folders/projects.
Permissions for Labii are controlled both at the organization and project level. Users can be assigned to the following roles:
is_administrator=true, administrators have full control over the account, can create projects and view all records.
is_readonly=true, then readonly users can only be granted Read permission
is_archived=true, archived users cannot access any data.
Permissions can be assigned to teams and individuals within a project:
permission=Admin, the project manager(s). Administrators can update project settings, create subprojects, and update member access.
permission=Edit, Team members and people with Edit permission to the project can add new records and edit existing records.
permission=View, Users with the View permission to the project can read the record.
Similar to the columns view, the permissions view can be accessed by simply clicking on the "Permissions" tab when a record is opened.
You can search teams by typing a keyword into the search bar in the permission list view, and then clicking Search. The search results can always be cleared by clicking the Clear button.
With the Filter function, you can limit the number of permissions displayed. You can do that by clicking All permissions and then selecting a filter from the dropdown. Here are a list of filters:
All permissions. Filter to display all permissions.
My permissions. Filter to display the permissions for you.
Write permissions. Filter to display the permissions can write.
Read permissions. Filter to display the permissions can read.
Permissions are generated automatically based on your permission settings at the organization and project levels. These are the typical events that trigger the generation of permissions.
New people added.
Change the is_administrator status of a people
Change is_archived status of a people
Change is_readonly status of a people
Change team members
Change is_archived status of a team
Delete team
Change is_archived status of a project
Change the team/people of the project member
Change the permission of the project member
New record is added
Change the projects of the record
According to your organization and project settings, permissions will be automatically updated. It is usually not recommended to add a record-level permission manually. After the above events are updated, permissions added manually could be wiped out.
The add permission function can be used if you need to give a temporary permission to a user. To add a permission, click "+Permission". This will display a form.
Select a people from the dropdown menu
Choose a Read or Write permission
Click Submit button
It is also not recommended to change the permissions manually. Any change in permission could be erased by any of the above events.
To update a permission temporarily:
Choose a new people from the dropdown or choose a new permission from dropdown.
Click Submit button.
Likewise, deleting permissions is not recommended. Deleted permissions will be restored when one of the above events occurs.
You can regenerate permissions if you believe that the current list of permissions is not accurate based on the organization's and project's permission settings. Click the "Regenerate Permission" button to regenerate permissions
Click the pencil icon () next to a people or a permission
The temporary permission you added can, however, be removed using this function. Click on the "delete" icon () next to a permission to remove it.
