Skip to content

Onboard your first app and run a certification campaign

What you’ll do

You’re Sarah Chen, identity_admin at Acme Corp. Your CFO just asked: “Who has access to Salesforce, and have we reviewed it in the last quarter?” Today the answer is “I’d have to ask each manager and aggregate it manually.” After this tutorial, the answer is “here’s the evidence pack from the campaign that closed last week.”

This is the canonical operator scenario — the workflow every identity admin runs first when adopting AtmanID. It exercises three concepts (entitlement, owner, certification campaign) and ties them into a single 30-minute end-to-end loop. Time investment: one-time ~30 min for the first app, ~15 min for each additional app, ~5 min/quarter to launch each campaign cycle.

If you’re new to AtmanID concepts, read How AtmanID thinks about IAM first — this tutorial assumes you understand the entitlement / role / campaign vocabulary.

Prerequisites

  • An AtmanID tenant where you have the identity_admin role (your roles are shown on My Profile)
  • A SaaS app you want to onboard. This tutorial uses Salesforce as the running example, but the flow is identical for Workday, Okta, GitHub, Snowflake, etc. — anything with a CRUD-shaped admin API or a manual user export.
  • For the connected path: admin credentials to the target app (OAuth client + secret, or service account + API key)
  • For the disconnected path: a CSV export of current users + their access from the target app

Step 1 — Add the app to AtmanID

Navigate to Identity & Access → Applications and click Add Application. The wizard has three steps (Choose Type → App Details → Connector). First, choose how the app is connected:

  • Connected — automated sync via a connector; AtmanID discovers and tracks accounts. Connected apps are included in the scheduled connector sync (daily). Requires admin credentials to the target.
  • CSV-Managed — no API connector; accounts are discovered through periodic CSV upload and reconciliation. Use this for systems AtmanID doesn’t yet have a connector for, or when you can’t share admin credentials yet.
  • Manual — no connector; accounts and entitlements are tracked by hand.

Pick Connected if you have the credentials. Otherwise pick CSV-Managed and you’ll re-upload before each campaign (it’s slightly more work but functionally equivalent for certification purposes).

Fill in the basics:

  • Name: Salesforce Production (or your equivalent — this is the human-readable label that shows up everywhere downstream)
  • Description: one line on what the app is used for.
  • Connector (Connected only): pick Salesforce from the gallery. Credentials (instance URL, connected-app client ID and secret, integration user) are entered in the app’s ⚙ Config tab after creation, not in the wizard.

Create the app. AtmanID writes an audit record with action_type = 'APPLICATION_CREATED'. Then open the app and set its App Owner — the person who reviews access in an App Owner campaign and is notified about it.

Step 2 — Define entitlements

An entitlement is a thing inside the app that someone can have access to. For Salesforce, entitlements include things like:

  • Sales Cloud — Standard User (the core seat)
  • Service Cloud — Read Only
  • System Administrator (the dangerous one)
  • Reports — Manage Custom Reports
  • Data Export Tool (regulated — touches customer PII)

For a connected app, open Applications → Salesforce Production → Entitlements and click Discover Entitlements once the credentials are saved; discovered entitlements are listed on that tab.

For a CSV-Managed app, include an entitlement_code column in the CSV, or define entitlements manually.

For each discovered entitlement:

  • Set the risk level (typically: System Administrator → Critical, Data Export → High, everything else Low or Medium)
  • Assign an entitlement owner — the person who knows whether someone should still have this access. Often this is an engineering manager or a department head, not the IAM admin. The certification campaign will route review requests to this person.
  • Add a business description — one sentence answering “what does this access let someone do?” The certification reviewer reads this, not the technical name.

This is the highest-leverage step in the whole tutorial. Bad entitlement metadata = rubber-stamp certifications. A reviewer who sees “Salesforce — sf_admin role X.7” with no description has no way to make a meaningful decision; they approve everything. A reviewer who sees “Salesforce — System Administrator (full database export, can edit billing)” pauses and thinks. Spend 5 extra minutes here for every entitlement; it pays back over years of certifications.

Step 3 — Verify the current access state

Before launching a certification, sanity-check what AtmanID thinks the access state is.

Navigate to Applications → Salesforce Production → Accounts. You’ll see every account the connector has discovered. Spot-check 3 things:

  • Are there orphan accounts? Users in Salesforce who don’t match any AtmanID identity. This usually means a former employee whose Salesforce account didn’t get deactivated when they left. Flag these to the app owner — they should be cleaned up before the campaign, otherwise reviewers waste time on accounts that shouldn’t exist at all.
  • Are there accounts you’d expect that aren’t shown? A user reaching out and saying “I can’t see my access in AtmanID” usually means a connector mapping issue. Fix before campaign.
  • Do the entitlement counts feel right? If you have 50 employees and 200 entitlements assigned, either someone has a lot of access OR you’re seeing duplicate-account artifacts from a connector quirk.

If anything looks off, fix it now — a campaign that runs on bad data is worse than no campaign because it pollutes the audit trail with rubber-stamp reviews on accounts that shouldn’t have existed.

Step 4 — Launch the certification campaign

Navigate to Security & Risk → Access Certifications and click Launch Campaign. The wizard has five steps — Basics → Scope → Reviewers → Schedule → Review & launch. Configure:

  • Campaign Name: Salesforce Quarterly Review — Q2 2026 (use a consistent naming convention; you’ll have many of these over time)
  • Campaign Type: App Owner Certification reviews every active entitlement in one application with the app owner as reviewer. To route each entitlement to its own owner instead, use Entitlement Owner Certification (one entitlement per campaign). Manager Certification routes each user’s access to their manager — the high-volume, rubber-stamp-prone default; avoid it for app reviews.
  • Scope: select Salesforce Production. The population estimate beside the scope shows how many reviews will be queued.
  • Deadline: the campaign closes at 23:59 UTC on the date you pick. 14 days is standard. 7 days = reviewers complain. 30 days = reviewers procrastinate AND complain.
  • Non-Response Policy: what happens to items a reviewer hasn’t decided by the deadline — Escalate, Auto-Revoke or Auto-Certify, with a grace period in days for the two automatic options. Auto-Revoke is the only setting that guarantees a campaign actually finishes at scale.

Click Launch Campaign (or Save as Draft to launch later). AtmanID writes a CERT_CAMPAIGN_CREATED audit row with the campaign id (a draft launched later writes CERT_CAMPAIGN_LAUNCHED) and queues one review per access assignment in scope.

Reviewers find their items under My Workspace → Inbox → Reviews (My Reviews).

Step 5 — Reviewer experience (you can preview as Sarah)

To see what reviewers experience, open the campaign from Access Certifications — its items list shows each review as the reviewer will see it.

For each access assignment under review, the reviewer sees context such as:

  • User name + email + manager (so they know who they’re approving)
  • The entitlement with its description (so they know what access they’re approving)
  • Original business justification — what was claimed when access was granted
  • Last-used date — when did this user last actually use this entitlement? Shown when usage data is available for the app. Stale access (no use in 90+ days) is the strongest signal for revocation.
  • Peer group comparison — how many other people on the same team have this entitlement? If the user is the only one on their team with System Administrator, that’s worth questioning. If 18 of 20 sales engineers have Sales Cloud — Standard User, the rest is the question.
  • Three actions: Certify (access stays as-is), Revoke (access queued for removal), Escalate (sent to another reviewer).

If you’ve designed Step 2 entitlement metadata well, this experience is informative not annoying. If Step 2 was rushed, this is where you find out — reviewers complain that they can’t tell what they’re approving.

Step 6 — Monitor campaign progress

Open the campaign from Access Certifications for its progress view. You’ll see:

  • Progress and a burndown toward the deadline (so you can nudge stragglers)
  • Decisions — filter items by Certified / Revoked / Escalated / still deciding, and by risk
  • Remediation — items where the reviewer chose Revoke, and whether the revocation has been carried out

Reminders can be configured on the campaign or sent on demand to reviewers who haven’t finished. Social reminders still close the loop faster.

Step 7 — Closeout + audit trail

When the campaign closes, its page shows the outcome, for example:

  • Total reviews: 247
  • Decisions: 198 Certified, 31 Revoked, 18 Escalated
  • Revocations: 28 of 31 carried out; the rest are open revocation tickets in the Revocation Queue (Identity & Access → Provisioning Queues → Revocation)
  • Audit trail: every decision, reviewer action and revocation, queryable from the audit API and the dashboard. The compliance evidence is a query, not a separately curated report (per Audit chain integrity).

Use Export Report on the campaign to download every decision as a CSV for the SOC 2 audit firm. Or the auditor can query the audit trail themselves under their external_auditor role (see Set up an external auditor for SOC 2 evidence collection for that workflow).

Verify in the audit trail that the campaign ran (launch, reviews and decisions all appear; this example lists the launch):

Terminal window
curl -s "$ATMANID_BASE_URL/api/v1/audit?action_type=CERT_CAMPAIGN_CREATED&since=2026-10-01T00:00:00Z" \
-H "Authorization: Bearer $ATMANID_API_KEY"

Expected output: the campaign’s CERT_CAMPAIGN_CREATED record (query CERT_CAMPAIGN_LAUNCHED if you launched from a draft). Reviewer decisions are recorded as ACCESS_CERTIFIED, ACCESS_REVOKE_QUEUED and ACCESS_REVIEW_ESCALATED in the same period.

What just happened

You converted a question your CFO asked (“who has access to Salesforce + has it been reviewed?”) from a multi-week manual aggregation effort into a recurring, audit-ready 14-day cycle that runs every quarter automatically. The first run took ~30 min of your time + 14 days of waiting; subsequent runs take ~5 min of your time to launch + 14 days of waiting. The audit evidence is intrinsic to the workflow, not a separate report you have to assemble.

This is the shape of every certification you’ll run in AtmanID — same flow for Workday, Snowflake, GitHub, anything with discoverable users and entitlements. The 5-extra-minutes-per-entitlement investment in Step 2 is what separates campaigns that produce real evidence from campaigns that produce rubber stamps.

Common pitfalls

  • Skipping Step 3 (verify access state). Launching a campaign on bad data wastes everyone’s time and pollutes the audit trail with bogus reviews. Always sanity-check first.
  • Routing all reviews to a single reviewer. Some admins do this for speed; it’s the highest-volume rubber-stamp pattern. Per-entitlement-owner routing is slower for the admin but produces real evidence. Use it.
  • Setting decision deadline shorter than 14 days. Reviewers have day jobs. 7-day deadlines produce rushed reviews and angry reviewers. 14-21 days is the sweet spot.
  • No non-response policy. Without Auto-Revoke on no-response, some reviews never close and the whole campaign drifts open indefinitely. Set it. Make it the default.
  • No follow-up on Revoke failures. If the connector failed to revoke 3 entitlements, those users still have access. Check the campaign’s remediation status and the Revocation Queue at closeout and chase any non-zero numbers.

Going further

© AtmanID · Privacy