Settings, alerts and retention
Understand account, organization and platform configuration boundaries.
Choose the correct settings scope
| Section | Purpose |
|---|---|
| Account | Your profile and account lifecycle. |
| Security | Supported enterprise SSO configuration. |
| Organization | Workspace details, members, invitations and organization selection. |
| Platform | Alert settings, delivery history and trace-retention configuration. |
| Billing | Subscription and payment-provider workflows when configured. |
| Licenses | Deployment licensing and entitlement information. |
Organization writes depend on your current membership role. Review the active organization before saving shared configuration. Account deletion, member removal and resource deletion have different consequences; do not use them as a troubleshooting reset.
Configure alert delivery
Use Settings → Platform to review alert settings and delivery history. Configure only destinations your team controls. Generate a bounded synthetic event and inspect its actual delivery status. Saving a destination is not proof that network delivery succeeded or that a message was read.
Review alert payloads for sensitive fields and confirm what your capture settings permit. Failed delivery and an absent delivery record must not be treated as a successful notification. Self-hosted workers need approved network access to configured destinations.
Set retention deliberately
The Data Retention panel accepts a retention period in days. A saved retention value is configuration; actual cleanup depends on the deployment’s retention worker/scheduler and operator settings. Verify cleanup in the running deployment before promising a deletion schedule.
Changing capture or retention settings does not retroactively prove that older records or external exports were removed. Agree what happens to existing evidence and backups separately. See data handling.
Identity, billing and licensing
SSO requires an actual identity-provider registration, valid issuer/client configuration and a complete redirect/login test. Payment flows require the deployed payment provider, webhook processing and the intended entitlement result. License settings require the operator’s configured licensing service or process.
The local documentation/browser checks do not certify those external integrations. Verify each against the identity, billing and licensing environments you intend to ship. Use deployment guidance for operational prerequisites and API-key rotation for application credentials.