Skip to main content

Credential Statuses

Credential statuses show where a credential is in its journey from creation to activation. This page explains what each status means and when you'll see it.

Status Overview​

Credential statuses fall into these main stages:

  • Preparation: Being created and edited
  • Approval: Waiting for review (if your policy requires it)
  • Production: Being made or issued
  • Active Use: Ready and in use
  • Deactivated: Temporarily turned off
  • End of Life: Replaced, cancelled, or deleted

Preparation Statuses​

These statuses show credentials that are being prepared before production.

Registered​

Just created. Being prepared. Not submitted for ordering yet.

  • How it gets here: A new Credential is started
  • What happens next: You can move it to preview, requested, waiting_for_approval (if approval is needed), or in_queue (in fast-track setups)
  • Can it move forward? Yes
  • Notes: This is a safe place to edit details and photos before submitting

Preview​

A visual preview exists (e.g., card front/back). Still in preparation.

  • How it gets here: You generated a preview while preparing the Credential
  • What happens next: You can move it to requested, waiting_for_approval, or in_queue
  • Can it move forward? Yes
  • Notes: Use this to catch mistakes before ordering or issuing

Requested​

Submitted for ordering. Added to the shopping cart when using the standard flow.

  • How it gets here: You submit the Credential for ordering
  • What happens next: After checkout it moves to in_order, or to waiting_for_approval if an approver must sign off first
  • Can it move forward? Yes
  • Notes: This is the "I'm ready—put me in the order" step

Approval Statuses​

These statuses show credentials waiting for approval.

Waiting for Approval​

Needs an approver to review before it can move forward.

  • How it gets here: Your policy requires approval for this Credential
  • What happens next: After approval, it moves to in_queue (fast-track flows) or requested (standard flow). If not approved, it may be cancelled
  • Can it move forward? Yes (after approval)
  • Notes: Approvers see what they need to approve; nothing moves until they decide

Production Statuses​

These statuses show credentials being made or issued.

In Queue​

Approved (or no approval needed) and queued to start preparation.

  • How it gets here: Approved (or auto-approved) and placed in the queue
  • What happens next: Moves to in_production (cards) or straight to active/inactive for some mobile setups
  • Can it move forward? Yes
  • Notes: Some tenants start automatic preparation from here

In Order​

Placed in an order. Waiting for production (for cards) or for mobile handling.

  • How it gets here: The order has been placed/checked out
  • What happens next: Moves to in_production (cards) or active/inactive (mobile IDs with automatic handling)
  • Can it move forward? Yes
  • Notes: Batches appear here too; each Credential still has its own progress

In Production​

Being made. For cards: printing/encoding is in progress. For mobile IDs: this state is brief and will quickly move forward automatically.

  • How it gets here: Production has started
  • What happens next: Moves to quality_check (cards) or active/inactive (mobile)
  • Can it move forward? Yes
  • Notes: For mobile, this can be a quick hop; for cards, this covers the making/encoding step

Quality Check​

Finished making and awaiting a final review.

  • How it gets here: Card production completed and is awaiting a final check
  • What happens next: If approved, moves to produced. If not approved, goes back to in_production for rework
  • Can it move forward? Yes (after approval)
  • Notes: Use this step to ensure photos, text, and encoding are correct

Produced​

Fully made and approved. Ready for handout or activation.

  • How it gets here: Passed quality check or completed production in a fast-track setup
  • What happens next: Moves to active (put into use), in_production (rework), or deleted (if removed)
  • Can it move forward? Yes
  • Notes: For cards, you can now hand out; for mobile, next is typically activation

Active Use Statuses​

These statuses show credentials that are ready to use or in use.

Active​

Ready and in use. The credential works wherever it's connected (e.g., access control or Mobile ID).

  • How it gets here: Activated after being produced/issued
  • What happens next: Can move to deactivated, replaced, or deleted (depending on policy)
  • Can it move forward? Yes
  • Notes: This is the normal "live" state

Inactive​

Mainly for mobile IDs. Prepared but not yet turned on (manual provisioning required before use).

  • How it gets here: A mobile ID is prepared but not activated automatically
  • What happens next: Can move to active or deactivated
  • Can it move forward? Yes
  • Notes: Common for manual provisioning flows

Deactivated​

Temporarily turned off. Can be re‑activated later when appropriate.

  • How it gets here: You turned off a live Credential (lost card, leave of absence, etc.)
  • What happens next: Can move to active (restore), replaced, or deleted
  • Can it move forward? Yes
  • Notes: Use when you don't want to remove it permanently

End of Life Statuses​

These statuses show credentials that are no longer in active use.

Replaced​

An older credential has been superseded by a new one. Kept for history, no longer the one in use.

  • How it gets here: A new Credential was created to supersede this one
  • What happens next: Typically stays replaced; may later be deleted based on retention rules
  • Can it move forward? Effectively no (for operational use)
  • Notes: Keeps a clean history of what changed and when

Cancelled​

Stopped before production. Often means it was removed from an order/cart and won't be made.

  • How it gets here: The order item was removed or the request was withdrawn
  • What happens next: Usually stays cancelled; you can create a new Credential if needed
  • Can it move forward? Usually no
  • Notes: Prevents unwanted production

Deleted​

Permanently removed. Personal details are anonymized and the credential is no longer available.

  • How it gets here: An admin deleted the Credential
  • What happens next: Nowhere
  • Can it move forward? No
  • Notes: This is permanent; used for cleanup or compliance

Duo ID Statuses​

These statuses show credentials where a Duo ID invite was sent so the person can provide their own details.

Duo Requested​

A Duo ID invite was created and (optionally) emailed so the person can supply details (like a photo).

  • How it gets here: You start a Duo ID invite for the person to complete details
  • What happens next: After the person submits, moves to duo_waiting_for_approval, or duo_rejected if the attempt is ended
  • Can it move forward? Yes
  • Notes: You can resend the invite if needed

Duo Waiting for Approval​

The person has sent in their details. Waiting for an approver to review.

  • How it gets here: The invited person submitted their information
  • What happens next: After approval, moves to requested or in_queue (depending on your flow), or duo_rejected if rejected
  • Can it move forward? Yes (after approval)
  • Notes: After approval, it continues like any other Credential

Duo Approved​

Not commonly used in today's flow. After approval, credentials typically move straight into "requested" or "in_queue".

  • How it gets here: Legacy paths may mark "approved"
  • What happens next: Moves to requested or in_queue
  • Can it move forward? Yes
  • Notes: Most tenants skip this explicit status today

Duo Rejected​

The submission was rejected. If needed, a new invite can be sent with corrections.

  • How it gets here: The approver rejected the submission
  • What happens next: Can move to duo_requested (if you send a fresh invite), or it can remain rejected
  • Can it move forward? Usually no, unless you retry
  • Notes: Capture the reason; it helps when resending

Rare or Legacy Statuses​

These statuses are rarely used in current workflows but may appear in special cases.

Soft Deleted​

Not commonly used for credentials. Reserved for special cases where items are hidden but kept.

  • How it gets here: Rare internal flows
  • What happens next: Can move to deleted
  • Can it move forward? No (but it's close to end‑of‑life)
  • Notes: Not visible in normal daily lists

Rejected​

Rarely used for credentials in the current flow. Kept for compatibility with earlier processes.

  • How it gets here: Legacy or special handling
  • What happens next: Can move to replaced or deleted (depending on policy), or remain rejected
  • Can it move forward? Usually no in practice
  • Notes: Newer flows typically use approval/cancel paths instead

Understanding Status Flow​

Credentials move through statuses in a logical flow, but the exact path depends on:

  • Your policy settings: Whether approval is required
  • Credential type: Cards vs. mobile IDs follow slightly different paths
  • Workflow setup: Fast-track vs. standard flows
  • Quality checks: Whether rework is needed

Most credentials follow a path like:

  1. Registered → (optional) Preview
  2. Requested → (optional) Waiting for Approval
  3. In Order → In Production → (cards) Quality Check
  4. Produced → Active

Common Questions​

Why is my credential stuck in one status?​

  • Check if approval is required and waiting
  • Verify the credential hasn't been cancelled or rejected
  • For mobile IDs, check if manual provisioning is needed

Can I skip some statuses?​

Some fast-track setups may skip certain statuses (like approval or quality check), but most credentials follow the standard flow.

What's the difference between deactivated and deleted?​

  • Deactivated: Temporarily turned off; can be reactivated later
  • Deleted: Permanently removed; cannot be recovered