Skip to main content

Project Roles

Defining, customizing, and assigning roles to your team members, ensuring clarity in responsibilities and permissions.

Carmela Flores avatar
Written by Carmela Flores
Updated over a week ago

Overview

INGENIOUS.BUILD simplifies how Project Roles work in your workspace. Project Roles no longer control permissions — those are now fully managed through Account Types. Instead, Project Roles act as identifiers used to organize team members and define approval routing for workflows.


Prerequisites

You must be an Administrator or have correct permissions to access an individual Employee's page to make the edits described in this article.


Process

What’s Changed

  • No more permissions tied to Project Roles:
    Project Roles no longer grant or restrict access. All permission management now happens through Account Types instead.

  • Roles are now identifiers:
    You can use these roles to organize your team members and define approval routing, such as for lists, templates, or financial workflows.


Creating Project Roles

You can create custom Project Roles within your workspace.

  1. Navigate to the Employees list page.

  2. Click the three dots on the upper right of your screen, then click Project Roles.

  3. Click Create Role.

  4. Enter the role name (for example, “Designer,” “Project Coordinator,” or “Reviewer”).

  5. Click Save.

Note: Project Roles are currently name-only. You don’t assign permissions at this stage.


Custom Account Types

As part of this update, previous Project Role permissions have been merged into Account Types.

  • Workspaces that used custom Project Role permissions before this change may now see additional custom account types, created to maintain backwards compatibility.

  • Workspaces that did not use Project Role permissions will only see the four standard account types (Admin, BizOps, Leadership, Standard).

This ensures all existing user access settings remain consistent after the update.


Assigning Project Roles to Users

  1. To assign a role to an employee, select the employee from the Employee list page, then click Edit Employee.

  2. Under Account Information, you will see an option to assign a Default Project Role.

  3. You can also assign a Additional Project Roles.

    1. These additional roles will allow the Employee's project role to be changed within a Project Directory to any of the selected additional project roles by a Lead Project Manager or Executive.

    2. In this field, you can select as many additional roles as necessary.

  4. Click Save.

These assignments will help when setting up approval workflows, ensuring users are routed correctly based on their designated roles.


Using Project Roles in Approval Workflows

When configuring approval workflows for Lists and Templates or Financial Approvals, you can now assign approvers by Project Role rather than individual users.

  • Navigate to Lists & Templates → Financial Approval Workflows.

  • When adding an approval step, select a User/Role from the dropdown.

  • Choose the relevant Project Role from the list.

This setup allows your approval process to stay flexible — if a person’s role changes, the workflow will automatically adapt based on the updated assignment.


Changing Project Roles in a Project

Only user with the correct Custom Account Types or an Administrator Account Type will have the ability to change a project role from the default to an additional project role within the Project Team/Directory.

  1. Navigate to a project and select the Project Team/Directory module.

  2. Select one of the dropdowns next to the indented Employee's name.

  3. Select one of the additional roles they have been assigned.

    1. If no options exist in the drop down they will need to be assigned additional project roles in their Employee page by an Administrator or equivalent account type.


By setting up clear Project Roles and assigning them properly, your workspace can streamline approval workflows, improve visibility across teams, and maintain flexibility as project responsibilities evolve.

Did this answer your question?