Skip to content

GrowthDept Commerce is in build. Brands Growth Dept already runs get it first. Each feature on these pages is marked in testing, in build or planned.

Security and permissions

Every request is checked. Every sensitive action is recorded.

Commerce decides what each person may see and do on the server, for every page, every API call and every background job. Hiding a button is never the only lock.

ActionOwnerSupportFulfillment
View ordersYesYesYes
Refund an orderYes, with a second stepYes, with a second stepNo
Export customersYes, with a second stepNoNo
Invite staff and change rolesYes, with a second stepNoNo
Helpdesk ticketsYesYesNo
Example. Each store sets its own roles; these three are illustrations.

People and roles

Roles that match Shopify's, and go further

Roles and permissions

In testing
  • Ready-made roles that mirror Shopify's staff roles, plus custom roles and groups of roles.
  • Several roles per person, given for one store or for the whole organization.
  • Each permission names a thing and an action: view, create, edit, delete, approve, publish, export or manage.
  • Everything is refused unless a role allows it, and nobody can give out a permission they don't hold themselves.

A permission set for each app

In testing

Attribution, email and SMS, A/B testing, reviews, support and AI employees each have their own permissions, so access to one app says nothing about another.

Sign-in

In testing
  • Password, Google, passkeys, or your organization's single sign-on.
  • Two-step sign-in with an authenticator app and recovery codes.
  • Required for owners and admins, and for anyone who can move money, manage staff, export data or change settings. Refunds, captures and dispute responses ask for it again.

Growth Dept staff are kept apart

In testing

Our staff sign in to a separate console. Reaching a merchant's store takes emergency access that is time-limited, needs a stated reason, and is recorded each time it is used.

Data

Each store's data stays its own

Stores kept apart in the database

In testing

The database itself separates one store's rows from another's, so a request for one store can't return another store's data even if the application code has a bug. A test fails the build if any store table lacks that protection, and others try to read across stores and must be refused. Files, caches, job queues and search are kept apart by store as well.

Customer details kept separate

In testing

Names, email addresses, phone numbers and addresses sit in their own tables, encrypted field by field, so reports and analytics work without them.

A record of sensitive actions

In testing

Role changes, payments, sign-ins and other security events are written to an audit log. Entries can be added, never changed or deleted.

Deleting a customer's data

In build

When a deletion request arrives, one path removes that customer's personal details from Commerce, including its copy of the Shopify data.

The technical details

For your engineers

  • Postgres row-level security keyed on the store, on every store table; a schema test fails the build if one is missing it.
  • Customer contact fields encrypted with AES-256-GCM, bound to the row they belong to.
  • HTTPS only, __Host- cookies, and a nonce-based Content Security Policy on signed-in pages.
  • Signatures checked on incoming webhooks from Shopify and Stripe, and rate limits on sign-in and sign-up.
  • Dependency, secret and code scanning on every change In build, and an independent penetration test before live payments Planned.

Bring your team, with the roles they need.

Set up roles once in Commerce and they apply in every Growth Dept app.