Back-end users (Operators)

A back-end user is a platform operator. They manage the platform configuration, integration flows, and system operations.

Key Characteristics

• These users are created exclusively by the operator via the back office.
• There are multiple permission levels, defining access and actions within the admin interface:
  • Admin
  • User
  • Reader

Store Assignment

Operator users can be assigned to one or more stores. This enables store-level segmentation in the Back Office: an operator assigned only to stores France and Belgium will not see stores Germany or Spain in their interface.

Key rules:

• Explicit assignment only — there is no implicit "all stores" mode. Each store must be explicitly assigned.
• No automatic inheritance — when a new store is created, it is not automatically accessible to existing operator users. Access must be explicitly added.
• Default on creation — newly created operator users have no store assignment by default. Stores must be assigned separately.
• Identification — stores are referenced by their externalId.

⚠️

Store assignment controls visibility in the Back Office only. It does not prevent API calls with a non-assigned store header.

Searching, Filtering and Sorting Operator Users

The operator users list endpoint ADM-OPERATOR-USER-550 supports advanced search, filtering and sorting capabilities.

Full-text search — the search parameter searches across email, firstName and lastName fields.

Available filters:

All multi-value filters use OR logic. Unknown filter parameters are silently ignored.

Sorting — use the sort parameter with the format field:direction (e.g. lastName:asc). Sortable fields: id, externalId, email, civility, firstName, lastName, fullName, locale, status, createdAt, updatedAt. Malformed sort entries are silently ignored.

✅

Tip: Combine storeIds and groups filters to quickly find all operators with a specific permission level on a given store.