Multi-Tenant Architecture & Role-Based Permissions

Understand how Ordrly isolates business data and enforces structured role-based permissions across retailers, brands, and staff users.

Published Feb 22, 2026 2 views

Multi-Tenant Architecture & Role-Based Permissions

Overview

Ordrly is built on a multi-tenant architecture that isolates data by business while enabling structured collaboration between retailers and brands.

Role-based permissions ensure that users can access only the data and workflows appropriate to their assigned responsibilities.


1. Multi-Tenant Business Model

Each retailer and brand operates within its own business scope.

  • Orders are scoped to a specific business.
  • Invoices are tied to a specific retailer account.
  • Returns and reimbursements are linked to originating businesses.
  • Credit limits and Net Terms are retailer-specific.

Data from one business is not accessible to another unless explicitly connected through marketplace relationships.


2. Staff & User Roles

Each business may have multiple staff members assigned different roles.

Permissions may include:

  • Order management
  • Credit configuration
  • Invoice review
  • Return approvals
  • Reporting access
  • Administrative configuration

3. Business-Level Scoping

System queries and workflows are scoped to the active business context, ensuring financial and operational isolation between tenants.


4. Audit & Accountability

User actions such as credit adjustments, return approvals, and order updates are logged for traceability and accountability.


Why This Matters

Multi-tenant isolation and structured permissions are essential for enterprise-grade wholesale operations, protecting sensitive financial and operational data.

Was this article helpful?