Users and organizations

From account creation to team structure, access control, and API credential management

A user account gives access to Commerce Layer. Each user can belong to one or more independent organizations. Within each org, you invite members, assign roles and permissions, and configure the API applications your team needs.

Users

Users are individuals who create an account in Commerce Layer. A user can create or join one or more organizations. Within each organization, they can manage memberships and assign or receive specific roles and permissions. To become a user, you need to sign up using an email address or one of the other available options.

Organizations

An organization is an independent group that comprises members with assigned roles and permissions. A user can manage many companies, clients, or merchants within a single account by using one or more organizations. With the appropriate permissions, members can create new merchants, markets, and business models for each market without any data duplication.

Members, roles, and permissions

Each organization is completely independent. You can invite one or more users to join an organization and assign them a role — either Admin or Member. New members receive an invitation by email and will be prompted to create an account if they don't already have one.

Enterprise users can define custom roles and assign permissions to each role, allowing different members to have different privileges across the organization.

Applications

Each organization has its own set of applications, which define the API credentials your team uses to build on Commerce Layer. Three types of applications are available, each with a role that grants different permissions:

• Sales channel — non-confidential (public) API credentials for building any customer-facing touchpoint. Their permissions are restricted so that they can be safely used client-side without exposing sensitive data.

• Integration — confidential API credentials for backend integrations with third-party systems. They can have one of two roles: Read-only or Admin.

• Webapp — used to build custom web apps or services that extend Commerce Layer with functionality not available out of the box. They don't have predefined roles and permissions: they inherit the permissions of the authenticated user.