Plans have standard defaults. Scope can be adjusted when the work is bigger.
Atomation starts from clear one-time and continuous monitoring defaults. If a customer's Okta footprint, retention needs, deployment model, or support requirements are larger, those limits can be adjusted in a written scope of work or order form.
Baseline and continuous monitoring use different retention rules.
| Plan | Scan cadence | Snapshots | Retention | Exports |
|---|---|---|---|---|
| Baseline Health Check | Manual scan only | One active org assessment; reruns allowed during the retention window | 14-day default retention/fix window after the first completed scan | Reports, findings, and raw snapshot export available during the retention window |
| Continuous Monitoring | Manual scans plus one active schedule per org | Rolling 10-snapshot history per org by default | Oldest snapshot is removed when the next snapshot exceeds the included history | Current and retained reports, findings, and snapshot exports available while retained |
Expanded limits are quoted by size, retention, cadence, and support scope.
Some clients need more than the default plan limits. That is handled through a written scope instead of being implied by the base plan.
- Additional Okta orgs
- Longer retention or more snapshot history
- Higher scan frequency or custom notification routing
- Larger user, group, app, token, workflow, or evidence volume
- Custom rule work, customer-control mapping, partner delivery, or self-hosted deployment support
Adjusted limits may add storage, compute, backup, implementation, support, or professional services cost.
Atomation's assessment access remains read-only against the customer's Okta org. The product does not request write scopes, does not store customer secrets in exports, and does not automatically remediate or write changes back to Okta. Follow-up implementation work is a separate, customer-approved services scope.
Need a scope that does not fit the default limits?
Book a free discovery call. We'll map your workflow, find the highest-value automation, and show you the smallest useful first build — no obligation.