How do 360 Reporting permissions work?
Answer
Procore's 360 Reporting tools require two separate permission layers to access 360 Reports:
-
Permissions to create and manage reports.
-
Permissions to access reporting data.
1. Permissions to Create and Manage Reports
You must have the appropriate access to the Project and Company 360 Reporting tools to create and manage reports.
2. Permissions to View 360 Report Data
For the Project Execution dataset, your data access is determined by your existing tool permissions. You can create and view detailed Project and Company 360 Reports using all the data you already have permission to see—no tool-level admin access is required.
To view data in all other datasets, you generally need 'Admin' permissions on the source tool where that data originates.
The sections below list the permissions needed in each source tool to see the data object in 360 Reports. Note that Company Admins have permissions to view all data.
Action Plans
If you have access to view the action plan in the tool, you can view all associated data from its child objects. See Action Plans Permissions.
Admin
Tendering
Budget
Change Events
If you have access to view the change event in the tool, you can view all associated data from its child objects. See Change Events Permissions.
Commitments
Coordination Issues
If you have access to view the co-ordination issue in the tool, you can view all associated data from its child objects. See Co-ordination Tool Permissions.
Correspondence
If you have access to view the correspondence in the tool, you can view all associated data from its child objects. See Correspondence Permissions.
Note: Super Private correspondences are excluded.
Crews
Site Diary
If you have access to view the site diary in the tool, you can view all associated data from its child objects. See Site Diary Permissions.
Direct Costs
Directory
Documents
Drawings
If you have access to view the drawing in the tool, you can view all associated data from its child objects. See Drawings Permissions.
Estimating
Forms
If you have access to view the form in the tool, you can view all associated data from its child objects. See Forms Permissions.
Incidents
If you have access to view the incident in the tool, you can view all associated data from its child objects. See Incidents Permissions.
Inspections
If you have access to view the inspection in the tool, you can view all associated data from its child objects. See Inspections Permissions.
Instructions
If you have access to view the instructions in the tool, you can view all associated data from its child objects. See Instructions Permissions.
Meetings
If you have access to view the meeting in the tool, you can view all associated data from its child objects. See Meetings Permissions.
Observations
If you have access to view the observation in the tool, you can view all associated data from its child objects. See Observation Permissions.
Payments
Photos
If you have access to view the photo in the tool, you can view all associated data from its child objects. See Photos Permissions.
Main Contracts (Funding/Client Contracts)
Snag List
If you have access to view the snag item in the tool, you can view all associated data from its child objects. See Snag List Permissions.
RFIs
If you have access to view the RFI in the tool, you can view all associated data from its child objects. See RFI Permissions.
Programme
If you have access to view the programme in the tool, you can view all associated data from its child objects. See Programme Permissions.
Specifications
If you have access to view the specification in the tool, you can view all associated data from its child objects. See Specification Permissions.
Submittals
If you have access to view the submittal in the tool, you can view all associated data from its child objects. See Submittals Permissions.
Daywork Sheets
Tasks
If you have access to view the task in the tool, you can view all associated data from its child objects. See Task Permissions.
Timesheets
If you have access to view the timecard in the Timesheets tool, you can view all associated data from its child objects. See Timesheets Permissions.
3. Practical Example: Company 360 Reporting for the RFIs Tool
Here is a practical example of how source tool data permissions work.
Example
The Scenario
-
You are assigned access to nine (9) Procore projects.
-
On five (5) projects, you have 'Admin' permissions on the RFIs tool.
-
On four (4) projects, you have 'Read Only' permissions on the RFIs tool and no granular permissions assigned.
The Action
-
You create a Company 360 Report and add data from the RFIs tool. See Create a Company 360 Report.
The Result
-
The report shows RFIs data for the five (5) projects where you have 'Admin' access.
-
Procore's security rules automatically filter out and exclude data from the four (4) projects where you only have 'Read Only' permissions. This happens because the RFIs tool requires users with 'Read Only' level permissions to have granular permissions. To learn more, see Which Procore tools support granular permissions?

