Docs/Verification/Approved, rejected,
Verification

Approved, rejected,

and revoked statuses Verification requests move through statuses that help users understand the outcome of the review process. These statuses are important because they explain where a verification request stands and what it means for the profile or workspace.

Approved

An approved status means the request successfully passed review.

What approved means

Approved generally means:

  • the review requirements were met
  • the identity or workspace passed the necessary checks
  • the badge or trust signal can now be shown where supported

Why approved matters

Approval helps:

  • increase trust
  • improve public credibility
  • support stronger hiring confidence
  • make the profile or workspace look more complete and legitimate

After approval

After approval, users and workspaces should:

  • keep their profile or branding consistent
  • maintain the quality of their public presence
  • continue using the badge responsibly as part of their trust profile

Rejected

A rejected status means the request did not meet the requirements during review.

What rejected means

Rejected usually means:

  • the proof was not sufficient
  • the identity was unclear
  • the public presence did not match the request
  • required information was missing
  • the request did not meet the platform standard

Why rejection can happen

Rejection is not always final. In many cases, it simply means the request was not strong enough yet.

What to do after rejection

If rejected:

  • review what was submitted
  • correct missing or inconsistent details
  • strengthen the profile or workspace
  • resubmit later if appropriate

Best practices after rejection

  • do not resubmit immediately without fixing the underlying issue
  • make the public identity clearer
  • improve profile completeness before trying again

Revoked

A revoked status means verification was previously approved but later removed.

What revoked means

Revocation may happen if:

  • the verified identity changes in a major way
  • the workspace or user no longer meets the trust standard
  • the badge is no longer considered valid under current review conditions

Why revoked matters

Revocation helps keep trust signals meaningful over time. A badge should not remain active if the underlying credibility or identity basis has changed significantly.

What to do after revocation

If verification is revoked:

  • review what changed
  • restore consistency where possible
  • improve the relevant profile or workspace
  • request verification again later if appropriate

Why these statuses matter

These statuses help users understand that verification is a real process, not just a cosmetic label. They make trust signals stronger because they reflect actual review outcomes.

💡Best practices

  • treat approval as something to maintain, not just achieve
  • keep public identities consistent over time
  • correct issues before resubmitting after rejection
  • understand that revocation protects the credibility of the system

Billing