Grant Granular Permissions in a Project Permissions Template

Action Plans 

• Add Records. Grants users the privilege to add records to an Action Plan. On by default for users with 'Standard' permissions.
  Note: Must be turned on for users with 'Read-only' Permissions.
• Add Record Request to Published Plans as Assignee. Grants users the privilege to add a record request if they are an assignee.
• Create and Edit Action Plan. Grants users the privilege to create and edit an Action Plan. See Create an Action Plan and Edit an Action Plan.
• Create and Edit Project Templates. Grants users the privilege to create and edit project level Action Plans templates. 
• Edit Due Date in Published Plans. Grants users the privilege to edit the due date in any published Action Plans.
• Edit Notifications. Grants users the privilege to edit project settings for Action Plans.
• Edit Item Notes as Action Plans Assignee. Grants users the privilege to edit item notes on action plans they are assigned to.
• Edit Item Status as Action Plans Assignee. Grants users the privilege to edit the status of an action plan item they are assigned to.
• Delete Action Plan. Grants users the privilege to delete an Action Plan. See Delete an Action Plan.
• Sign as Action Plan Approver. On by default for users with 'Standard' permissions and cannot be modified. See Approve an Action Plan to be Performed.
  Note: Must be turned on for users with 'Read-only' Permissions.
• Sign as Action Plan Approver for Users with the Same Company. Grants users the privilege to sign as an Action Plan Approver for anyone in a specified company. See Approve an Action Plan to be Performed.
  Note: You can only sign as an approver for users your share a company with. Action Plans does not allow you to sign as an approver for users in another company. 
• Sign as Completed Action Plan Receiver. On by default for users with 'Standard' permissions and cannot be modified. See Sign a Completed Action Plan.
  Note: Must be turned on for users with 'Read-only' Permissions.
• Sign as Completed Action Plan Receiver for Users with the Same Company. Grants users the privilege to sign as an Action Plan Receiver for anyone is a specified company. See Sign a Completed Action Plan.
  Note: You can only sign as receiver for users your share a company with. Action Plans does not allow you to sign as an receiver for users in another company. 
• Sign as Action Plan Assignee for any User. Grants users the privilege to sign an Action Plan as an assignee from the project. 
• Sign as Action Plan Assignee for Users within the Same Company. Grants users the the privilege to sign an Action Plan as an assignee from a specified company.
• Sign as Action Plan Assignee. On by default for users with 'Standard' permissions.
  Note: Must be turned on for users with 'Read-only' Permissions.
• Remove Record. Grants users the privilege to remove records from an Action Plan. On by default for users with 'Standard' permissions.
  Note: Must be turned on for users with 'Read-only' Permissions.
• See the Permissions Matrix for the Project level Action Plans tool for more information about the different actions that can be performed by users with the permission level you select.

Admin

• Update General Settings. Grants users the privilege to add, edit and remove project details in the general settings for the Project level Admin tool. See Add or Edit General Project Information.
• Update Active Tabs. Grants users the privilege to add, edit and remove the Procore tools that are active on a project. See Add and Remove Project Tools and Rearrange the Project Tools Menu.
• Manage Segment Items. Grants users the privilege to add, edit, export and delete segment items on these segments in the project's Work Breakdown Structure: 'Cost Code', 'Sub Job' (optional) and any custom segments.  

   Notes

  For the 'Manage Segment Items' granular permission, be aware of the following:

  • To edit or delete a company level custom segment item that was copied to your project, the Add/Edit/Delete Project Level Segment Items and Delete Segment Items Inherited from a Company settings must be turned ON by your company's Procore Administrator when adding the segment. To learn more, see Add Custom Segments, Edit Segment Items on a Project, and Delete Unused Segment Items from a Project.
  • When editing a company level segment item that was copied to your project, you can only change the 'Description' field of the segment item. See Edit Segment Items on a Project. 
  • When editing a project level segment item that was specifically created on a project, you can change both the 'Code' and 'Description' of the segment item. See Edit Segment Items on a Project. 
  • Procore's default 'Cost Type' segment can only be managed by a Procore Administrator in the Company level Admin tool. See Add Company Cost Types. 
• Manage WBS Codes.  Grants users the privilege to manage the WBS budget code structure in a project's Work Breakdown Structure. See Arrange the Project Budget Code Structure.

   In Beta

  For users participating in the Beta Program for the Work Breakdown Structure: Activate & Deactivate Project Level Budget Codes feature, the 'Manage WBS Codes' granular permission also grants users the privilege to Activate Budget Codes on a Project and Deactivate Budget Codes on a Project. 
• Manage Locations. Grants users the privilege to add, edit and remove multi-tiered locations from a project. See Add Tiered Locations to a Project, Edit Tiered Locations and Delete Tiered Locations from a Project. See What are multi-tiered locations? 

See the Permissions Matrix for the Project level Admin tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Tendering

• Create Tender Notes. Grants users the privilege to create tender notes.  See Add Notes to the Tender List.
• Edit Tender Notes. Grants users the privilege to edit tender notes. 
• Delete Tender Notes. Grants users the privilege to delete tender notes.
  Note: Users with 'Standard' or 'Read-Only' level permissions to the Tendering tool will also need to be added to the Tender Package's distribution list to see the tender package and perform the actions above.

See the Permissions Matrix for the Project level Tendering tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Budget

• Import Budget From File. Along with the 'Create and Edit Original Budget Amount' granular permission, this granular permission grants users the privilege to import a budget from a file. See Import a Budget.
• Create and Edit Original Budget Amount. Grants users the privilege to create and edit the original budget amount. See Add a Budget Line Item and Edit a Budget.
• View Direct Cost Details. Grants users the privilege to view transaction-level details being populated from the Direct Cost tool via a popup window that appears in the Budget tool. The Direct Costs columns is visible when creating, editing and viewing line items. See Read a Budget. 
  Notes: 
  • This granular permission provides users with the ability to click a value in the 'Direct Costs' column of a budget view to open a popup window that shows direct cost transaction detail.
  • If your company is using either the Procore +  Sage 300 CRE® integration or the Viewpoint® Vista™ Integration by Ryvit, this setting must be enabled in the permissions template that is assigned to Procore end users performing budget exports.
• Delete Budget Line Items. Grants users the privilege to delete budget line items. See Delete a Budget Line Item.
• Lock Budget. Grants users the privilege to lock the Budget tool. See Lock a Budget.
• Send and Retrieve Budgets from ERP. Grants users the privilege to send data from the Budget tool to the ERP Integrations tool and also to retrieve information from the ERP Integrations tool before it is accepted for export to an integrated ERP system by an accounting approver. For more information, see the links for your ERP Integration:
  • Send a Budget to ERP Integrations for Accounting Acceptance
  • Retrieve a Budget from ERP Integrations Before Acceptance

See the Permissions Matrix for the Project level Budget tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Commitments

• View Private Purchase Order Contract. Grants users the privilege to see purchase orders marked as private, without having to add them to the 'Private' drop-down. Users can also view information in the Variations tab on private purchase orders. See View a Purchase Order.
• View Private Work Order Contract. Grants users the privilege to see subcontracts marked as private, without having to add them to the 'Private' drop-down. Users can also view information in the Variations tab on private subcontracts. See View a Subcontract.
• Create Purchase Order Contract. Grants users the privilege to create purchase orders. See Create a Purchase Order. 
• Create Work Order Contract. Grants users the privilege to create subcontracts. See Create a Subcontract. 
• Update Purchase Order Contract. Grants users the privilege to edit purchase orders. See Edit a Purchase Order.
• Update Work Order Contract. Grants users the privilege to edit subcontracts. See Edit a Subcontract.

See the Permissions Matrix for the Project level Commitments tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Correspondence

• Create Item. Grants users the privilege to create a correspondence item.
  Note: Since users with 'Standard' level permissions on a correspondence type can create correspondence items, the 'Create Item' granular permission cannot be unchecked while 'Standard' is selected for the correspondence type on the permissions template.
• Respond to Items They Are On. Grants users the privilege to respond to correspondence items that they are added to the item's 'Assignee' field, 'Received From' field or 'Distribution' list.
  Note: Since users with 'Standard' level permissions on a correspondence type can respond to correspondence items they are on, the 'Respond to Items They Are On' granular permission cannot be unchecked while 'Standard' is selected for the correspondence type on the permissions template.
• Edit Open Items They Created. Grants users the privilege to edit 'Open' correspondence items that they created.
  Note: Since users with 'Standard' level permissions on a correspondence type can edit 'Open' correspondence items they created, the 'Edit Open Items They Created' granular permission cannot be unchecked while 'Standard' is selected for the correspondence type on the permissions template.
• Respond to Items Accessible to Users within Same Company. Grants users the privilege to respond to correspondence items that are accessible to another user within their same company. Users with this granular permission cannot view 'Private' correspondence items unless they have also been granted the 'View Private Items Accessible to Users within Same Company' granular permission.
• View Private Items Accessible to Users within Same Company. Grants users the privilege to view 'Private' correspondence items that are accessible to another user within their same company.

See the Permissions Matrix for the Project level Correspondence tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Site Diary

• Collaborator Entry Only. Grants 'Read Only' or 'Standard' users the privilege to create entries in the Working hours, Notes, Deliveries and Daily Construction Report sections of the Site Diary. See Create Site Diary Entries as a Collaborator and Approve Collaborator-submitted Site Diary Entries.
  • Notes: 
    • By default, the Daily Construction Report Register is not enabled on projects. Users with 'Admin' permissions on the Site Diary can turn logs on or off for a project in the Site Diary's configure settings. 
    • 'Standard' users without granular permissions can create entries for any register that is enabled on the project. If 'Standard' users are granted the 'Collaborator Entry Only' privilege, they will only be able to view and add entries to the four registers mentioned above, however, they will be able to edit their entries until they are approved.
    • The granular permission for 'collaborator entry' has to be on a global permission template OR a project permission template before the option is available in the Site Diary configuration settings.
• Standard Users Can Edit and Delete Own Entries. Grants 'Standard' users the privilege to add, edit and delete their own entries in any section of the Site Diary, as long as the day has not been marked as complete. See Mark a Site Diary as Complete.
  Important! To grant this privilege:
  • The permissions must be set to 'Standard.'
  • The 'Standard Users Can Edit and Delete Own Entries' checkbox must be marked.
  • The 'Collaborator Entry Only' checkbox must be cleared.

See the Permissions Matrix for the Project level Site Diary tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Direct Costs

• Create Direct Cost. Grants users the privilege to add and/or import a direct cost to the project's Direct Costs tool. See Create a Direct Cost and Import Direct Costs.
• Update Direct Cost. Grants users the privilege to edit a direct cost in the project's Direct Costs tool. 
• Delete Direct Cost. Grants users the privilege to delete a direct cost in the project's Direct Costs tool. 

See the Permissions Matrix for the Project level Direct Costs tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Directory

• Add from Company Directory (Assignable Permission Templates Only). Grants users the privilege to bulk add any users with profiles in the Company Directory to the Project Directory. Users with this granular permission can only assign 'Assignable Permission Templates' to other users based on their own permissions template settings. See Bulk Add Users and Companies to a Project Directory and What is an assignable permissions template?
  Note:  This granular permission does NOT grant users the permissions to change another user's project permissions template or to edit the user's information after they initially add the user to the Project level Directory.
• Assign Project Roles. Grants users the privilege to assign project roles and edit project role assignments to users for the project's Home page. See Configure the Project Team in the Project Directory.
• Create and Edit Users. Grants users the privilege to create and edit any users in the Users tab in the Project Directory. Users with this granular permission can only assign 'Assignable Permission Templates' to other users based on their own permissions template settings. See Add a User Account to the Project Directory and What is an assignable permissions template?
• Create Contacts (Only Applicable if Timesheets or Incidents is Enabled). Grants the user the privilege to create 'contacts' (formerly known as 'reference users') in the 'Workers' field in the project's Site teams tool (see Add a Worker) or in the 'Person Affected' or 'Witness Name' fields in the project's Incidents tool (see Add an Injury/Illness Record to an Incident, Add a Near Miss Record to an Incident, and Add a Witness Statement to an Incident). To learn more about contacts, see  What is a 'contact' in Procore and which project tools support the concept?
• Create and Edit Companies. Grants users the privilege to create, edit and deactivate company profiles in the Project Directory. See Add a Company to the Project Directory. 
• Create and Edit Distribution Groups. Grants users the privilege to create and edit distribution groups in the Project Directory. See Add a Distribution Group in the Project Directory.
• Manage Permission Templates (Assignable Only). Grants users the privilege to manage permission templates in the Project Directory. Users with this granular permission can only assign 'Assignable Permission Templates' to others based on their own permissions template settings. See Assign a Project Permissions Template to a User in the Project Directory and What is an assignable permissions template?
• Remove User from a Project. Grants users the privilege to remove users from projects. See Remove a Single User from a Project and Remove a Batch of User Accounts from a Project Directory.
• Remove Company from a Project. Grants users the privilege to remove companies from projects. See Use Bulk Actions > Remove from Project on Companies in the Project Directory.
• Request Company and People Imports. Grants a user with 'Standard' permission the privilege to submit a request to import users or vendors to the Project Directory. See Request Company and People Imports.
• View Company Insurance Information. Grants users the privilege to view a company's insurance information added to the Insurance tab. Important! Only users with 'Admin' level permissions can add or edit insurance information on a company record. See Add Insurance to a Company Record in the Company Directory.
• Update Contacts (Only Applicable if Timesheets or Incidents is Enabled). Grants users the privilege to update 'contacts' (formerly known as 'reference users') in the Project level Directory tool and in the project's Site teams tool. See Edit a Contact in the Project Directory and Edit a Worker. To learn more about contacts, see What is a 'contact' in Procore and which project tools support the concept?

See the Permissions Matrix for the Project level Directory tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Documents

• Access Private Folders and Files. Grants users the privilege to access folders and files marked private. To learn more about file and folder privacy in the Documents tool, see Manage Permissions for Files and Folders and Can I make files and folders in the Documents tool private by default?.
• Rename Folders and Files. Grants users the privilege to rename both files and folders in the Documents tool. See Rename a File and Rename a Folder. 
• Move and Copy Files and Folders. Grants users the privilege to move and copy both files and folders stored in the Documents tool. See Move Files and Folders.
• Set Permissions. Grants users the privilege to use the Manage Permissions button in the Documents tool. See Manage Permissions for Files and Folders. 
• Delete Folders and Files. Grants users the privilege to delete files and folders in the Documents tool. See Delete Files and Folders. 
• See Recycle Bin. Grants users the privilege to view the Documents tool's Recycle Bin in order to view its contents. To learn how to retrieve an item from the Recycle Bin, see Retrieve a File or Folder from the Recycle Bin. 

See the Permissions Matrix for the Project level Documents tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Drawings

• Upload Drawings. Grants users the privilege to upload drawings to the drawings tool. All drawings uploaded to the Drawings tool by a 'Standard' or 'Read only' user will need to be reviewed for OCR accuracy and will be unpublished until an 'Admin' user reviews and publishes the drawings to the team. See What is the unpublished status on drawings?
• Upload and Review Drawings. Grants users the privilege to upload drawings and review them to confirm accuracy. A user can only review drawings that they uploaded and an 'Admin' user will need to publish the drawings.

See the Permissions Matrix for the Project level Drawings tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Meetings

• Add Comment to Meeting. Grants users the ability to add comments to meetings. 
• Delete own Comment on a Meeting. Grants users the ability to delete comments they have made on a meeting.
• Create Meeting¹. Grants users the ability to Create Meetings, filling out the relevant details of the meeting, set up video conference links, location, start/finish times and add attendees. See Create a Meeting.
• Distribute Meetings. Grants users the ability to Distribute the Agenda and the meeting minutes. Distribute a Meeting Agenda and Distribute and Redistribute Meeting Minutes.
• Update Meeting¹. Grant users the privilege to update all meetings that they have access to view (either that the user created, private meetings the user is an attendee for or public meetings that the user has access to). This also allows the user to transition the meeting from Agenda to Minutes and vice versa.
  Note: if a user has Create permissions but does not have Update permissions, the user will be able to create a meeting but as soon as that item is created they won’t be able to make changes to the meeting details. See Edit a Meeting
• Manage Meeting Items¹. Grants users the privilege to Create, Update and Delete Meeting Items within the Meeting Categories. See Edit a Meeting Item.
• Manage Meeting Categories. Grants users the privilege to Create and Delete Meeting Categories for the Meeting. The exception is that the ‘Uncategorized Items’ Category cannot be deleted. See Add a Meeting Category and Delete a Meeting Category.
• Manage Related Items for Meetings. Grants users the privilege to add or delete related items for meetings when granular permission is turned ON. Add a Related Item to a Meeting.
• Email Meeting. Grants users the privilege to email meetings. 
  
  ¹ Permission available on the mobile application. All other Meetings granular permissions only take effect on the web application.

See the Permissions Matrix for the Project level Admin tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps 

Observations

• View Private Observations Assigned to Users within Same Company. Grants a user the privilege to view all Observation items assigned to colleagues within their same company, including observations marked as 'Private'.
• Update Status and Comment on Observations Assigned to Users within Same Company. Grants a user the privilege to respond to updated and add comments to observations assigned to other users within the same Procore company account. This includes observations marked as 'Private.' 
• Can Assign Standard Users to Observations. Grants a user the privilege to assign 'Standard' level users to observations.

See the Permissions Matrix for the Project level Observations tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Photos

• Create Photo Album: Grants users the privilege to create a new photo album in the project's Photos tool. See Create a Photo Album.
  Note: Since 'Standard' level users can create a photo album, the 'Create Photo Album' granular permission cannot be disabled while 'Standard' permission is selected for the Photos tool on the permissions template.
• Delete Photo Album: Grants users the privilege to delete any photo album in the project's Photos tool. See Delete a Photo Album. 
• Reorder Photo Albums: Grants users the privilege to reorder photo albums in the project's Photos tool. See Reorder Photo Albums.
• View Private Photos: Grants users the privilege to view photos that are marked as Private. See Mark a Photo as Private.

See the Permissions Matrix for the Project level Photos tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Head Contracts

• Create Head Contract. Grants users the privilege to create head contracts in the project's Head Contracts tool. See Create Head Contracts.
• Update Head Contract. Grants users the privilege to edit a head contract in the project's Head Contracts tool. See Edit a Head Contract.
• Delete Head Contract. Grants users the privilege to delete a head contract in the project's Head Contracts tool. See Delete a Head Contract.
• View Owner Progress Claim Detail. Grants users the privilege to view the Details tab of the progress claim and the tab's Export button. See Create an Owner Progress Claim.

See the Permissions Matrix for the Project level Head Contracts tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Beta  Head Contracts Workflows

• View Workflow Templates. Grants users the privilege to view the template of a head contract with a custom workflow.
• View Complete Workflow History as Workflow Participant. Grants users the privilege of viewing a custom workflow's entire history when they are a participant in the head contract workflow.
• View Previous Step History Only. Grants users the privilege of viewing a head contract workflow's previous step when they are a participant in the workflow.
• Can Be Workflow Manager. Grants users the privilege of acting as a workflow manager for head contracts on the project.
• Can Start Workflows. Grants users the privilege of starting custom workflows for head contracts on the project. See Start a Custom Workflow.
• Configure Workflow Templates. Grants users the privilege of configuring custom workflow templates for head contracts on the project. See Configure a Custom Workflow Template for Head Contracts on a Project. 

Back to Steps

Defect List

• View Private Defect Items Assigned to Users Within Same Company. Grants a user the privilege to view a defect list item marked 'Private' if another user in their company is the defect item's Assignee.
• Respond to Defect Items Assigned to Users Within Same Company. Grants a user the privilege to respond to a defect list item assigned to another user in their company, including defect items marked as 'Private'.

See the Permissions Matrix for the Project level Defect List tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

RFIs

• Act as RFI Manager. Grants a user the privilege to be selected as the RFI Manager for individual RFIs or to be selected as a project's default RFI Manager. For more information about what tasks users with this granular permission enabled on their permissions template can perform, see What tasks does the 'Act as RFI Manager' granular permission allow users to perform?
• Mark Official Responses. Grants a user the privilege to mark (or unmark) official responses on an RFI if they are the RFI's creator or if they are an Assignee or a Distribution List member on the RFI.
  Note: The 'Only Show Official Responses to Standard and Read-Only Users' configuration setting must be turned OFF in order for a user with 'Standard' level permissions on the project's RFIs tool to view all responses to an RFI that they created. See Configure Advanced Settings: RFIs. Users with the 'Act as RFI Manager' granular permission enabled on their permissions templates can view all responses to RFIs that they create ('Standard' only) or that they are designated as RFI Manager for even if this setting is turned ON.
• View Private RFIs Associated to Users within Same Company. Grants a user the privilege to view any RFI marked 'Private' if another user in their company (including them) is the RFI's creator or is designated as the RFI Manager, an Assignee or a Distribution List member.

See the Permissions Matrix for the Project level RFIs tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Program

• Update Task Completion Percentage. Grants a user with 'Standard' and 'Read Only' permissions privilege to update percent complete on mobile.
• Create Lookaheads. Grants a user the privilege to create a Lookahead. See Create a Lookahead Program.
• Delete Lookaheads. Grants a user the privilege to delete a Lookahead. See Delete a Lookahead.
• View Lookaheads. On by default and cannot be modified. See View Lookahead Program.
• Create Lookahead Tasks. Grants a user the privilege to create Lookahead Tasks. See Create a Subtask.
• Delete Lookahead Tasks. Grants a user the privilege to delete a Lookahead Task. See Delete a Task.
• Update Lookahead Tasks. Grants a user the privilege to update and modify Lookahead tasks. See Edit a Task.

See the Permissions Matrix for the Project level Program tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Submittals

• Create Submittal. Grants a user the privilege to create submittal items.
• Create Submittal Package. Grants a user the privilege to create submittal packages.
• View Private Submittals Associated to Users within Same Company. Grants a user the privilege to view a submittal marked 'Private' if another user in their company is the submittal's creator or is designated as the Submittal Manager, a Submitter, an Approver or a Distribution List member.

See the Permissions Matrix for the Project level Submittals tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Timesheets

• Review & Edit Timesheets. Grants users with 'Read Only' or 'Standard' level permissions on the Project level Timesheets tool with the privilege to edit any timecard entry while it's in the 'Pending' status.
  • These users can also change the status of a timecard entry from 'Pending' to 'Reviewed' on any timesheet using both the Company level and Project level Timesheets tools. For the Project level tool, see Edit a Timesheet and Review a Timesheet. For the Company level tool, see Edit a Timecard Entry in the Company Level Timesheets Tool. 
  • These users can perform Bulk Actions on any timecard or timesheet in the 'Pending' status using both the Company level and Project level Timesheets tool. See Perform Bulk Actions in the Company Level Timesheets Tool, Edit Your Company's Timesheets in Bulk, and Duplicate Your Company's Timesheets in Bulk.

     Note

    • After a timecard entry or timesheet is placed into the 'Approved' status, you will not be able to edit or change the status of either item. 
    • Although these users are able to see the 'Approved' menu option, when you hover your mouse cursor over that option you will see a message that you do not have sufficient permissions to change items to the 'Approved' status. 

See the Permissions Matrix for the Project level Timesheets tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps

Transmittals

• View Private Transmittals Associated to Users within Same Company. Grants a user the privilege to view a transmittal marked 'Private' if another user in their company is the transmittal's creator or included in the 'To' or 'CC' fields of the transmittal.

See the Permissions Matrix for the Project level Transmittals tool for more information about the different actions that can be performed by users with the permission level you select.

Back to Steps