Verification, Moderation & Trust
Manage verification, reporting, moderation, suspension, appeal and trust-badge reference values.
Verification Categories
Use the existing Verification Category collection to group verification subjects and requirements.
Name of Category | Items Verified | Actions |
|---|
Moderation Action Categories
Classify administrator or moderator actions without storing the action event itself in this reference collection.
Name | Actions |
|---|
Report Categories
Use as broad groupings for user reports. Individual selectable reasons belong under Report Reasons when both levels exist.
name | description | Actions |
|---|
Badge Categories
Group trust, verification, participation or achievement badges without granting a badge automatically.
Name | Actions |
|---|
Verification Levels
Preserve the established L1 Basic through L6 Critical scale and its required review controls.
Level Code | Name of Level | Actions |
|---|
Verification Statuses
Preserve stable values used by verification workflows, including pending, review, verified, rejected, expired, suspended and escalated states.
Display Name | Description | Actions |
|---|
Verification Methods
Use the existing Verification Method collection for supported review methods; actual evidence remains protected.
Description | Method Name | Actions |
|---|
Verification Requirements
Use the existing Verification Requirements collection and connect each requirement to its category, level and applicable subject.
Requirement Name | Actions |
|---|
Verification Document Types
Use or relabel Additional Verification Documents Types where it is the canonical source; do not duplicate it.
| Document type | Applies to | Status | Actions |
|---|---|---|---|
| ExampleNational identity document | Individual account | Demo only |
Moderation Statuses
Control moderation lifecycle separately from account, content-publication and verification statuses.
Name | Description | Actions |
|---|
Report Reasons
Provide specific user-selectable reporting reasons beneath the appropriate Report Category.
Name | Description | Actions |
|---|
Flag Reasons
Use for internal or automated flags and retain the selected reason on the moderation record.
Name | Description | Actions |
|---|
Suspension Reasons
Use explicit, reviewable suspension reasons and preserve evidence, authority and duration on the operational record.
Name | Description | Actions |
|---|
Rejection Reasons
Scope each reason to verification or moderation. Do not mix it with offer, request or booking rejection reasons.
| Reason | Context | Status | Actions |
|---|---|---|---|
| ExampleDocument unreadable | Verification | Demo only |
Appeal Types
Classify appeals and route them to an authorised reviewer independent of the original decision where practical.
| Appeal type | Description | Status | Actions |
|---|---|---|---|
| ExampleVerification decision appeal | Review of a rejected verification | Demo only |
Badge Types
Define the individual badge beneath its category; badge issuance belongs in operational badge records.
Badge Label | Description | Actions |
|---|
DrapCode connection notes
- Create or duplicate this page at the route above and restrict page access to authorised administrators and moderators.
- Bind each accordion table and Add/Edit action to the existing collection represented by its heading. Keep current technical names until dependencies are checked.
- Keep Verification Subject, Verification Queue, Verification Master Collection and Verification Documents on protected operational pages; do not treat them as static dropdown collections.
- Connect Verification Category → Verification Requirement and Verification Level; connect Verification Document Type and Method only where applicable.
- Use Report Category → Report Reason and Badge Category → Badge Type. Scope Rejection Reasons to verification or moderation so they are not confused with offer or booking decisions.
- Require authorised human review for verification, suspension, appeal and serious moderation decisions. Reference data must never trigger those decisions by itself.
- Record every material configuration and case action in Audit Logs with actor, time, record, action and before/after values. Send appropriate user/admin notifications without exposing protected evidence.
- After changes, test verification submission/review, moderation queue, reporting, suspension, appeal, badge issuance, direct URL access and non-admin permissions.