Skip to content

Operator Manual — BackOffice

The BackOffice is the central tool for administration, management, and internal support of the entire Axia platform operation. Through it, the operator interacts with end users, configures modules, tracks indicators, and ensures process compliance.

The Super Administrator has access to a complete dashboard with financial, operational, and growth indicators. From it, it is possible to manage users, grant granular permissions by segment, and exercise administrative control over accounting, finance, payments, NFTs, crowdfunding, stores, and products.

BackOffice Capabilities

  • Data processing — Manages internal records of users, employees, accounting, and inventory.
  • Operational support — Sustains the company's core processes, ensuring efficiency and traceability of operations.
  • User and permission management — Creates access profiles, approves registrations, and controls the authorization levels of each operator.
  • Financial management — Centralizes accounting, corporate finance, withdrawal management, charges, and platform revenues.
  • Information Technology — Maintains the IT infrastructure, including network, servers, cybersecurity, and internal technical support.
  • Logistics and supply chain — Manages internal logistics, inventory, and coordination with suppliers.

Manual Sections

SectionDescription
DashboardIndicators and operational overview
UsersRegistration, approval, permissions and KYC
FinancialPayments, withdrawals, charges, distribution and reports
AccountingAccounting entries and reconciliation
CreditLoan requests and credit management
AuditAudit logs and action traceability
StoresStore and product management
ContractsDigital contracts and documents
ERC-3643Regulated asset tokenization
Anti-Fraud ModuleFraud prevention rules and alerts
Bulk ActionBatch operations on users or records
ProductPlatform product configuration
ProceduresSupport, updates, and new feature requests

Access Profiles

The BackOffice uses a two-level permission model:

  1. Static permission — defined in the backend via the @AuthenticationRequired decorator, controls which endpoints each role can access.
  2. Dynamic permission — registered in the database and verified on the frontend via *ngIf, shows or hides modules and actions according to the operator's profile.

Both levels must be configured for an administrative feature to appear correctly for a specific profile.

For questions or operational issues, visit the Support and Procedures section.