Supplier isolation
Account-scoped controls separate one supplier’s data from another’s.
COMPANY / SECURITYPrivate relationships.
Private relationships.
Scoped access.
Understand how SupplyDesk describes account access, data handling, and integration permissions.
Access boundariesExampleDETAILYOUR WORKSPACE
SupplierOwn account data
BuyerAssigned products & prices
OrdersBuyer-specific access
QuickBooksOptional integration
How access is organized.
Buyer boundaries
Buyers are scoped to their assigned catalog, prices, and order history, including within the same supplier account.
Integration scope
QuickBooks access supports the enabled integration workflow. Connection credentials are encrypted at rest.
Infrastructure and billing.
SupplyDesk uses managed cloud infrastructure, encryption in transit and at rest, and backups. Payment processing is handled through Stripe; SupplyDesk states that it does not store card numbers.
The overview does not claim a SupplyDesk SOC 2 or ISO certification. If your procurement process requires an assurance document, retention schedule, recovery objective, or contract commitment, request it directly before adoption.
Questions worth resolving before rollout.
- Who should have supplier access and who should have buyer access?
- Which catalog and pricing records should each buyer see?
- Which integration permissions are needed for your intended workflow?
- What security documentation does your procurement process require?
- Who should your team contact about a suspected access or sync issue?
Security questions or an incident?
Contact hello@supplydesk.ca with the affected account and a description of the issue. Do not include passwords or other secrets in your message.
Contact the team for current technical documentation and contractual details.