Skip to main content
Back to Kantata.com Blog Tour Status

Project Permissions Defaults

By David Forsythe | Updated
Ask ChatGPT Ask Claude

The Account-level permissions in Kantata OX determine a user's overall privileges and the areas for which they have access. Every time a user joins a project, they are also assigned individual Project-level permissions that determine what access and abilities they have within each project.

 

Overview

The Account-level permissions in Kantata OX determine a user's overall privileges and the areas for which they have access. Every time a user joins a project, they are also assigned individual Project-level permissions that determine what access and abilities they have within each project.

These permissions can be adjusted on a project-by-project basis, but the initial Project Permissions that each member inherits are based on their Account-level permissions. You can map different project defaults for each Account Permission level—on both the Provider and Client side of the project—on the Project Permissions Defaults page to ensure that each member will enter a project with the proper access and permissions every time.

Note: These settings save time when used in combination with batch actions or integrations and reduce the effort required to verify that each member's Project-level permissions are set where you want them. Keep in mind that reconfiguring the Project Permissions Defaults does not affect the current Project-level permissions for members who have already joined a project.

Project Permissions Defaults page_fullscreen.png

At the top of the Project Permissions Defaults page, you’ll see the Providers and Clients tabs. You can quickly switch back and forth between the two tabs to perform actions for either the provider or client side of the project, such as adjusting permission levels and editing any additional permissions.

How to Map Project Permission Defaults

  1. Hover over Settings in the left navigation and select Project Permissions Defaults.

  2. Choose whether you want to map permissions for the Provider side or Client side of the project. The Provider tab is selected by default.

    Note: The Provider and Client tab labels will be different if you have set up custom team names.

    Provider_and_Client_tabs_Project_Permission_Defaults__1_.png

  3. In either tab, use the drop-down menus in the Project Permission column to select the permission you want to map to the corresponding Account Permission.

    Project Permissions Options in drop-down menu.png

    Note: The View permission levels only allows users to view project and task information, while the Edit permission levels allows users to make changes to this information, such as creating and updating tasks within a project.
    • For members on financial projects with the Account-level permissions of Project Creator, Collaborator, Collaborator (External), and Punch Clock, only the Project Permissions of View Tasks, Edit Tasks, View Time and Expenses, and Edit Time and Expenses are applicable. For example, a Collaborator mapped to Project Administrator by default will enter a financial project as Edit Time and Expenses and a non-financial project as Project Administrator. An invalid selection will default to the next lowest applicable Project Permission level.
    • On non-financial projects for any Account Permission level, only Edit Tasks and Project Administrator are applicable. For example, a Report Viewer mapped to the Edit Financials Project Permission level by default will enter a financial project as Edit Financials and a non-financial project as Edit Tasks. An invalid selection will default to the next lowest applicable Project Permission level.
    Note: The Collaborator (External) Account Permission is recommended for External Members in your Talent Network. This Account Permission is only available for Enterprise and Premier users.

  4. Use the selections in the Additional Access column to assign extra permissions to users with the corresponding Account-level permissions.

    Note: Account and Project Administrators have access to all Additional Access permissions and these permissions cannot be adjusted. Additionally, since clients don't track time and expenses or view private tasks, the View Time and Expenses, Edit Time and Expenses, and Set Task Privacy options aren't available in the Client tab.

    Additional Access Permissions in drop-down menu.png

  5. When you are finished making changes, click Save in the top-right corner of the screen.

  6. If you hover over an Information icon anywhere on the page, details about permission and access levels are shown.

External Project Participants

The Project Permissions Defaults also gives you the ability to limit access to information by configuring the default permissions and access for External Project Participants.

  • On the Provider side, External Project Participants are typically contractors.
  • On the Client side, External Project Participants are typically clients.

When you invite external project participants into your account, they do not require you to use a license seat, but the actions they can take are limited.

Note: If external project participants do not have an existing Kantata account, an account will be created for them that gives them a limited usage of Kantata tools and features. For more information, see Accessing a Project in Another Account.

 

Related Articles

By David Forsythe
Join us at Kantata!
Return to top