Help Library

Start with My Profile to build your personal record, Check Myself to review your own screening, or Check Someone Else to invite another individual. These journeys use your existing Persona sign-in. Hiring managers use IDC for organization orders and team operations; Persona is not a second employer dashboard. Choose the journey that matches your purpose before entering information at its destination.

Sandbox identifies a test journey using fictional results and no actual search. The displayed test payment does not charge money. Completion confirms that the test workflow finished, not that the person passed a real screening. Hiring managers and candidates must not use these results as verified evidence or for employment, housing, or eligibility decisions.

Hiring managers may review only the claims or report sections a person has permitted them to access. A shared profile does not unlock private documents, unrelated checks, or the candidate's account. Check Someone Else is a personal-purpose journey, not a shortcut for employer screening. Use IDC for organizational orders, approvals, decisioning, and the separately authorized employment workflow.

Pending indicates unfinished work, not an adverse finding about a person. Read the specific status and next available action: authorization, payment, provider configuration, or processing may still be incomplete. Failed describes a workflow problem requiring attention; it is not a hiring decision. Use recorded results and readiness labels to distinguish completion from provider availability.

Build your profile and enter credentials such as employment, education, licenses, certifications, and references. Review names, dates, and supporting information before requesting an available verification. Saving information is not proof that a source confirmed it; self-entered details remain distinct from verified inputs.

Evidence from an eligible verification source must support the item before it is presented as Verified. A completed form, uploaded file, payment, or sandbox result does not establish verification. Check the source, status, and freshness information on the item rather than treating every saved detail as an equally supported claim.

Identity guides you through government-ID submission, a selfie and liveness challenge, and the provider result. Follow the document and capture requirements shown at each step, including challenge expiry. Check Provider readiness before expecting a real verification. Where the page identifies a sandbox, use fictional test material only; simulated completion is not genuine identity proof.

Verification depends on the credential type, identified source, and configured provider. Open the credential, review its details, and authorize the available verification action. Saving a source contact does not itself contact that person or confirm the claim. When a provider is unavailable, the credential remains pending rather than receiving an unsupported confirmation.

Private evidence is not automatically included in a shared profile. Government-ID images, biometric evidence, sensitive source identifiers, source contacts, and dispute evidence stay outside the recipient claim view. Sharing an approved assertion is different from sharing its underlying files. Inspect the recipient preview instead of assuming an upload becomes a public attachment.

Choose Check Myself, review the package scope and displayed price, record authorization, and complete the available payment step. Start the check, follow its progress, and open the private report when ready. The current package uses simulated payment and fictional screening; the separate FBI Self Check follows its own submission process. Package results return to Persona.

Progress appears on the personal check through authorization, test payment, screening, and report readiness. Use Update Status while processing; automatic polling is not enabled. Open Personal Updates from the dashboard for in-app notices about participation, readiness, failures, and access changes. These notices do not mean an email or text was sent; the current workflow uses private in-app updates.

Monitoring remains paused in the current build. A freshness date or completed check does not enroll you in recurring screening, and Update Status retrieves the existing check rather than ordering a new one. Any future monitoring activation must clearly identify supported coverage, frequency, price, consent, cancellation, and private change alerts before separate approval.

Submission and any required payment follow the official FBI process opened from the FBI Self Check workspace. Persona records your personal-review purpose and submission progress; after receiving the result, you can store the delivered PDF in its owner-only area. This result is excluded from employer reports and recipient shares. Follow the dedicated correction link for an FBI record challenge.

Refreshes ask for updated source verification of a particular credential version. Review the purpose, available method, and any displayed cost before approving; a recipient request does not automatically authorize provider work. Paid options depend on configured checkout, and a pending payment is not a completed verification. Follow the request state until a source result is recorded with provenance.

Retry the existing order only when its message offers that action. A temporary connection or response-verification problem preserves the personal order and existing payment reference, so do not create another purchase to refresh status. A recorded provider failure needs attention before another check starts. The current package is sandbox-only; its retry path never requires a second real charge.

Cancellation withdraws authorization and report access, but it does not erase retained order or audit history. If service cancellation cannot be confirmed, local access remains withdrawn and Confirm Cancellation retries that outstanding step. Use Revoke Share or Revoke Requester Access when only another person's access should end. Canceling the whole check has broader consequences.

Participation is required before an invitation can become a personal screening order. The recipient signs in with the matching verified Persona email, reviews the request, and approves authorization and requester sharing. They may decline instead; expired or canceled invitations cannot proceed. An invitation alone does not authorize screening, and the recipient must decide first.

Acceptance records participation and consent; it does not itself charge the recipient or requester. The requester handles the separate payment confirmation before screening starts. Today this is a clearly labeled sandbox confirmation with no real charge. Never interpret a successful test receipt as a completed commercial payment.

Invitations for personal checks appear under Check Someone Else for the matching verified Persona email. Review the requester and consent choices there; use Personal Updates for related in-app notices. Employer-originated access or screening requests appear separately under Requests. A notice being recorded does not prove email delivery, so check the appropriate inbox.

Requests should be reviewed individually for the named organization, requester, purpose, and requested information. Profile Access concerns selected portable claims; New Screening requires a separate authorization for an employer screening workflow. Approve only the request you intend to accept, or decline it. Approval of one request is not blanket access for every organization.

Ownership stays with the individual using Persona. A hiring manager cannot automatically browse a candidate's private profile or personal report merely because they work together. Profile access, personal report sharing, and employer screening are separate choices. Review the named recipient and requested purpose before granting permission.

Preview Recipient View lets you inspect selected profile claims before issuing a profile share. Personal report sharing is separate: select the recipient email, report sections, and duration, confirm the share, then use Preview Recipient View on that grant. Report recipients need their own matching verified Persona sign-in. Unselected report sections are not visible.

Revocation stops further access through the affected share, and expiration also closes access. Manage profile grants under Sharing and personal report grants on the check. Invitation subjects can use Revoke Requester Access without canceling their own check. Revocation cannot erase information a recipient already saw or retained outside Persona, but the owner's private report remains unchanged.

Recipients use the profile-sharing link supplied by the owner and complete its recipient-email confirmation before viewing approved claims. A personal report share follows a different route: sign in to Persona with the matching verified email and open Reports shared with me. Neither route provides the owner's login or permission to browse unrelated personal information.

Access can end when the owner revokes a grant, its expiry is reached, or a profile share exhausts its permitted views. A mismatched recipient email also prevents entry. Personal report shares additionally depend on current report authorization and account eligibility. Ask the owner to review the grant rather than trying another person's credentials.

Downloads are not permitted in the shared-profile recipient view, and personal report sharing does not expose a download action. Viewing selected claims does not grant access to source files, identity evidence, or the owner-only FBI result. Owners may have separate download controls for their own records; those controls are not inherited by another viewer.

Versions keep a profile share tied to the exact claim selected when it was issued. Editing a credential creates a new version rather than silently replacing the recipient's approved snapshot. The recipient view can flag that a newer owner version exists and show freshness or dispute information. Review those signals before relying on an older snapshot.

Corrections & Disputes tracks credential changes and challenges to source-verification information. Open the relevant credential to edit your own details or challenge its verification result; prior versions and recorded activity remain preserved. Hiring managers should ask the owner to review a discrepancy rather than edit that person's claims. This credential workflow does not rewrite personal screening results.

Recovery starts with Forgot Password on the Persona sign-in page using the exact email for that account. Persona and IDC have separate accounts; a login for one does not automatically work for the other. Check the configured email inbox, or the local test inbox when testing. When MFA is enabled, use your authenticator or an unused recovery code, and never share passwords or codes.

Security checks may require email verification, a fresh sign-in, or completion of your enabled MFA challenge before a protected page opens. Suspended or inactive accounts cannot continue protected workflows. Return through the normal Persona sign-in and Security controls instead of using a different person's session. These checks protect access; they do not indicate that screening found a match.