Pick the path that matches your work. Each path names its goal, the three pages to read next, and the Console role it needs in your DALP Instance. Most roles are granted to your wallet, the account that signs for you on the network, and a Permission manager grants them on Roles and permissions. Two are account roles: an Owner of the organisation manages its members and settings, and a Platform admin runs the whole deployment. Role names here match the labels the Console shows.
Run assets day to day
Goal: issue assets, manage their supply and service them through their asset lifecycle.
Console role: Asset manager to issue. The wallet that issues an asset receives Permission manager, Governance, Supply management and Emergency on that asset. Supply management mints and burns, and Emergency pauses the token.
Onboard and verify investors
Goal: register participants, verify them and decide which rules an asset enforces on every transfer.
Console role: Identity manager to register identities, Verification issuer to attach verifications, and Compliance manager to configure compliance modules and global controls.
Administer the organisation
Goal: invite people, grant roles, connect custody and require maker-checker approval for sensitive changes.
Console role: Owner to invite members and change settings, and Permission manager to grant and revoke on-chain roles.
Connect your own software
Goal: call the Platform API from your own software, and receive events without polling.
Console role: none of its own. You create an API key on API keys, and the key acts with the roles of the person who created it, within the read or read-write scope you set for the key. Transaction lifecycle explains how the platform runs each request that changes state on the network.
Deploy and run the instance
Goal: install DALP in your cluster, connect its networks and keep it running through upgrades.
Console role: Platform admin for the network catalogue and the Platform admin screens. With local sign-in, the first account created on a fresh instance takes that role, and every later sign-up is a member. Create the first account before the Console is reachable from outside your network. With an identity provider, a claim from the provider decides who is a Platform admin.
Review the platform
Goal: assess how DALP is built, which controls a request passes, and who can reach the instance.
No Console login is needed to read these pages. To review a running instance, ask for the Auditor role, which gives view-only access to permissions, identities, audit logs and system state. The audit trail records state changes and sensitive reads.