Okta setup overview
Start here to choose API access, SAML SSO, SCIM provisioning, or role-mapping docs.
Okta Assessment / Documentation
Start here: connect your first org.
The setup guides are written for whoever is doing the setup — not just identity specialists. Everything else (product, evidence, reports, security) has its own section below.
01 / Start here
Set up & connect
Written for whoever is doing the setup — no identity background needed. Connect your first org and run the first scan.
Open
Okta API access
The Okta Admin Console steps for the assessment connector — values to paste, scopes to grant, and how to verify.
Okta SSO setup
Set up SAML 2.0 sign-in for the primary workspace identity org.
SCIM provisioning setup
Configure user lifecycle, group provisioning, and group-to-role linking.
Roles and permissions
What each Atomation role can do, and how Okta groups map to them.
Partner program and delivery
Hosted pilot partner portal onboarding, tenant-addressed client workspaces, pricing scope drivers, customer approval boundaries, and the remaining authorization-validation gate.
02 / Docs
Learn the product
Understand the assessment before any Okta connection is made.
Okta Assessment overview
What Atomation assesses, who the reports are for, and how the first baseline becomes a reviewable product output.
Getting started
How the first assessment is scoped, connected, scanned, and turned into reports.
Client onboarding
Customer handoff packet for first login, org profile, framework selection, automated API setup, org SSO metadata when needed, manual evidence, and first-scan readiness.
What we check
Representative Okta coverage areas across access, policy, service credentials, alerts, evidence, and licensing.
FAQ
Common questions on assessment scope, data handling, deterministic findings, retention, and reports.
03 / Docs
Evidence & Reports
See how findings, screenshots, exports, and framework mappings are packaged.
Automated evidence
A buyer-facing view of evidence automation, report artifacts, screenshots, and example findings.
Reading reports
Report structure, export formats, summary versus operator detail, and evidence appendix behavior.
Evidence and finding examples
Representative screenshots and examples for group-rule dependencies, finding cards, control mapping, and licensing signals.
Alert coverage review
Customer-supplied System Log and SIEM evidence, alert routing, owners, and monitoring gaps; no raw System Log collection by the assessment connector.
Licensing review
Observed usage signals, cleanup candidates, customer agreement context, and renewal-planning questions.
Framework lenses
HIPAA, SOX ITGC, SOC 2, GLBA/FFIEC, ISO 27001, PCI DSS, CIS Controls v8, NIST 800-53, and customer-provided control mapping.
Compliance best practices
The 8 standards that ask for Okta evidence and the security best practices auditors actually check.
04 / Docs
Security & Deployment
Choose the right data boundary and understand the security model.
Hosted workspace model
Hosted Atomation workspaces, partner portals, tenant-addressed client workspaces, and bounded Okta assessment-access claims.
Security model
Assessment access limited to evidence collection, deterministic findings, tenant-bound request context, and exact stored-connector-secret encryption wording.
Plans, retention, and scope
Current history and export behavior, contractual retention boundaries, and roadmap-only monitoring features.