Repository navigation
Point service account access errors at organization settings instead of a fixed admin path - #8978
Merged
Merged
Conversation
github-actions
Bot
added
the
no-changelog
…ixed admin path The errors for a service account token that lacks access named the admin page as "Settings > Users > Security". Service accounts have since moved to Organization settings > Security, and the page can move again. The errors now say "in your organization's settings in the Shopify admin", which stays true across admin layout changes. Both the Organizations API refusal in @Shopify/organizations and the token exchange refusal in cli-kit are updated. No changeset: both messages are unreleased and already covered by pending changesets.
alexanderMontague
force-pushed
the
eddie/store-commands-token-401
branch
from
October 29, 2026 18:58
c13c562 to
e8dc74b
Compare
alexanderMontague
changed the title
alexanderMontague
approved these changes
Oct 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related to shop/issues-develop#24293
TL;DR: The errors shown when a service account token lacks access now point at "your organization's settings in the Shopify admin" instead of the fixed path
Settings > Users > Security.WHY are these changes introduced?
This PR originally added the "This token can't manage dev stores." error for
store create dev,store listandstore delete. #8999 landed a fuller version of that fix onmain(OrganizationStoreAccessError/organizationStoresRequestDoc), so that part is dropped here.What's left is the wording. Both #8999 and the token exchange error from #9000 tell the user to go to
Settings > Users > Securityin the Shopify admin. Service accounts now live under Organization settings > Security, and the page can move again. A hardcoded path goes stale; "your organization's settings" stays correct.WHAT is this pull request doing?
OrganizationStoreAccessErrorin@shopify/organizations(shown when the Organizations API refuses a token forstore list,store create devandstore delete) now says:AutomationTokenExchangeErrorin cli-kit (shown when Identity refuses the token exchange because the service account lacks a capability, or the token was revoked or expired) uses the same location wording.automation-token-exchange-errorsand store-command changesets.How to manually test your changes?
With a service account token that doesn't have Dev store management:
The next step reads "Give the service account Dev store management access in your organization's settings in the Shopify admin." and no longer names
Settings > Users > Security.Checklist
patchfor bug fixes ·minorfor new features ·majorfor breaking changes) and added a changeset withpnpm changeset add