These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- GRC Audit Compliance
- Integrations
Integrations
Trace users and source evidence through the assessment records.
- GRC Audit Compliance
- Signed-in users
- Assessment files
- Evidence references
- Saved reports
Systems to connect
- Signed-in users. Link each named staff record to the correct user before assigning assessment, control or review work.
- Assessment files. Put a supporting file on the right assessment through an assessment attachment, with its title, uploader, evidence type and visibility.
- Evidence references. Record the source identifier on the control test line so the Control Tester and Independent Reviewer can find the material examined.
- Saved reports. Read assessment, finding and decision results from their source records and keep each report within the reader’s organization scope.
How connections are governed
Start with one named staff member and one assessment. Confirm that the staff record refers to the intended user and organization. Attach a sample file to the corresponding assessment family and check whether its visibility is Internal or Shared. Have the Independent Reviewer follow the test line’s evidence reference to the source material before deciding on a submitted revision. The Admin checks the operation key, result state and persisted effects if an update has an uncertain outcome. Keep each decision tied to the assessment and revision that produced it.
Set up GRC Audit Compliance your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.