-
Notifications
You must be signed in to change notification settings - Fork 1
Permissions
Damien Ayers edited this page Oct 31, 2013
·
4 revisions
In the beginning, there were no projects and we had global permissions for everything. The permissions were quite lax, giving anyone with an AustESE account permissions to view and edit pretty much anything.
Since adding projects, the repository module has support for project level permissions, but other modules are still using the lax global permissions.
Permission checks using function _check_permission_on_project() check the project specific permission if in the context of a project, and check the global permission if not in the context of a project.
- All permissions should have a global and a project specific permission. These are defined in each module.
- Only administrators should be given global permissions. They shouldn't be used for anything else.
- The project level permissions should be given sensible defaults to apply for all new projects
- These project level permissions can be overridden on a per-project basis
The permission checks should allow access to any administrator with the global permission, and if in the context of a project, anyone with that permission for that project.
| Module | Permission | Description |
|---|---|---|
| Alignment Tools | ||
| Edit Alignment | Allow users to create and edit alignments | |
| View Alignment | Allow users to view alignments | |
| Annotations | ||
| View Annotations | Allow users to view annotations | |
| Edit Annotations | Allow users to edit annotations | |
| Content Repository | ||
| Edit metadata | Allow users to create and edit ALL metadata in the content repository | |
| View metadata | Allow users to view ALL metadata in the content repository | |
| View Visualisations | Allow users to view visualizations | |
| Lightbox Tool | ||
| View light box | Allow users to view light box | |
| Reading Tool | ||
| View reading tool | Allow users to view reading tool |