Skip to content

Tutorials

The Tutorials section combines concepts and guides into complete scenarios. If a guide answers β€œhow do I do X” and a concept answers β€œwhat is X,” a tutorial answers β€œcomplete the X scenario from start to finish.”

These pages take longer to write than guides (each is ~30-60 minutes of reader time) but pay off at the highest conversion rate for evaluators trying to understand if AtmanID solves their actual problem.

Available tutorials

Developer onboarding

  1. First API call β€” make your first authenticated AtmanID API call in under 10 minutes using curl. Get a key, list your users, parse the response, verify the audit log.
  2. First SDK script β€” same scenario via the TypeScript SDK. Typed responses, retry logic, structured errors.
  3. Common patterns β€” pagination, error handling, retries, rate limit handling, webhook signature verification, idempotency.

Operator onboarding

  1. Onboard your first app and run a certification campaign β€” the canonical end-to-end scenario for a new identity admin. Add Salesforce to AtmanID, define entitlements, identify reviewers, launch a quarterly campaign, review responses, export the decisions for the auditor. ~30 minutes for the first app, ~5 min/quarter to launch each campaign.
  2. Set up an external auditor for SOC 2 evidence collection β€” Sarah onboards Marcus from a Big Four firm with read-only access scoped to a SOC 2 engagement. NDA flow, evidence pack generation, audit chain integrity verification, engagement closeout. Both perspectives β€” Sarah’s setup work AND Marcus’s auditor experience. ~25 minutes.

Operator onboarding (more scenarios)

  1. Build a custom approval workflow with the Workflow Designer β€” Sarah builds a multi-stage approval workflow for high-risk Salesforce admin entitlements. Serial stages, approver quorums, conditional routing, SLA-breach policy, approver delegation. ~25 minutes.
  2. Integrate AtmanID into a CI/CD pipeline via the SDK β€” Dev integrates AtmanID into the deploy pipeline. Each deploy registers its agent identity, scopes capabilities to least-privilege, requests JIT access elevation when production push needs it, deactivates on rollback. ~30 minutes.
  3. Onboard a Joiner / Mover / Leaver lifecycle β€” Sarah handles a full HR-driven JML cycle. New hire joins (birthright access), changes department (mover; stranded access revoked or ticketed), then leaves (full deprovision, owned agents swept, mailbox clean-up). ~30 minutes.
  4. Investigate and remediate a privileged access incident β€” Priya gets a SIEM alert at 2am. Walk the security-shaped scenario from detection β†’ investigation β†’ containment β†’ post-incident review. ~30 minutes during the incident + ~2 hours post-incident write-up.

GitOps + automation

  1. GitOps NHI lifecycle with the jml-sync GitHub Action β€” Dev manages a fleet of NHIs via a YAML manifest in his repo. The atmanid/jml-sync GitHub Action runs on every push, diffs the manifest against tenant state, and applies CREATE/UPDATE/DEACTIVATE changes (unchanged rows report SKIPPED_NOOP) with audit-chain attribution. The managed_by ownership boundary as the architectural safety primitive. ~30 minutes for first manifest + perpetual zero-touch on every commit.

Adjacent sections

  • Concepts β€” read first if you encounter unfamiliar terminology in a tutorial
  • Guides β€” for the individual recipes that tutorials chain together
  • Reference β€” for the API/SDK calls that appear in code-shaped tutorials

Β© AtmanID Β· Privacy