Roles and permissions

Role permissions, API key scopes and customer ownership rules.

Access combines a session (cookie or of_ bearer API key) with role permissions defined in features/keystone/models/fields.ts.

Collectibles permissions

PermissionAllows
canReadCollectiblesRead collectible records
canManageCatalogimportCardCatalog, refreshMarketPrices
canManageProductsrepriceInventory, products
canManageListingsListings
canManageAuctionsAuction desk
canManageConsignmentsConsignment records
canManageEvidenceCondition, grade, provenance, custody evidence
canManageCollectibleCustomersCollector records
canManageRiskRisk records
canManageIntegrationsProvider connections

The shared product, inventory, order, payment, fulfillment, return, discount, gift card, user, role and webhook permissions also apply.

API keys

Effective access is the intersection of the key's scopes and its owner's role. Keys can have expiry and IP restrictions.

Customer ownership

Binders, want-list items and saved searches are created against the signed-in user and filtered to that user on read, update and delete.

Locked lists

Inventory units, movements, reservations and listings refuse generic GraphQL create and update. They change through commands.

On this page