Set up · How-to
Administrators: first steps
Sign-in and SSO, users and roles, domain profiles, review flows, validation and the duties to repeat.
Updated 11 Nov 20262 min read
All Tracewright pages
- What Tracewright does
- Quick start: your first project
- Roles and who can do what
- How AI drafting works
- Review flows and electronic signatures
- Traceability and release readiness
- Add meetings, documents and emails
- Record meetings
- Review and approve records, day to day
- Checklists and review meetings
- Baselines and publishing
- Risk management
- Project memory, search and the assistant
- Administrators: first steps
- AI models and governance
- Jira and Polarion
- Microsoft 365, Teams and Outlook
- Alerts to Teams channels and webhooks
- Desktop app and browser extension
- Import from DOORS, Polarion, Jama and other tools
- Troubleshooting
- Frequently asked questions
- Modules
Your Tracewright installation (our managed service or your own deployment) starts with one administrator account. From there:
- 1Sign in and secure your accountown password, MFA or passkey
- 2Sign-in for everyoneSSO with your identity provider
- 3Users and rolesinvite people, set app roles
- 4Domain profiles and review flowsmatch your procedures
- 5Integrations and AIconnect tools, choose models
- 6Run qualificationfile the evidence
1. Secure your account
Sign in with the first-administrator details we give you, set your own password and turn on multi-factor sign-in or a passkey.
2. Sign-in for everyone
Under Settings → Sign-in, connect your identity provider (single sign-on) so people use their work accounts. Settings apply within seconds, without a redeploy, and every change is in the history.
3. Users and roles
Users lists people, their app role, sub-roles (such as IT Admin), sign-in method and status. Roles shows what each role may do, capability by capability; create custom roles where your procedures need them. Project duties are set per project on its Team tab.
4. Domain profiles and review flows
- Domain profiles hold an industry's vocabulary: standards, classifications, life-cycle phases, record kinds and intake fields. Use a built-in profile or copy one for your organisation.
- Review flows set the steps a record goes through. Copy a built-in flow to make your own. Every change is a new version.
5. Validation
Administration → Validation → Run qualification runs the automated checks and produces the validation evidence (IQ/OQ/PQ) for Tracewright itself. Expect no failures; file the run with your deployment record. Run it after every update and monthly.
Duties to repeat
| Duty | Where | How often |
|---|---|---|
| Qualification run | Administration → Validation | After every update, and monthly |
| Access reviews | Project → Team → Access review | Per project (default every 90 days) |
| Model, connector and integration review | AI Control Centre, Integrations | Quarterly; suspend what is unused |
| AI-use register | Administration → AI governance | By each entry's review date |
| Profiles, flows and checklists | Administration | When a standard or procedure changes |
| Leavers | Users | Deactivating a user stops their tokens and connections |
| AI budget and cost | AI Control Centre → Overview | Monthly |
Was this page helpful?
Can't find what you need? Contact support or read about Tracewright.