> ## Documentation Index
> Fetch the complete documentation index at: https://docs.frankieone.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Statuses and Tags
## Introduction
Every profile (entity) and every workflow in FrankieOne Portal carries clear labels— **entity state**, **event statuses**, **issue tags**, and a **risk level**.\
These labels help you spot successes, problems, and urgent risks at a glance. Use this guide to learn what each label means and how to act on it.
## Entity State
| State | What it means | Typical next step |
| :---------- | :---------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Unchecked | Entity has been created but no verification checks have been run yet. | Initiate verification workflow to begin the checking process. |
| Active | Entity has passed all required checks and is currently in good standing. | Monitor for any changes or periodic re-verification as needed. |
| Archived | Profile is stored but hidden from the default list. | For entities marked as "Archived," this is a reversible action that simply hides the profile from the default view. Unarchive if further work is needed. |
| Blocklisted | Entity has been added to a blocklist due to high risk or compliance concerns. | Review blocklist reason and determine if an appeal is possible or if permanent blocking is appropriate. |
| Duplicate | Entity has been identified as a duplicate of another profile in the system. | Compare both profiles and decide whether to merge or keep separate. |
You can filter the Entities table by these statuses using **Entity status** in the Filters modal.
## Event Statuses
The event status tells you the current status of the entity. This is based on the status of the most recent workflow run on that entity.
| Status | What it means | Typical next step |
| :-------------- | :--------------------------------------------------- | :------------------------------------------------------------ |
| Unchecked | Checks are still running or queued. | Wait for workflow to finish or retrigger if stuck. |
| Needs Attention | At least one check needs manual review. | Open the profile, review issues, decide to Pass or Fail. |
| Passed | All required checks were met. | None—onboarding is complete. |
| Manually Passed | A user reviewed the profile and marked it as Passed. | Record the reason for manual pass. |
| Failed | Checks revealed blocking issues. | Review issues and decide if appeal or correction is possible. |
| Manually Failed | A user reviewed and failed the profile. | Record the reason and notify the applicant if required. |
The Event status always reflects **the most recent workflow** run on the profile, so you instantly know the latest outcome.
## Entity Issues
High-level issue tags appear in the Entities list so you can decide which profile to open first.\
Inside the profile you will find **detailed sub-issues** (for example, which specific sanction list matched).
| Category | What it means | Typical next step |
| :---------------- | :---------------------------------------------------------------------------------------------------------------------- | :----------------------------------------------------------------------------------- |
| **KYC** | Issues related to Know Your Customer verification, such as no match or partial match found. | Review the specific KYC failure reason and request additional information if needed. |
| **BAD\_DATA** | Problems with the data provided by the customer, such as incorrect name, DOB, address, ID, email, or mobile. | Identify which specific data element is problematic and request correction. |
| **AML** | Anti-Money Laundering concerns including PEP status, adverse media, sanctions matches, or negative news. | Review the match details and determine if enhanced due diligence is required. |
| **IDV** | Identity verification issues such as data consistency problems, document validation failures, or compromised documents. | Examine the specific IDV failure and request additional verification if appropriate. |
| **Blocklisted** | The entity has been added to a blocklist, preventing further processing. | Review the blocklist reason and determine if an appeal is possible. |
| **Duplicate** | The system has detected this person may already have an account. | Compare both profiles and decide whether to merge or keep separate. |
| **System** | Technical issues within the platform that prevented successful verification. | Contact technical support or retry the verification process. |
| **Expiry** | Documents or verifications have expired and need to be renewed. | Request updated documents or re-verification. |
| **Informational** | Non-critical information that requires attention but doesn't necessarily block onboarding. | Review the information and take appropriate action if needed. |
The **Entities list** shows only the **high-level tags** above. Open the profile for a breakdown of every failed check and exact match details.
## Risk Level
| Risk level | Meaning | Typical business rule |
| ------------ | ---------------------------------- | ---------------------------------------- |
| Low | Meets the safest score range. | Auto-approve. |
| Medium | Some moderate risk factors. | May ask for extra documents. |
| High | Significant risk factors. | Needs manual review and enhanced checks. |
| Unacceptable | Risk score exceeds your threshold. | Automatically fail profile. |
The Risk level shown in the entities list is **always based on the last completed workflow**, so it changes as new checks finish.