Global Admin Operations
The Dashboard section of the Admin Portal is visible only to users with global or platform-level roles. It contains tools for managing the Eclipse platform itself, rather than a specific tenant. Access requires GLOBAL_ADMIN or equivalent permissions.
Global User Management
Navigate to: Dashboard → EFT Users
Global users are EFT Corporation staff accounts that have platform-wide access across all tenants. This section is used to create, view, and manage these accounts.
Creating a Global User
- Navigate to Dashboard → EFT Users.
- Click + Add User.
- Fill in the user details:
- First name, last name, email address
- Role (e.g.,
GLOBAL_ADMIN,PLATFORM_SUPPORT) - Authentication method (PKI, TOTP, or password)
- Click Save. An activation email is sent to the user.
Managing Global Users
The user table lists all platform-level users with their current status. Actions available per user:
- Edit — Update name, email, or role
- Deactivate / Reactivate — Toggle active status
- Reset Auth — Trigger re-registration of TOTP or PKI credentials
Properties Management
Navigate to: Dashboard → Properties
System properties are key-value pairs stored at the global platform level. They control platform-wide behaviour that is not tenant-specific — such as default rate limits, global feature flags, billing configuration data, and PTS batch settings.
Viewing Properties
The properties table lists all defined system properties. Use the search bar to filter by property name.
Creating a Property
- Click + Add Property.
- Enter the property name (key) and value.
- Click Save.
Property names follow a dot-notation convention (e.g.,
monthly.billing.config.42,platform.maintenance.mode). Do not create properties that duplicate tenant config keys — use tenant config items for tenant-scoped settings.
Editing a Property
- Click Edit on the property row.
- Update the value.
- Click Save.
Deleting a Property
- Click Delete on the property row.
- Confirm deletion. Deletion is permanent.
SDN / Sanctions List Upload
Navigate to: Dashboard → SDN Upload
The SDN (Specially Designated Nationals) upload tool allows platform administrators to update the sanctions screening list used by the Eclipse KYC pipeline.
Uploading an SDN List
- Navigate to Dashboard → SDN Upload.
- Click Upload File.
- Select the SDN list file (supported formats depend on your sanctions provider configuration — typically CSV or XML).
- Click Upload.
- The system processes the file and updates the in-memory sanctions list. Processing status is shown on screen.
The SDN list is used by the KYC
SdnCheckprocessor. All new and re-verified customers are screened against the updated list automatically.
Global Payments
Navigate to: Dashboard → Payment
Global payments allow platform administrators to initiate wallet-to-wallet payments outside of the normal tenant payment flow. This is primarily used for operational adjustments and inter-tenant transfers.
Initiating a Global Payment
- Navigate to Dashboard → Payment.
- Click + New Payment.
- Fill in:
- Source wallet ID
- Destination wallet ID
- Amount and currency
- Description
- Click Submit.
All global payments are logged with a full audit trail.
Global Bulk Transfer
Navigate to: Dashboard → Bulk Transfer
Global bulk transfer allows platform-level mass disbursement across wallets using a CSV upload. This is equivalent to the tenant-level wallet transfer bulk upload, but executed from the global context.
Uploading a Bulk Transfer File
- Navigate to Dashboard → Bulk Transfer.
- Click Upload CSV.
- The CSV format must be:
amount,description,toWalletId,externalUniqueId - Each row specifies one transfer. The
externalUniqueIdmust be unique per row to prevent duplicate processing. - Click Upload to submit the batch.
Monitoring Progress
The transfer progress panel shows:
- Total rows in the file
- Successfully processed
- Failed rows (with error descriptions)
- Remaining
A summary report is emailed to the logged-in user when the batch completes.
Global Ratify / KYC Management
Navigate to: Dashboard → Global Ratify
Global Ratify provides a platform-wide view of KYC verification results and allows manual review of queued verification tasks.
Ratify Dashboard
The ratify dashboard shows:
- Pending verification queue
- Recently processed verifications
- Summary statistics (pass rate, failure breakdown by rule)
Reviewing a KYC Result
- Select a record from the queue.
- The verification summary shows:
- Customer details
- Documents submitted
- Individual check results (facial match score, document validity, sanctions result, etc.)
- If manual intervention is required:
- Click Approve to pass the customer
- Click Reject with a reason code
- Click Request More Info to flag the customer for resubmission
OCR Check Review
Navigate to: Dashboard → Ratify OCR
The OCR check screen shows the raw output from document OCR processing — extracted fields, confidence scores, and comparison results. Use this to investigate failures in the document verification step of the KYC pipeline.
Global QR Codes / PTS Batch
Navigate to: Dashboard → PTS Batch
The PTS Batch section manages QR code generation and Postilion batch file operations at the global level.
Generating QR Codes
- Navigate to Dashboard → PTS Batch.
- Click + Generate QR Codes.
- Configure the batch parameters:
- Quantity
- Associated wallet type
- Expiry settings
- Click Generate. QR codes are created and available for download.
Batch Operations
The PTS Batch section also provides tools for managing Postilion settlement batch files. Access is restricted to roles with PTSBatch.MANAGE permission.
Global Configuration
Navigate to: Dashboard → Configuration
The Configuration section exposes global platform-level configuration items — the top of the three-tier config hierarchy (Global → Institution → Tenant).
Viewing Configuration Items
Configuration items are listed in a searchable table. Each item shows:
- Config key
- Current value
- Last modified timestamp
Editing a Configuration Item
- Click Edit on the config item.
- Update the value.
- Click Save.
Global config values are inherited by all tenants unless overridden at the institution or tenant level. Exercise caution when modifying global config — changes affect the entire platform.
Updated about 8 hours ago
