Documentation Index
Fetch the complete documentation index at: https://quintsecurity.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
The Settings page consolidates all configuration: personal preferences, team management, and API token operations.
Theme
Toggle between dark and light mode. Dark mode is the default and recommended for extended use.
The theme preference is stored per-user and persists across sessions and devices. You can also toggle via the command palette (Cmd+K then type “theme”).
Default Views
| Setting | Options | Default |
|---|
| Default time range | 1h, 6h, 24h, 7d, 30d | 24h |
| Landing page | Overview, Sessions, Alerts, Fleet | Overview |
Notifications
Configure which events trigger notifications and how they’re delivered.
Alert Notifications
| Setting | Description | Default |
|---|
| Critical alerts | Notify on critical severity alerts | On |
| High alerts | Notify on high severity alerts | On |
| Medium alerts | Notify on medium severity alerts | Off |
| Low alerts | Notify on low severity alerts | Off |
Delivery Methods
| Method | Description |
|---|
| Browser push | Desktop notifications via the browser. Requires permission grant on first enable. |
| Email digest | Periodic email summary. Options: real-time, hourly, daily, weekly, off. |
For most teams, enabling critical + high alerts with daily email digest strikes the right balance between awareness and noise.
Team Management
Admins and owners see the team management section. From here:
Invite Members
Send an invite by entering an email and selecting a role. The invitee receives no email from Quint — they just need to sign up (or log in if they already have an account), and the membership is auto-claimed.
Member List
View all members and pending invites:
- Name and email
- Role — with edit button for admins+ (respecting role assignment rules)
- Status — active or pending
- Joined date — or invite date for pending members
- Actions — remove member, change role
Role Changes
Click the role badge next to any member to change it. You can only assign roles up to your own level. See RBAC for details.
Removing a member revokes all their personal tokens immediately. Make sure any automations using their personal tokens are migrated to service tokens first.
API Tokens
Create and manage tokens for programmatic API access. This section mirrors the functionality of the Token API.
Create Token
- Click “Create Token”
- Enter a name (e.g., “CI Pipeline - Staging”)
- Select the token type: personal, service, or deploy
- Choose scopes: read, ingest, manage, admin, or all
- Click “Create”
- Copy the token immediately — it won’t be shown again
Token List
All org tokens displayed with:
| Column | Description |
|---|
| Name | Human-readable label |
| Type | Personal, service, or deploy |
| Scopes | Granted permissions |
| Created by | Who created the token |
| Last used | Timestamp of most recent use |
| Created | When the token was created |
| Actions | Revoke button |
Revoke Tokens
Click the revoke button on any token. Revocation is immediate and irreversible. The token stops working on the next API call.
Stale tokens (unused for 90+ days) are highlighted in the list. Regularly audit and revoke tokens you no longer need.
Preferences API
All settings on this page are also available via the API:
GET /v1/preferences — retrieve current preferencesPUT /v1/preferences — update preferences (JSONB merge)
See the Auth API Reference for full details and examples.
