AtomationDocsPartner delivery guide

Atomation Partner Delivery Guide

A reusable shell for IAM, security, compliance, and implementation partners who help deliver Okta assessments with customer-approved evidence routing.

Customer handoffOkta assessmentEvidence ready

Partner Delivery Model

Atomation supports partner-led and co-delivered Okta assessment work when the customer approves the partner role, evidence routing, and report recipients.

This guide is a shell. It does not imply official Okta partner status, marketplace status, or customer endorsement. Keep partner claims conservative until verified.

Customer approvalRequired before access

Partner access to findings, evidence, reports, or remediation notes requires customer approval.

Evidence routingCustomer-owned

Partners should not receive raw identity evidence unless the customer explicitly approves the route.

Delivery roleCoordination and remediation

Partners can coordinate setup and remediation, while Atomation keeps product verification and report QC.

DocumentationSame setup guides

Partners use the same customer onboarding, API access, and SSO/SCIM guides.

Delivery Roles

RoleOwnerResponsibility
AtomationAtomation operatorProduct setup, scan operation, finding review, report packaging, and quality control.
PartnerApproved partner leadCustomer coordination, implementation context, remediation planning, and stakeholder brief.
CustomerCustomer sponsor and Okta adminApprove Okta access, confirm scope, review reports, and own remediation decisions.

Customer Approval Points

  • Customer approves Atomation tenant creation.
  • Customer approves read-only Okta API service app setup.
  • Customer approves optional SCIM provisioning for workspace users.
  • Customer approves first scan authorization.
  • Customer approves evidence routing and report recipients.
  • Customer approves partner access to any report or finding output.

Partner-Led Workflow

  1. Partner identifies the customer need and confirms the Okta assessment scope.
  2. Atomation creates or prepares the customer workspace.
  3. Customer Okta administrator completes read-only API setup.
  4. Atomation verifies access and runs the first scan.
  5. Atomation operator reviews findings before publication.
  6. Partner joins findings readout only after customer approval.
  7. Partner supports remediation planning and customer handoff.
Customer onboarding

Use the customer getting-started guide.

Okta API access

Use the read-only service app guide.

Okta SSO and SCIM

Use the workspace access and provisioning guide.

Roles and permissions

Review least-privilege workspace roles.

Screenshot Placeholders

Screenshot placeholderPartner delivery overview

High-level engagement model and customer approval path.

Screenshot placeholderCustomer approval checklist

Evidence routing, report recipients, and partner access controls.

Screenshot placeholderFindings summary

Sanitized findings package for an approved partner readout.

Screenshot placeholderReport export package

Approved report and remediation handoff artifacts.

Guardrails

  • Do not name customers publicly without written approval.
  • Do not imply Okta endorsement or OIN catalog availability unless verified.
  • Do not route customer identity data to third-party AI tools.
  • Do not request write scopes for the assessment connection.
  • Do not give partners access to raw evidence without customer approval.

Internal template path: internal/atomation-app/docs/templates/partner-delivery.md