4 Where to go next

4.1 User Manual chapters by role

The User Manual is the complete reference. Start with the chapters for your role:

RoleChapters
Every userGetting Started; Policy Management (Policy portal and acknowledgements); Security Awareness (Taking a test)
Data LiaisonData Privacy (Data mapping questionnaires)
Risk ownerRisk Management (The risk detail page, Treatments, Reviews, Exceptions)
Control ownerRisk Management (Controls); Internal Audits (Working with findings)
Compliance managerCompliance Management; Projects; Report Center
Policy owner or approverPolicy Management
Vendor or third-party risk managerThird-Party Management; Online Assessments
Security operationsIncident Management
Data Protection OfficerData Privacy; Incident Management (Personal data breaches); Third-Party Management (Data protection)
Internal auditorInternal Audits; Account Reviews; Report Center
CISO or executiveGetting Started (The Dashboard); Report Center

4.2 The Administrator's Guide

Read the Administrator's Guide to install and run TraxrGRC: deployment, the first administrator, sign-in with SAML SSO or LDAP, outgoing email, users, groups and roles, notification rules, branding, backups and the audit log.

Every Settings screen has a card on the Settings page, shown only to people who may open it. The Settings entry in the sidebar appears for anyone with at least one card: administrators see them all, and a GRC Manager, for example, sees Custom Fields, Notifications and Audit Log.

4.3 The REST API

Scripts and other systems can read and maintain records through the REST API at /api/v1. The machine-readable OpenAPI document is served at /api/v1/openapi on your installation and needs no token.

  1. A user with Create on API tokens (an administrator, by default) creates a token at /settings/api-tokens, with a name, an optional expiry date and the module scopes it may use.
  2. The token, starting with aat_, is shown once. Store it safely.
  3. Send it in the Authorization header:
curl -H "Authorization: Bearer aat_your_token_here" \
  https://grc.example.com/api/v1/risks

A token acts as the user who created it, limited to its scopes, and every change it makes is recorded in the audit log.

Full details: User Manual, REST API.

4.4 Getting help