Permissions

How the platform decides what an account can see and do.

Role-Level Permissions

Every account’s permissions start with its role — Buyer, Seller, or Trade Agent. Role determines the broad category of actions available: buyers can place orders, sellers can manage listings, agents can act on tasks. This is the same layer that drives Role-Based Navigation.

Trade-Level Scoping

Within a role, access is further scoped to the specific trades you’re party to. A buyer can only see their own orders, not another buyer’s. A trade agent can only act on trades they’ve been assigned to, not every trade in the system.

Permissions are enforced, not just hidden
Scoping is enforced at the data layer. Even if a URL for another organization’s trade were guessed directly, the platform would not return that data to an account without permission.

Organization Administrators

Some accounts hold additional administrative permissions within their organization — for example, managing which trade agents are available for assignment, or reviewing organization-wide reporting. These permissions are granted by an existing administrator, not self-service.

Common Mistakes

  • Assuming a missing action button is a bug rather than a permissions boundary — check your role first.
  • Sharing login credentials to work around a permissions gap instead of requesting the correct access.

If you believe you’re missing a permission you should have, contact your organization administrator or support.