> ## Documentation Index
> Fetch the complete documentation index at: https://developers.argosidentity.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Product updates: May 2026

> ARGOS Identity product updates for May 2026

Hello, this is ARGOS Identity.

Here are the new features and improvements we delivered in May.

***

## Error page segmentation & infinite retry loop prevention

<span style={{backgroundColor: '#EEF4FF', color: '#0064FF', padding: '4px 12px', borderRadius: '16px', fontSize: '13px', fontWeight: '600'}}>Feature Improvement</span>

When key engine processes — such as ID liveness, selfie (Passive) liveness, face comparison, or Korean government authenticity verification — fail consecutively, users were previously caught in an infinite retry loop. With this improvement, if the same error accumulates **3 times**, the user is now directed to a **dedicated error page for that specific error type** instead of being offered another retry. Fewer than 3 occurrences are still handled with a recapture prompt or notification.

### New error codes

**Engine errors (`SE`)** — each engine has its own dedicated error page, so you can immediately identify which engine failed.

| Error code | Engine                                                    |
| ---------- | --------------------------------------------------------- |
| `SE-50020` | ID Liveness                                               |
| `SE-50021` | Selfie Passive Liveness                                   |
| `SE-50022` | Face Compare                                              |
| `SE-50030` | Korean government verification — Resident Registration ID |
| `SE-50031` | Korean government verification — Driver's License         |
| `SE-50032` | Korean government verification — Passport                 |
| `SE-50033` | Korean government verification — Alien Registration       |

**Capture/step retry loop (`LO`)** — when the same error accumulates **3 times** during ID capture or step processing, the user is moved to a loop-block page. Unmapped loop errors fall back to a generic page.

| Error code | Trigger condition                             |
| ---------- | --------------------------------------------- |
| `LO-30001` | OCR ID recognition failure                    |
| `LO-30002` | Data processing error                         |
| `LO-30003` | Required parameter missing                    |
| `LO-30004` | requestId missing                             |
| `LO-30005` | ID image quality too low                      |
| `LO-99999` | Loop error not mapped to the above (Fallback) |

### Error Handling Method — Warning conversion & Custom Policy integration

You can configure how each engine error is handled in the dashboard: **`Error` (default — redirect to a dedicated error page) ↔ `Warning` (skip that verification and continue)**. This is set per item for **ID Liveness · Selfie Passive Liveness · Korean government verification**.

When set to `Warning`, the user is not redirected to an error page; only that verification is skipped and the subsequent KYC process continues. The resulting Warning record can then be caught by the **"Warning occurred" trigger in Custom Policy**, applying follow-up actions such as ARGOS Score penalties, holding (Pending), or rejection per your policy. (This follows the same pattern as the Expired ID Warning handling.)

<Info>
  To configure the Error Handling Method, see the [Anti-Fraud & Forgery Prevention](/dashboard/en/project-management/policy-and-authentication/anti-fraud-and-forgery-prevention) guide; to build a Custom Policy that uses the Warning, see the [KYC Process](/dashboard/en/project-management/policy-and-authentication/kyc-process) guide; for the full error code mapping and error page definitions, see the [Error Codes and Pages](/en/idcheck/reference_tables/Error-codes-and-pages) reference.
</Info>

***

## Unsupported browser and device notification improvements

<span style={{backgroundColor: '#EEF4FF', color: '#0064FF', padding: '4px 12px', borderRadius: '16px', fontSize: '13px', fontWeight: '600'}}>Feature Improvement</span>

When users access the liveform from unsupported environments — including older browsers, environments without WebAssembly support, or devices running **Android OS below version 9** — they previously received only a generic notice with no error code. This improvement assigns the error code **`RT-60002`** and includes a link to the supported environment guide. Clients can now immediately identify the reason for the block and provide users with specific guidance.

<Tip>
  For the list of supported browsers and devices, see the [Recommended Browsers and Devices](/en/idcheck/getting-started/recommended-browsers-and-devices) guide. For the full error code mapping, see the [Error Codes and Pages](/en/idcheck/reference_tables/Error-codes-and-pages) reference.
</Tip>

***

## Administrator permission management (RBAC) improvements

<span style={{backgroundColor: '#EEF4FF', color: '#0064FF', padding: '4px 12px', borderRadius: '16px', fontSize: '13px', fontWeight: '600'}}>New Feature</span>

Permissions (roles) for ARGOS internal administrators and project external administrators are now **separated**, with each role independently controlling which items can be viewed, modified, or deleted on the dashboard. Roles are divided into Owner, Leader, Member, and Guest.

<Frame caption="Administrator Settings — role-based (Owner·Leader·Member·Guest) permission separation and administrator list">
  <img src="https://mintcdn.com/argosidentity/kQgxAhUlTpk4TIQ7/images/dashboard/new/rbac/admin_role_list_en.png?fit=max&auto=format&n=kQgxAhUlTpk4TIQ7&q=85&s=7116ee76b273afc6c315866665d6f98a" alt="Administrator list with per-role attributes and attribute permission guide" width="3467" height="1046" data-path="images/dashboard/new/rbac/admin_role_list_en.png" />
</Frame>

### Personal information display control

Depending on the assigned role, **data fields in a user's submission are displayed masked**. In the **Personal Info Visibility by Role** setting, you specify per item which roles (Owner·Leader·Member·Guest) can see each piece of personal information (PII) — such as resident registration numbers, document numbers, identification numbers, and ID card images — and any unchecked item appears masked to administrators with that role.

<Info>
  Masking applies to **on-screen display only**; the actual stored data and API response data are not changed. (e.g., Name `John Doe` → `***`, Date of Birth `1990-01-15` → `****-**-**`)
</Info>

<Frame caption="Personal Info Visibility by Role — per-role display/masking of submission data fields">
  <img src="https://mintcdn.com/argosidentity/kQgxAhUlTpk4TIQ7/images/dashboard/new/rbac/pii_visibility_by_role_en.png?fit=max&auto=format&n=kQgxAhUlTpk4TIQ7&q=85&s=26b130d452f1036d8f782d8936d062df" alt="Per-item Owner·Lead·Member·Guest visibility checkboxes with masking examples" width="946" height="1308" data-path="images/dashboard/new/rbac/pii_visibility_by_role_en.png" />
</Frame>

<Note>
  Currently, only the **ID Photo (image)** field can be adjusted in the **Personal Info Visibility by Role** setting. The other fields cannot be adjusted yet — configurable settings will be provided later.
</Note>

### Permission-based feature control

Actions that exceed a role's permission scope — such as saving options, deleting records, or canceling administrator invitations — are handled consistently: the relevant button is either hidden entirely or accompanied by a permission notice. This prevents unauthorized operations at the source.

<Tip>
  For access control configuration, refer to the [System Operation](/dashboard/en/project-management/project-settings/system-operation) and [Access Control](/dashboard/en/project-management/security-settings/access-control) dashboard guides.
</Tip>

***

ARGOS continues to improve its identity verification service for stronger security and a better user experience.

Thank you for using ARGOS Identity.
**The ARGOS Identity team**