Palladium AI uses a three-tier role model to control what each user can see and do within the platform. Roles are assigned per team for member and admin, while platform_owner is a global designation that spans all teams and unlocks platform-level configuration. Understanding the boundaries between roles helps you keep financial data secure and delegate responsibilities appropriately.
Permissions Table
| Action | member | admin | platform_owner |
|---|
| View team dashboard | ✓ | ✓ | ✓ |
| Record savings deposits | ✓ | ✓ | ✓ |
| Apply for a loan | ✓ | ✓ | ✓ |
| View all team loans & deposits | ✓ | ✓ | ✓ |
| Approve or reject loans | — | ✓ | ✓ |
| Invite members to a team | — | ✓ | ✓ |
| Change member roles | — | ✓ | ✓ |
| View Geographies analytics | ✓ | ✓ | ✓ |
| Add member location pins | — | ✓ | ✓ |
| Access admin API console | — | — | ✓ |
| Publish/edit API products | — | — | ✓ |
| View all teams’ data | — | — | ✓ |
Assigning Roles
Admins can update any team member’s role directly from the Members page. Find the member’s row, open the role dropdown, and select the new role — the change takes effect immediately. You can promote a member to admin or demote an admin back to member at any time without disrupting their access to existing records.
The platform_owner role is different: it is a global role set by the platform operator, not by individual team admins. If you need platform_owner access granted or revoked, contact your platform operator to make that change.
The platform_owner role grants access across all teams and the admin API console. Assign it only to trusted operators.
