Fine-grain control in Albert
When you're granted named access to a project, that access comes with a project role. Your project role defines exactly what you can do at the module level, independent of your broader user class.
Albert has six project roles.
Project roles
Owner — Unrestricted access to all formulas and tasks in the project. Can add and edit collaborators and their roles.
Editor — Unrestricted access to all formulas and tasks in the project. Cannot add or edit collaborators.
Project Viewer, Task Editor — View access to formulas. Edit access to all tasks in the project.
View Only — View-only access to the project, tasks, notebooks, and worksheet. Can still fully interact with general tasks, which are Shared by default and accessible to any user with the appropriate role.
All tasks editor — No access to formulas. Edit access to all tasks in the project.
Property tasks editor — No access to formulas. Edit access to property tasks only.
Why Task Access Can Differ From Project Role
General tasks are Shared by default. Any user with the appropriate Albert role can fully interact with them — regardless of their project role. Even a View Only user can create and update general tasks.
Batch tasks inherit their class from the parent project. Project Viewer, Task Editor gets full edit access to batch data alongside their project visibility.
Property tasks have a fixed Restricted class. Project Viewer, Task Editor gets full access via their project role. View Only users get read-only access, since their project role doesn't include task editing.
This is also why All Tasks Editor and Property Task Editor exist as dedicated roles — they give contributors the specific object access they need without requiring broader project permissions.
Permissions by module
Full control = create, read, edit, delete, and manage access.
Edit = create, read, edit, delete.
Limited = create and read, or read and update depending on the module.
Read = view only.
Module | Owner | Editor | Project Viewer, Task Editor | View Only | All Tasks Editor | Property Task Editor |
|---|---|---|---|---|---|---|
Project | Full control | Edit | Limited | Read | Limited | Read |
Inventory - Formulas | Full control | Edit | Read | Read | — | — |
Batch instructions | Full control | Edit | Read | Read | — | — |
General tasks | Full control | Full control | Full control | Full control | Full control | — |
Property tasks | Full control | Full control | Full control | Read | Full Control | Full control |
Batch data | Full control | Edit | Edit | Read | Full control | — |
Lots | Full control | Edit | Limited | Read | Limited | Limited |
Attachments | Full control | Edit | Read | Read | Edit | Edit |
Notes | Full control | Edit | Read | Read | Edit | Edit |
Worksheet | Full control | Edit | Read | Read | — | — |
Notebook | Full control | Full control | Edit | Read | Edit | Limited |
Non-escalation of privileges
Project roles can never grant more than what a user's overall role permits. If a user's role does not include the ability to edit projects, being assigned as Owner at the project level will not grant them editing capabilities.
