4. Merchant user roles in the Portal
Administrator and Developer are roles held by users of a business registered with DLT. They describe what that user can do inside DLT Merchant Portal. Developer here is a merchant team role, not the DLT development team maintaining the Portal. DLT back-office platform roles cannot use this Portal user contract.
| Capability | Administrator | Developer |
|---|---|---|
| Read/update own profile, verify own email, change own password | Yes | Yes |
| View merchant profile, logo, and enabled services | Yes | Yes |
| Update editable merchant profile and logo | Yes | No |
| View merchant integration credential metadata in the Portal | Yes | Yes |
| Manage and retrieve newly issued merchant integration credentials in the Portal | Yes | No |
| Replace/remove merchant integration keys in the Portal | Yes | No |
| View team member directory | Yes | Yes |
| List/manage invitations, change roles, remove members | Yes | No |
| Read test/live transactions, sanitized merchant history, and metrics | Yes | Yes |
| Reveal additional sensitive evidence | Outside initial portal contract | Outside initial portal contract |
| Initiate or mutate collection transactions | No | No |
Login returns numeric user.role: 1 for Administrator, 10 for Developer. Profile/member resources return administrator or developer. Fetch GET /portal/me after login for the canonical role.