User Permissions Matrix - Web
- Last updated
- Save as PDF
The following reference page is a comprehensive breakdown of all user actions and the specific user permissions (Read Only, Standard, and/or Admin) that are required to be able to perform that action. Since certain tools are available at both the Company and Project levels, be sure to select the appropriate navigational hyperlink below.
Company Level
Admin (Company Level)
The following table highlights which user permissions are required to perform the described user action.
- Indicates that the task can only be completed when Procore is configured to use the Company level ERP Integrations tool. See ERP Integrations.
* The user must have 'Admin' level permissions on both the Company and Project level Admin tools.
Directory (Company Level)
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the tutorial.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Company level Directory tool?
Important
A user who is granted 'Admin' level permissions on the Company level Directory tool is automatically granted 'Admin' permissions across all Project level and Company level tools.Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Company to the Company Directory |
|
|
![]() |
||
Add a Distribution Group to the Company Directory |
![]() |
||||
Add a User Account to the Company Directory |
|
|
![]() |
Users with granular permissions have the following limitations:
|
|
Add an Existing User to Projects in Your Company's Procore Account |
|
|
![]() |
Users with granular permissions can only add other users to projects that they have already been added to. |
|
Add Insurance for a Vendor in the Company Directory |
|
|
![]() |
||
Allow Users to Create New Projects |
![]() |
||||
Assign a Company Permission Template to a User in the Company Directory |
|
|
![]() |
Users with granular permissions have the following limitations:
|
|
Assign a Default Project Permissions Template to a User in the Company Directory |
|
|
![]() |
Users with granular permissions can only assign users to assignable default project permissions templates. | |
Assign a Project Permissions Template to a User in the Company Directory |
|
|
![]() |
Users with granular permissions have the following limitations:
|
|
Change a User's Permissions to Company Tools in the Company Directory |
|
|
![]() |
Users with granular permissions can only grant access to Company tools by assigning users to assignable company permissions templates. |
|
Change a User's Project Permissions Template in the Company Directory |
|
|
![]() |
Users with granular permissions have the following limitations:
|
|
Configure Advanced Settings: Company Directory |
![]() |
||||
Customize the Column Display in the Directory Tool |
![]() |
![]() |
![]() |
||
Deactivate a Company in the Company Directory |
![]() |
||||
Delete a Distribution Group from the Company Directory |
![]() |
||||
Designate an Insurance Manager for Your Procore Company |
|
|
![]() |
||
Download a vCard for a User Account in the Company Directory |
![]() |
![]() |
![]() |
||
Download a Company or User Import Template |
![]() |
![]() |
|||
Edit a Company in the Company Directory |
|
|
![]() |
||
Edit a Contact in the Company Directory |
|
|
![]() |
||
Edit a Distribution Group in the Company Directory |
![]() |
||||
Edit a User Account in the Company Directory |
|
|
![]() |
Users with granular permissions have the following limitations:
|
|
Export the Company Directory to CSV or PDF |
![]() |
![]() |
![]() |
||
Inactivate a Batch of Companies in the Company Directory |
|
|
![]() |
||
Inactivate a Batch of User Accounts in the Company Directory |
|
|
![]() |
||
Inactivate a Contact in the Company Directory |
|
|
![]() |
||
Inactivate a Company in the Company Directory |
|
|
![]() |
||
Invite a Batch of Procore Users to Join a Company's Procore Account |
|
|
![]() |
||
Invite or Re-invite a User to Procore |
|
|
![]() |
||
Merge Companies |
![]() |
||||
Reactivate a Batch of Companies in the Company Directory |
|
|
![]() |
||
Reactivate a Batch of User Accounts in the Company Directory |
|
|
![]() |
||
Reactivate a Contact in the Company Directory |
|
|
![]() |
||
Reactivate a Company in the Company Directory |
|
|
![]() |
||
Reactivate a User in the Company Directory |
|
|
![]() |
||
Remove an Existing User from Projects in Your Company's Procore Account |
|
|
![]() |
Users with granular permissions can only remove other users from projects that they are a part of. | |
Remove Company Insurance |
|
|
![]() |
||
Request Company and People Imports |
![]() |
![]() |
|||
Respond to a 'Welcome to Procore' Email |
![]() |
![]() |
![]() |
![]() |
|
Search and Filter the Company Directory |
![]() |
![]() |
![]() |
||
Send a Company or User Import Template to Procore |
![]() |
![]() |
|||
Send a Procore Company to ERP Integrations for Accounting Acceptance |
![]() |
||||
Set Tenderer Information at the Company Level |
|
|
![]() |
||
Switch Between Views in the Company Directory |
![]() |
![]() |
![]() |
||
Update Expiring Insurance for a Vendor in the Company Directory |
|
|
![]() |
||
View Company Details in the Company Level Directory Tool |
|
|
![]() |
||
View User Details in the Company Level Directory Tool |
|
|
![]() |
Documents (Company Level)
The following table highlights which user permissions are required to perform the described user action.
1 Users with 'Standard' level permissions can only check in a file that they have checked out.
2 Users with 'Read Only' or 'Standard' level permissions can only access 'Private' files and folders if they have been granted access to the file or folder.
3 Search results will only include the documents the user performing the search has access to.
ERP Integrations
Integration by Procore | Integration by Ryvit | Sage 100 Contractor | Sage 300 CRE | QuickBooks
Sage 100 Contractor
Inspections (Company Level)
The following table highlights which user permissions are required to perform the described user action.
Permissions
The following table highlights which user permissions are required to perform the described user action.
1 Users with the appropriate permissions can assign company permissions templates to users in the Company level Directory tool when creating or editing a user account. See Add a User Account to the Company Directory and Edit a User Account in the Company Directory.
2 Users with the appropriate permissions on the Company level Directory tool can assign a default project permissions template to a user when creating or editing the user's Directory record. See Add a User Account to the Company Directory and Edit a User Account in the Company Directory.
3 Users with the appropriate permissions on the Company level Directory or Project level Directory tools can change a user's project permissions template on a specific project when adding the user to a project or editing the user's Directory records. See Add a User Account to the Project Directory, Edit a User Account in the Company Directory, and Edit a User Account in the Project Directory.
4 Users with the appropriate permissions can create project specific permission templates in the Project level Directory tool. See Create a Project Specific Permissions Template from the Project Directory.
Planroom
The following table highlights which user permissions are required to perform the described user action.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Configure Advanced Settings: Planroom | ![]() |
|||
Download Tender Documents | * | ![]() |
![]() |
![]() |
Reading Your Tender Package | * | ![]() |
![]() |
![]() |
Submit a Tender | * | ![]() |
![]() |
![]() |
View All Tender Packages in the Company | ![]() |
|||
View Tender Package (that they have access to) | * | ![]() |
![]() |
![]() |
View the Planroom Tool | * | ![]() |
![]() |
![]() |
*Tenderers need to be added to the Company level Directory in order for you to invite them to tender on a project. Once a company is added to a tender package, tenderers within that company will automatically be given access to the Planroom upon logging into Procore.
Portfolio
The following table highlights which user permissions are required to perform the described user action.
1 This task requires 'Admin' level permissions on the Company level Directory tool, or 'Read Only' or higher on the company's Portfolio tool with the privilege to create new projects. See Allow Users to Create New Projects.
2 This task requires 'Admin' level permissions on the Company level Directory tool OR 'Admin' level permissions on the Project level Admin tool for the project template. See Add an Existing User to Projects in Your Company's Procore Account.
3 Only users who were added to the Project level Directory for one or more inactive projects can view those inactive projects in the company's Portfolio tool.
Prequalification Portal
The following table highlights which user permissions are required to perform the described user action.
Note: Users will only have access to prequalification forms that they have been invited to collaborate on.
Users need to be added to the Company level Directory in order for you to invite them to prequalify. Once they are invited to prequalify, they will automatically be given 'Read Only' permissions on the Prequalification Portal tool.
Prequalifications
The following table highlights which user permissions are required to perform the described user action.
Users need to be added to the Company level Directory in order for you to invite them to prequalify. Once they are invited to prequalify, they will automatically be given 'Read Only' permissions on the Prequalification Portal tool.
1 'Standard' level users can view all categories response data except for Financials.
2 'Standard' or 'Admin' level permissions are required on the company's Directory tool to complete this function.
3 'Standard' level users can perform functions on items they have created.
Programs
The following table highlights which user permissions are required to perform the described user action.
* These actions require the displayed permissions on either the Company or Project level Admin tool. |
Reports (Company Level)
The following table highlights which user permissions are required to perform the described user action.
1 This task can only be completed by the report's creator.
2 Report-specific permissions may apply.
3 This task can be completed by users with access to the report as its creator or a viewer (if shared).
4 This task can only be completed by the creator of a report's visuals.
5 The Company Level Open Submittals Report must be enabled on the backend by Procore.
6 This task can only be completed by the dashboard's creator.
Schedule (Company Level)
The following table highlights which user permissions are required to perform the described user action.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Create Calendar Items | ![]() |
![]() |
||
Configure Advanced Settings: Company Level Schedule | ![]() |
|||
Search Project Schedules | ![]() |
![]() |
![]() |
|
View All Schedule Tasks (for projects they have access to) ![]() |
![]() |
![]() |
![]() |
|
View All Scheduled Tasks for All Projects | ![]() |
Timecard
The following table highlights which user permissions are required to perform the described user action.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Configure Advanced Settings: Timecard | ![]() |
|||
Configure Your Company For The Timecard | ![]() |
|||
Create a Timecard 1 | ![]() |
![]() |
||
Edit a Timecard 1 | ![]() |
![]() |
||
Export a Timecards Report | ![]() |
|||
Delete a Timecard 1 | ![]() |
![]() |
||
View the Change History of a Timecard | ![]() |
|||
View a Timecard 1,2 | ![]() |
![]() |
![]() |
1 Users with 'Standard' level permissions can view, create, edit and delete their own timecards.
2 Users with 'Read Only' level permissions can only view their own timecards.
Timesheets (Company Level)
The following table highlights which user permissions are required to perform the described user action.
1 'Admin' users on the project's Timesheets tool can perform functions on all time entries.
2 'Standard' users on the project's Timesheets tool can perform functions on time entries that they have created.
3 'Admin' level permissions are required on QuickBooks® Desktop Desktop to complete this function.
4 'Admin' level permissions are required on Sage 300 CRE® Desktop to complete this function.
5 Transferring time entries from Procore does NOT require the Procore + QuickBooks® Connector and/or Procore + Sage 300 CRE® Connector.
6 'Admin' users on the Company's Timesheets tool who have been added to the project can perform functions.
7 'Admin' users on the Company's Timesheets tool can perform functions on all time entries.
Workforce Planning
To access the Workforce Planning tool, users must have 'Read Only' permissions or higher for the Workforce Planning tool in the Company level directory. Their ability to take actions within the Workforce Planning tool are managed by these additional granular permissions.
Project Level
Admin (Project Level)
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
: Indicates that the task can only be completed when Procore is configured to use the Company level ERP Integrations tool. See ERP Integrations.
1 You must have 'Admin' permissions to the Project level tool that you want to extract data from.
2 The Project level Timesheets tool must also be enabled.
3 The Project level Admin tool's Permissions Table page only allows permissions to be changed for users who do not have a permission template assigned to them and are not Company level Admins. All other permissions must be managed in the Project and Company Level Directory tools.
Tendering
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
1 Users must also have 'Admin' level permission to the Project level Directory tool to complete this function.
Note: In projects updated to Tender Management Enhanced Experience, this action can also be performed by users with 'Read Only' or higher permissions to the Project level Directory tool with the 'Create and Edit Companies' AND 'Create and Edit Users' granular permissions.
2 Users with 'Standard' level permission can view Tender Notes by default.
3 Users must also have 'Read Only' or higher permissions to the Documents, Drawings, or Specifications tools. Users can only view and update items that they have access to.
4 Users with 'Read Only' or higher level permissions to the project's Tendering tool AND added to the Tendering CC Group can complete this function.
5 These tasks are performed by tenderers using the Company level Planroom tool. See Planroom.
Budget
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
: Indicates your company's Procore account must be configured to work with an integrated ERP system.
1 This task also requires 'Admin' permissions on the project's Client Contracts, Funding, or Prime Contracts tool.
2 Also requires 'Admin' permissions on the Company level Reports tool.
3 These steps require that your company has enabled the ProEst by Procore integration.
4 The Reports tool must be an active Project Tool. See Add and Remove Project Tools.
Change Events
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action that is supported by Procore for Android or Procore for iOS.
1 These tasks also require additional permissions on other tools in Procore. For more information, view the "Things to Consider" section in the tutorial for that action.
2 Users with 'Standard' permission can only delete the change events they create.
3 Users with 'Standard' permission can only edit the change events they create.
4 Users also need 'Standard' or 'Admin' level permissions on the Commitments tool.
5 Collaborators can submit a quote only if they receive an RFQ email notification. To be eligible to receive an email, the collaborator's user account must be granted 'Standard' level permissions on the project's Commitments tool and designated as the 'Assignee' on the RFQ. For details, see Assign and Send an RFQ to a Collaborator and Submit a Quote as a Collaborator.
Change Orders
The following table highlights which user permissions are required to perform the described user action.
1 To perform this task as a user with 'Standard' level permissions on the Change Orders tool, you must be the 'Designated Reviewer' on the change order. See Create a Commitment Change Order.
2 Users with 'Admin' level permissions on the project's Change Orders tool must be granted additional tool permissions: (1) To edit a Commitment Change Order (CCO), 'Admin' level permissions on the project's Commitments tool, and/or (2) to edit a Prime Contract Change Order (PCCO), 'Admin' level permissions on the project's Prime Contracts tool. Additional factors may also apply. For details, see Edit a Change Order.
3 Users with 'Read Only' or 'Standard' level permissions on the project's Change Orders tool can view change orders for contracts not marked 'Private.' If a contract is marked 'Private,' users must be added to the 'Private' drop-down list on the contract.
4 Users with 'Admin' level permissions to the project's Change Orders tool can also view change orders for contracts not marked 'Private'. If a contract is marked 'Private', users either be (A) added to the 'Private' drop-down list on the contract or (B) assigned 'Admin' level permissions on the Commitments and/or Prime Contracts tool.
Admin Tool
The following table highlights which user permissions are required in the project's Admin tool to perform the described user action.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Enable the Change Orders Tool | ![]() |
Commitments
The following table highlights which user permissions are required to perform the described user action.
: Denotes an action that is supported in Procore's iOS and/or Android mobile application.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
: Indicates your company's Procore account must be configured to work with an integrated ERP system.
1 To perform this task, downstream collaborators should be designated as an invoice contact on the commitment. See Add Invoice Contacts to a Commitment.
2 Also requires a DocuSign© account.
3 Users must have 'Read-Only' or 'Standard' permissions on the project's Commitments tool. Users must also be added to the Private drop-down list for that commitment or must be designated as an Invoice Contact. See Add Invoice Contacts to a Purchase Order or Subcontract.
4 Commitments synced with an integrated ERP system cannot be deleted until they are unlinked. See Delete a Commitment Synced with QuickBooks® Desktop and Delete a Commitment Synced with Sage 300 CRE®.
5 Users with 'Admin' permissions on the project's Commitments tool can export a commitment as either a PDF or a DOCX file. Users with 'Standard' or 'Read-Only' permissions on the project's Commitments tool can export a commitment to the PDF file format if they have been granted access to the purchase order or subcontract via the Private drop-down list and the 'Allow These Users to See SOV Items' check box is enabled.
6 Users with 'Read-Only' permissions on the Commitments tool can perform these procedures if they are also listed in the Private field under the commitment's General tab.
7 Users with 'Read only' and 'Standard' permission (and who have NOT been assigned the granular permission detailed in the table) must also be a member of the 'Private' list.
8 Also requires 'Standard' or 'Admin' permission on the project's Change Events tool.
9 Users with 'Standard' level permissions on the project's Commitments tool can create PCOs when they are added to the 'Private' drop-down list and the 'Allow Standard Level Users to Create PCOs' configuration must be selected.
10 The invoice must be in the 'Draft' or 'Revise and Resubmit' status for a user with 'Standard' level permissions to delete it.
Coordination Issues
The following table highlights which user permissions are required to perform the described user action.
1 Users will also need 'Standard' or 'Admin' permissions on the RFIs tool.
2 'Standard' users can only edit, reopen and delete coordination issues that they created.
3 'Standard' users can only mark a coordination issue as complete if they are listed as the Assignee.
4 Users can only edit or delete comments that they have added.
5 Users can only reassign a coordination issue to another user if they are currently listed as the Assignee on the issue. However, 'Admin' users can change the assignee for a coordination issue by editing the Assignee field on the issue. See Edit a Coordination Issue.
6 Users will also need 'Standard' or 'Admin' permissions to the project's Observations tool.
Correspondence
The following table highlights which user permissions are required to perform the described user action.
: Denotes an action that is supported in Procore's iOS and/or Android mobile application.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
1 Users with 'Read Only' level permissions and the necessary granular permissions on a correspondence type can perform this task for correspondence items that they created.
2 Users with 'Standard' level permissions on a correspondence type can perform this task for correspondence items that they created.
3 Users will need additional permissions depending on the new item's tool.
4 Users will need additional permissions on the project's Drawings tool.
Crews
The following table highlights which user permissions are required to perform the described user action.
- Denotes an action supported in Procore's iOS and/or Android mobile application.
Task | None | Read Only | Standard | Admin |
---|---|---|---|---|
Add a Worker 1, 2 ![]() |
![]() |
![]() |
||
Create a Crew ![]() |
![]() |
![]() |
||
Delete a Crew | ![]() |
|||
Edit a Crew 2 ![]() |
![]() |
![]() |
||
Edit a Worker 1 ![]() |
![]() |
|||
Remove a Worker 3 | ![]() |
|||
Search Crews | ![]() |
![]() |
![]() |
|
Search for a Worker | ![]() |
![]() |
![]() |
|
View a Crew ![]() |
![]() |
![]() |
![]() |
|
View a Worker ![]() |
![]() |
![]() |
![]() |
1 Users must also be granted 'Read Only' or 'Standard' level permissions on the Project level Directory tool with the 'Create Contacts' granular permission enabled on their permission template OR must be granted 'Admin' level permissions on the Project level Directory tool to perform this task.
2 Users with 'Standard' permission can only edit a crew when designated as the 'Crew Lead'. See Create a Crew.
3 'Admin' users must also be granted 'Admin' permission on the project's Directory tool to perform this task.
Daily Log
The following table highlights which user permissions are required to perform the described user action.
: Indicates an action supported in Procore's iOS and/or Android mobile application.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
2 Users with 'Standard' permissions who are granted the ‘Standard Users Can Edit and Delete Own Entries’ granular permission can edit or delete their own entries for days that have not been marked as complete.
3 Users with 'Read Only' or 'Standard' permissions who are granted the 'Collaborator Entry Only' granular permission can edit their own entries until they are approved.
4 By default, users with 'Read Only' or 'Standard' permissions who are granted the ‘Collaborator Entry Only’ granular permission can only view logs that they created. If these users also have 'View entries associated to users within the same company' granular permission, they can additionally see entries from other users at their same company.
5 The Calendar View is not visible to users with the ‘Collaborator Entry Only’ granular permission enabled on their permission template.
6 The granular permission for 'Collaborator Entry Only' has to be on a global template before the option is available in the Daily Log configuration settings.
Direct Costs
The following table highlights which user permissions are required to perform the described user action.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.
Directory (Project Level)
Learn which user permissions are required to take the described actions in this tool.
Important
Some actions that impact this tool are done in other Procore tools. See the User Permissions Matrix for the full list of actions taken in all other tools.
Permissions
| | The action is available on Procore's Web, iOS, and/or Android application. Click to view the article.
Users can take the action with this permission level.
Users can take the action with this permission level AND one or more granular permissions.
What granular permissions are available for the Project level Directory tool?
Important
A user who is granted 'Admin' level permissions to the Project level Directory tool is also automatically granted 'Admin' permissions to all of the project's tools.Action | None | Read Only | Standard | Admin | Notes |
---|---|---|---|---|---|
Add a Company to the Project Directory |
|
|
![]() |
On a mobile device, this action can be performed offline. Tasks performed offline are be synced with Procore when a network connection is reestablished. | |
Add a Distribution Group to the Project Directory |
|
|
![]() |
||
Add a Contact to your Device |
![]() |
![]() |
![]() |
On a mobile device, this action can be performed offline. | |
Add a Phone Calls Entry from the Directory |
![]() |
![]() |
|||
Add a User Account to the Project Directory |
|
|
![]() |
On a mobile device, this action can be performed offline. Tasks performed offline are be synced with Procore when a network connection is reestablished. | |
Add Project Insurance to a Company Record in the Project Directory |
![]() |
||||
Assign a Project Permissions Template to a User in the Project Directory |
|
|
![]() |
Users with granular permissions have the following limitations:
|
|
Bulk Add Users and Companies to a Project Directory |
|
|
![]() |
Users with the granular permission can only assign 'Assignable Permission Templates' to others based on their own permissions template settings. | |
Change a User's Permissions in the Project Directory |
|
|
![]() |
Users with the granular permission can only assign 'Assignable Permission Templates' to others based on their own permissions template settings. | |
Configure the Project Team on the Project Home Page |
|
|
![]() |
||
Configure Advanced Settings for the Project Directory |
![]() |
||||
Create a Project Specific Permissions Template from the Project Directory |
![]() |
||||
Customize the Column Display in the Directory Tool |
![]() |
![]() |
![]() |
||
Delete a Distribution Group from the Project Directory |
![]() |
||||
Download vCard for a User Account in the Project Directory |
![]() |
![]() |
![]() |
||
Edit a Company in the Project Directory |
|
|
![]() |
||
Edit a Distribution Group |
|
|
![]() |
||
Edit an Account in the Project Directory |
|
|
![]() |
Only users with 'Admin' level permissions can edit inactive user accounts. | |
Email Forward Contact Information |
![]() |
![]() |
![]() |
||
Enable Schedule Notifications for a User on a Project |
![]() |
||||
Enable Weather Delay Alerts by Phone or Email |
![]() |
||||
Export the Project Directory to CSV or PDF |
![]() |
![]() |
![]() |
||
Forward Contact Information by Email |
![]() |
![]() |
![]() |
||
Invite or Reinvite a User to Join a Procore Project |
|
|
![]() |
||
Invite a Batch of Users to Join a Procore Project |
|
|
![]() |
||
Reactivate a Company in the Project Directory |
![]() |
||||
Reactivate a User in the Project Directory |
![]() |
||||
Remove a Company from the Project Directory |
|
|
![]() |
||
Remove a User from a Project |
|
|
![]() |
||
Remove Project Insurance from a Company Record |
![]() |
||||
Remove a Batch of User Accounts from a Project Directory |
|
|
![]() |
||
Remove a Batch of Companies from a Project Directory |
|
|
![]() |
||
Request Company and People Imports |
|
![]() |
|||
Save Contact to Phone on a Mobile Device |
![]() |
![]() |
![]() |
||
Search and Filter the Project Directory |
![]() |
![]() |
![]() |
||
Send a Message or WhatsApp to a Contact |
![]() |
||||
Set Tenderer Information at the Project Level |
![]() |
||||
Switch Between Views in the Project Directory |
![]() |
![]() |
![]() |
||
View the Project Directory |
![]() |
![]() |
![]() |
On a mobile device, this action can be performed offline if the item was previously viewed and cached on your mobile device. |
Documents (Project Level)
The following table highlights which user permissions are required to perform the described user action.
: Indicates an action supported in Procore's iOS and/or Android mobile application.
+ : Indicates that one or more granular permissions are available for the task. See the relevant tutorial or Grant Granular Permissions in a Project Permissions Template for more information.