Saleor app tokens and staff permissions meet in the dashboard
Saleor's API supports staff users, apps, tokens, and OIDC. The authentication documentation explains that app tokens and staff users can reach the API when storefront traffic is disabled, and that a dashboard app receives a JWT whose permissions are the intersection of the user's permissions and the app's permissions. The permissions page describes data permissions such as orders and products, permission groups, and the need to refresh a JWT after a user's permissions change.
A Saleor Dashboard reachable from the internet may be an expected part of a commerce deployment. The review should focus on the staff identity model and the applications that hold tokens. The dashboard can be the place where a person manages products, orders, and apps. It can also be the place where an app receives a token that acts on the API.
The storefront traffic setting adds another layer. If storefront traffic is turned off, only apps and staff users can reach the API. That can reduce public API exposure, but it does not secure the dashboard or the app tokens. A token should be reviewed by installation, permission set, owner, and revocation history.
Query plan
Use app="Saleor" and title="Saleor Dashboard" with sub_type=all, page 1, and page size 1. Saleor can be embedded in custom domains and white-label front ends, so a title match may miss a deployment while the application field may capture a different product component. Do not sum the counts or assume that every match is a staff-facing dashboard.
The live measurement was unavailable in this run because the authorized ZoomEye execution was rejected by the platform. The query remains useful for a later approved collection. Preserve the exact scope and report an error when a candidate query fails.
Review users, groups, and apps
List staff users and permission groups. Confirm that every user has a current role and that departed staff lose access to the dashboard and API. Check whether permission changes require a new JWT and whether the old token remains valid until it expires. A token's embedded permission list can be stale even when the user's group has changed.
Review app installation records and tokens. The Saleor documentation says an app token is the credential used to access the API and that deactivating an app disables all auth tokens generated for it. Test that behavior. Also check the app manifest, requested permissions, webhook subscriptions, and the person who approved the installation.
OIDC adds a useful central identity path, but the app still needs a permission model. Confirm that the OIDC scope and the Saleor permissions map to the intended roles. Test a user who is authenticated by the provider but has no staff permission. The app should not convert a successful login into an administrative role.
Secure the storefront boundary
Separate the public storefront from the staff dashboard where the deployment allows it. Put the dashboard behind a network or identity-aware access layer and keep its cookies scoped to the admin origin. Review CORS, CSRF protections, and the handling of app bridge tokens. Do not place a staff token in a static storefront bundle.
Monitor app installation, app token creation, permission-group changes, and OIDC configuration changes. A new app can request broad permissions without changing a single staff account. Keep a record of the app publisher, manifest URL, and review decision.
Investigate a match
Confirm ownership through DNS, certificate, and cloud records. A live Saleor storefront is not evidence of an exposed dashboard. Check the actual route and response only through an authorized business request. If an administrative route is reachable, review recent staff and app activity before removing access.
Saleor's intersection model is a strong building block when both sides are maintained. The staff group and the app manifest must each remain narrow. Inventory the deployment, then review the two permission sets that meet at the dashboard.