Skip to main content
Account Roles & Project Permission Sets

Understand the relationship and differences between Account Roles (Org Roles) and Project Permissions available and how they differ.

Updated over a week ago

Overview

What's the difference between account roles and project permissions in Pegasus?

An Account Role establishes the relationship or access level a user within your organization has and their ability to modify and manage global account settings, project configurations & data, users, licenses, and billing configurations within Pegasus. In short account roles define your users company-level permissions.

Project permission sets define a user's relationship to a given project(s) in Pegasus. Project permissions can also be established on a per-project basis for each user. Users can be a Manager permission set on Project A while having the View-only permission set on Project B.

In short, Account Roles define which users have access to managing company-level data and settings. Project permission sets define a user's Read/Write abilities at the project level.

Account Roles

Your account's company data and preferences includes licenses, projects, list data, report templates, and more. Managing company data is performed from the Admin Console.

Determining who can manage this information is equally as important. That's where roles come into play and every user in Pegasus has an account role. The types of account roles are (in order of hierarchy):

  1. Owner: By default, the first user created in your organization's Pegasus environment is the Owner. The Owner has control over everything in your account including licenses & billing, users, project assignments, list management, template management.

  2. Admin: Admins also have access to the Admin Console and have similar access/control as the Owner role, however they cannot modify users that are Owner roles, nor do they have access to billing information and modification.

  3. Member: This is anyone in your organization that you invite to as a user in Pegasus under your account environment. However, they do not have access to the Admin Console.

  4. Guests: External users that are not in your organization. Guests may have permissions to access and manage project data in your account, but are unable to view or manager company data.

Manage user account roles from the Users page in the Admin Console.

Project Permissions

📘RESOURCE

View our Pegasus Permission Set Matrix PDF below for a detailed breakdown of permission sets and what each can do on a project:

Project permission sets are assigned to each user at the project level. By default, Pegasus accounts have three project permission sets available:

  1. Manager: This permission set gives a user full-access to a project. With the Manager permission you can modify Project Setup Information, Contract information, Settings, Manage users access & permissions, Review Reports, and can create any project record/document.

  2. Field: Intended for users working in the field, this permission set grants View abilities for all sections in a project. Create or Write abilities are limited to Fields Reports, Tasks, Photos, Documents, and Plan Set Uploads.

  3. View: Limited to read-only for all sections. Can export and view documents as needed.

User Project Permission sets are managed at the project-level from each project's Project Settings page.

If you are assigned the Owner or Admin account role you can also manage a user's permission set for multiple projects from the Projects page in the Admin Console.

⚙️CUSTOMIZE PEGASUS

Configure Pegasus for your team with custom permission sets, account roles, and more...

Select the button below to schedule a meeting with our Customer Success team to discuss your business requirements:

Did this answer your question?