Platform Admin vs. Org Admin: Why the Distinction Matters

"Admin" is an overloaded word in a multi-tenant platform. The platform has admins. Each tenant org has admins. They share the word but not the powers. ReVend keeps that distinction visible in navigation.

Platform-only pages

/admin, /admin/organizations, /admin/users, /admin/platform/trust-scoring, /admin/escrow/disputes, /admin/auction/strikes/[companyId] and /admin/exchange-rates are platform administration surfaces. They are gated by platform scope; an org-admin cannot reach them no matter how their tenant role is configured.

Tenant Settings pages

Tenant admins manage their own organization from Settings: /settings/organization-profile for tenant identity and /settings/users for team members, invites, roles and user detail. Old tenant-facing Admin links redirect to those Settings pages instead of exposing Admin as a tenant concept.

Cross-tenant visibility

Platform staff can read across tenants for support reasons — a customer files a ticket about a deal that bounced, the platform staff needs to see the deal to investigate. The visibility is logged: every cross-tenant read writes an entry to the activity log with the staff user, the target tenant, and the action.

Why the split matters

Because putting tenant work and platform work under the same Admin label makes access-control mistakes easier. Settings is where a tenant manages itself. Admin is where ReVend operates the platform. Naming makes the audit easier.