Projectal contains permissions across all its features. This lets you control how each user of Projectal can access certain features and certain data in your Projectal.

For example:

• Sally is not allowed to view any financial information in Projectal
• John is not allowed to add, edit or delete staff records in Projectal
• Kelly is allowed to view projects and tasks, but is not allowed to edit or delete them
• Tom is only allowed to see the projects and tasks that he is working on.

Access Policies

An Access Policy is a set of permissions that you wish to apply to one or more users. They are a convenient way to collect and name a set the permissions for a group of users that log into your Projectal - typically based on their roles and responsibilities.

Once an access policy is created, then you can assign it to specific users and these users will be permitted to use Projectal as defined by the permissions in the access policy.

Example: You may want to create an access policy for all the artists within a creative studio so they are restricted to only access the tasks and projects that they are working on, and they are not permitted to see any financial information.

User Permissions

Each user has an access policy assigned to them and this defines their default set of permissions.  In addition, you can further customize the set of permissions for an individual user so that you match their Projectal permissions to exactly what they can and cannot see and do in Projectal.  These custom permission settings can be made in the Edit User screen and clicking the Customize button in the Access Policy section.

Example: Mary is an artist at a creative studio so she has been assigned the "ARTIST" access policy that defines her default set of permissions in Projectal.  However she is a trusted senior member of the team and has been given extra permissions beyond the typical artist so that she can perform her role.