Reference
Custom App Authentication and Scopes examines installation, sessions, tokens, least privilege, rotation, and revocation as a store-specific workflow. Credential lifecycle is part of the product boundary. Define the user decision, Shopify surface, app-owned state, failure model, and maintenance. The decision is What is the smallest access model for each actor and process?
Red flags
The primary risk is requesting broad permanent access for convenience.
Findings
This guidance applies directly to installation, sessions, tokens, least privilege, rotation, and revocation.
For custom app authentication and scopes, keep the interface centered on the staff or customer decision. Embedded admin screens should preserve Shopify context, make permission and loading states clear, and avoid turning an operational task into a generic dashboard.
Use Functions for supported deterministic commerce logic, Flow for visible automation, APIs for Shopify resources, and app infrastructure for stateful external work. Separate client identity, delegated authorization, token storage, rotation, revocation, and denied access.
Verify webhooks, deduplicate, queue long work, use safe retries, retain attempt history, and reconcile state. A valid token can still be over-scoped, expired, revoked, or used for the wrong tenant. An app must explain what an operator does when automatic recovery stops.
Budget hosting, monitoring, support, incidents, security, API version changes, dependency upgrades, and feature evolution. Exercise install, refresh or reauthorization, revocation, and offboarding paths.
Investigation
The sequence follows the actual operating model for this subject.
Compare native Shopify capability, configuration, existing apps, and process changes against installation, sessions, tokens, least privilege, rotation, and revocation. Record why the remaining gap deserves custom ownership.
Map actors, permissions, decisions, exceptions, loading, errors, confirmation, and reversal. The central decision is What is the smallest access model for each actor and process?
Place deterministic commerce logic, admin UX, storefront behavior, automation, and stateful services in their supported Shopify boundaries. Separate client identity, delegated authorization, token storage, rotation, revocation, and denied access.
Test installation, scope denial, duplicate events, jobs, dependency outages, migrations, rollout, rollback, and offboarding. The route risk is requesting broad permanent access for convenience. A valid token can still be over-scoped, expired, revoked, or used for the wrong tenant.
Ship observability, runbooks, support boundaries, API-version review, dependency updates, backups, and succession guidance. Exercise install, refresh or reauthorization, revocation, and offboarding paths.
Case frame
What is the smallest access model for each actor and process? The lenses below are specific to installation, sessions, tokens, least privilege, rotation, and revocation.
Describe the staff or customer workflow behind custom app authentication and scopes, its frequency, current failure cost, exceptions, and decision owner. A feature list does not prove custom software is the right answer.
Choose where installation, sessions, tokens, least privilege, rotation, and revocation belongs: embedded admin, Admin API, Storefront API, webhook processing, Flow, Function, app proxy, theme extension, or app infrastructure. Separate client identity, delegated authorization, token storage, rotation, revocation, and denied access.
Name what the app must store, what remains authoritative in Shopify, retention and deletion behavior, and how schema changes migrate. Avoid copying platform data without a product reason.
Assign hosting, deployments, incidents, security, API upgrades, documentation, support, and roadmap decisions. Exercise install, refresh or reauthorization, revocation, and offboarding paths.
Exhibits
| Layer | What to preserve | When |
|---|---|---|
| Gap record | Native, configured, existing-app, and process alternatives compared against the exact workflow. | Discovery |
| Product fixture | Realistic store, actor, data, permission, exception, and acceptance scenarios for installation, sessions, tokens, least privilege, rotation, and revocation. | Design |
| Lifecycle proof | Install, denied access, duplicate, timeout, migration, rollout, rollback, and recovery evidence. A valid token can still be over-scoped, expired, revoked, or used for the wrong tenant. | Pre-release |
| Ownership file | Named operational owner, dashboards, runbook, API-version schedule, support path, and cost boundary. Exercise install, refresh or reauthorization, revocation, and offboarding paths. | Handoff |
Disposition
Interview notes
It is justified when installation, sessions, tokens, least privilege, rotation, and revocation represents a valuable, store-specific workflow that native features, configuration, established apps, or a process change cannot meet reliably—and when someone will own the resulting product. Credential lifecycle is part of the product boundary.
Depending on the workflow, an app can use Admin or Storefront APIs, embedded admin UI, webhooks, Flow extensions, Functions, theme extensions, app proxies, checkout or customer-account extensions, and app-hosted services. Choose by execution, trust, and state requirements.
Discovery, hosting, queues, observability, backups, security, support, API upgrades, dependency maintenance, data migration, rollout, rollback, and succession are often omitted. They are part of owning the product.
Use realistic store fixtures, denied permissions, duplicate and delayed events, dependency outages, migration tests, monitoring, rollback, and operator recovery. Exercise install, refresh or reauthorization, revocation, and offboarding paths.
Devuchi
Devuchi is a subscription Shopify development service for ecommerce brands and agencies that need reliable recurring development capacity.
installation, sessions, tokens, least privilege, rotation, and revocation can be planned against the frameworks and checks in this reference.