Backoffice Actions
The DEUSS Backoffice is the administrative workspace for operators who manage Core platform data and intervene in controlled operational scenarios. The current application exposes write actions for onboarding, company governance, compliance, freeze handling, user verification, and bond issuance lifecycle operations.
For the step-by-step operator journey with screenshots, see Backoffice Admin Actions.
BO Roles
| Role | Scope |
|---|---|
BO_VIEW | Read-only access to the backoffice. The user can display data but cannot execute write operations. |
BO_FREEZE_OPERATOR | Incident/compliance containment role. Enables freeze/disable operations over entities, wallets, deals, markets, and orderbook objects. |
BO_COMPLIANCE_OPERATOR | Compliance role for AML, risk statuses, final settlement burn, and sensitive compliance interventions. |
BO_ONBOARDING_OPERATOR | Onboarding role for entity registration, issuer/investor status setup, company wallet creation, and basic onboarding operations. |
BO_COMPANY_OPERATOR | Role for broker, manager, and company/user account relationship management. |
BO_BOND_OPERATOR | Role for bond lifecycle operations, scoring, publish, issue, cancel, suspend, and close. |
BO_PAYMENT_OPERATOR | Role for payment and settlement operations over marketplace/orderbook deals and trades. |
BO_SUPER_ADMIN | Full application access to all BO write actions. The corresponding chain role must still exist on the admin wallet for chain-backed actions. |
Implemented Admin Actions
The table below lists the write actions currently exposed by the inspected deuss-backoffice application.
| Area | Admin action | Required BO permission / role source | Business effect |
|---|---|---|---|
| Users | Create user | canCreateUser from BO_ONBOARDING_OPERATOR or BO_SUPER_ADMIN | Registers a new user in the Core registry context. |
| Users | Update identity verification status | canUpdateUserIdentityState from BO_COMPLIANCE_OPERATOR or BO_SUPER_ADMIN | Sets a user's identity verification state to NONE, PENDING_VERIFICATION, VERIFIED, or FAILED. |
| Companies | Create issuer company | canCreateCompany from BO_COMPANY_OPERATOR or BO_SUPER_ADMIN | Creates a company with an issuer profile for admission and issuance workflows. |
| Companies | Create investor company | canCreateCompany from BO_COMPANY_OPERATOR or BO_SUPER_ADMIN | Creates a company with an investor profile for investment and trading workflows. |
| Companies | Add issuer profile to existing company | canEditCompany from BO_COMPANY_OPERATOR or BO_SUPER_ADMIN | Adds issuer classification data to an existing company. |
| Companies | Add investor profile to existing company | canEditCompany from BO_COMPANY_OPERATOR or BO_SUPER_ADMIN | Adds investor capability to an existing company. |
| Companies / Compliance | Update AML verification state | canEditAmlState from BO_COMPLIANCE_OPERATOR or BO_SUPER_ADMIN | Sets company AML state to PENDING_VERIFICATION, VERIFIED, REJECTED, or INFORMATION_UPDATE_NEEDED. |
| Companies / Freeze | Freeze company entity | canFreezeCompany from BO_FREEZE_OPERATOR, BO_COMPLIANCE_OPERATOR, or BO_SUPER_ADMIN | Starts a company-level freeze operation through the Core admin API. |
| Companies / Freeze | Unfreeze company entity | canFreezeCompany from BO_FREEZE_OPERATOR, BO_COMPLIANCE_OPERATOR, or BO_SUPER_ADMIN | Reverses the company-level freeze state where backend rules allow it. |
| Companies / Freeze | Freeze issuer profile | canFreezeCompanyProfile from BO_FREEZE_OPERATOR, BO_COMPLIANCE_OPERATOR, or BO_SUPER_ADMIN | Disables the issuer profile while preserving the company record. |
| Companies / Freeze | Unfreeze issuer profile | canFreezeCompanyProfile from BO_FREEZE_OPERATOR, BO_COMPLIANCE_OPERATOR, or BO_SUPER_ADMIN | Restores the issuer profile from frozen state where backend rules allow it. |
| Companies / Freeze | Freeze investor profile | canFreezeCompanyProfile from BO_FREEZE_OPERATOR, BO_COMPLIANCE_OPERATOR, or BO_SUPER_ADMIN | Disables the investor profile while preserving the company record. |
| Companies / Freeze | Unfreeze investor profile | canFreezeCompanyProfile from BO_FREEZE_OPERATOR, BO_COMPLIANCE_OPERATOR, or BO_SUPER_ADMIN | Restores the investor profile from frozen state where backend rules allow it. |
| Companies / Freeze | Freeze wallet | canFreezeWallet from BO_FREEZE_OPERATOR, BO_COMPLIANCE_OPERATOR, or BO_SUPER_ADMIN | Freezes a company wallet by wallet address. |
| Companies / Freeze | Unfreeze wallet | canFreezeWallet from BO_FREEZE_OPERATOR, BO_COMPLIANCE_OPERATOR, or BO_SUPER_ADMIN | Restores a company wallet from frozen state where backend and chain rules allow it. |
| Bond Issuance | Create bond issuance draft | canCreateIssuanceDraft from BO_BOND_OPERATOR or BO_SUPER_ADMIN | Creates a new off-chain issuance draft for an issuer company. |
| Bond Issuance | Publish / issue bond | Draft availability in the UI; operationally belongs to BO_BOND_OPERATOR or BO_SUPER_ADMIN | Initiates bond publication on-chain. This action is presented as irreversible in the UI. |
Read-Only Admin Views
BO_VIEW enables operators to inspect the backoffice data surface without write actions. Read-only views include:
- Company lists, filters, details, issuer/investor profiles, compliance status, scoring history, deals, offers, and transfers.
- User lists, filters, details, wallet addresses, distributor IDs, and identity status.
- Bond issuance lists, filters, details, documents, marketing assets, offers, deals, payments, and transfers.
- Platform-wide trading views for offers, counter offers, deals, and token transfers.
Role Coverage Notes
Some BO roles have a broader business scope than the currently implemented UI:
BO_PAYMENT_OPERATORis defined for payment and settlement operations, but the inspected backoffice currently exposes trading and settlement information as read-only indexer-backed views.BO_FREEZE_OPERATORis described at platform scope for entities, wallets, deals, markets, and orderbook objects. The current UI exposes freeze/unfreeze actions for company entities, issuer profiles, investor profiles, and wallets.BO_BOND_OPERATORcovers the full bond lifecycle at business level. The current UI exposes issuance draft creation and publish/issue initiation.- Chain-backed actions still depend on the corresponding on-chain role being present on the admin wallet. A BO role grants application authorization; it does not by itself grant blockchain authority.