twimco.Let’s talk ↗︎
Menu
Field notes / Buying software

Shopify's Apps page now shows token expiry and IP rules. Walk it before November 20

Shopify now surfaces each app's latest activity, sensitive permissions, expiring access tokens, and enforced IP restrictions under Settings > Apps as of November 5, 2026. The IP allowlist deadline for public apps is already on the calendar.

Editorial engraving of a bright window seat where a store ops manager checks her phone and ticks a paper checklist during a tablet call with an IT partner.

Shopify's November 5, 2026 admin update puts app activity, permissions (with sensitive-data labels), expiring access tokens, and enforced IP restrictions on the Apps index and detail pages. Use it as a buying and renewal checklist: apps without expiring tokens or IP enforcement need a vendor question before November 20, when public-app IP allowlisting is due, and before the November 12 bulk-operations gate tied to that work.

What Shopify put on the Apps page

On November 5, 2026 Shopify's changelog announced that merchants can review more information about connected apps from Settings > Apps. The apps index shows each app's latest activity and highlights security issues that may need attention. On an app's details page, access, permissions, and activity sit together, with labels for permissions that may include sensitive data.

You can also see whether the app has adopted required security measures Shopify calls out by name:

  • Expiring access tokens — credentials that expire and must renew, shortening how long a stolen token remains useful.
  • Enforced IP restrictions — Shopify API requests limited to approved IP addresses.

Security posture is finally visible next to the app name. Treat a blank as a no.

How the work moves

Thirty minutes on Settings > Apps

  1. Scan the index

    Note apps with security highlights and surprising latest activity.

  2. Open high-risk apps

    Read permissions labeled as possibly including sensitive data.

  3. Check token posture

    Mark whether expiring access tokens are adopted.

  4. Check IP posture

    Mark whether enforced IP restrictions are on—especially public apps before Nov 20.

  5. Write vendor asks

    Send one question list per weak app; schedule uninstalls for the ones you cannot trust.

Illustrative workflow, not a client screenshot or measured result.

Why this lands next to the IP allowlist deadline

Public Shopify apps are already under an IP allowlist clock: merchants and partners have been working toward November 20, 2026, with bulk-operations consequences called out around November 12. The new admin surface does not invent that deadline. It makes the related posture visible while you still have time to ask vendors a straight question: will this app enforce IP restrictions and expire tokens, or are we renewing a soft target?

If you already read the Field Note on the public-app IP allowlist, use this admin walk as the companion checklist for every installed app—not only the ones Shopify labels public.

Security posture is finally visible next to the app name. Treat a blank as a no.

How to buy (and renew) with the new page open

Start with money and customer data. Apps that can read orders, customers, or checkout-adjacent scopes go first. Sensitive-data labels are a hint, not a full data map.

Ask vendors about blanks. If expiring tokens or IP enforcement show as missing, send a dated question. "We'll get there" without a date is a renewal risk.

Match activity to the job. Latest activity that looks like constant write traffic on a "reporting only" app deserves a call.

Uninstall on purpose. Orphaned apps with broad scopes are still authenticated. The new page makes neglect visible; it does not uninstall for you.

Decision guide

What the new page shows vs what you still decide

ConsiderationNow visible in adminStill a human decision
Latest activity per appLatest activity per appWhether that activity matches the job you bought
Sensitive permission labelsSensitive permission labelsWhether those scopes are still justified
Expiring access tokensExpiring access tokens adopted or notWhether to renew an app that never expires tokens
Enforced IP restrictionsEnforced IP restrictions adopted or notWhether the vendor will meet the public-app allowlist deadline
Decision framework: assess these conditions against your own app stack.

What the page will not do for you

It will not rewrite your vendor contract. It will not prove the IP list is correct—only that enforcement exists. It will not replace a penetration test. And it will not decide whether a custom app you commissioned should become public or stay custom; that choice still belongs to how you buy software for the storefront.

Use the page as a monthly hygiene ritual during peak, then quarterly after. Security theater is reviewing once and screenshotting for a ticket. Hygiene is a named owner and a recurring calendar block.

Renewal season with evidence. When an app invoice arrives, open its detail page beside the invoice. If expiring tokens and IP enforcement are missing, the renewal email becomes a negotiation: adopt both, or we uninstall. Vendors who already meet the public-app allowlist work will have something to show; vendors who shrug are telling you their incident response plan.

Custom apps you built in-house belong on the same walk. Trusting yourselves is not a posture. Check whether those apps expire tokens and restrict IPs. Insider risk and laptop theft do not care that the app was custom.

Share the spreadsheet with finance and CX, not only IT. An app with sensitive customer permissions and no activity for ninety days is a CX and privacy issue as much as an engineering one. Uninstalls should be scheduled like any other change that might break a workflow—with a named rollback if a quiet app turns out to be load-bearing.

Make the walk a monthly ritual. Thirty minutes monthly during peak, then quarterly after, beats a heroic annual cleanup. Put Settings > Apps on the same hygiene calendar as staff permission reviews. The new activity and security highlights only help if someone looks.

When Shopify highlights an issue, treat it like a Sev-3 until triaged—not like a badge to screenshot for a compliance folder. Either the vendor fixes posture, you accept a dated risk, or you uninstall. Three outcomes, one owner, one due date.

If your public apps are mid-allowlist work for November 20, use this page as the merchant-side mirror of the partner checklist. Partners who cannot show IP enforcement here will struggle to meet the deadline that already has a Field Note on the journal.

Export or screenshot the Apps index highlights for the change ticket that tracks November 12 and November 20 work. Auditors and future you will want proof you looked. The page is the evidence surface; your ticket is the decision surface.

Put this into practice

Block thirty minutes this week: Settings > Apps, a spreadsheet with columns for sensitive scopes, expiring tokens, IP enforcement, and vendor response date. Escalate anything blank before November 12 if the app participates in bulk operations, and before November 20 if it is a public app on the allowlist path.

If you want a partner to turn that review into an operating habit, write TWIMCO.

Partners who build custom apps for you should receive the same questionnaire you send public-app vendors: expiring tokens, IP enforcement, sensitive scopes used, and last activity explanation. Custom is not a synonym for reviewed. Put their answers in the same spreadsheet so renewals and uninstalls use one standard.

If an app shows sensitive permissions but the business owner left the company, freeze the app until a new owner claims it. Orphaned scopes are how quiet incidents start.

Teach store admins that installing an app is now a security decision visible on the Apps page, not only a feature decision. A five-minute install can create a six-month exposure if tokens never expire. Put that sentence in the internal app-request form.

After the walk, send three vendor emails the same day while context is fresh. Delayed questions become forgotten risks.

Close every blank IP or token row with either a vendor commit date or an uninstall date. Open rows are how November 20 arrives as a surprise.

A blank security row is a decision waiting to happen—make it this week.

Do the walk with two people so disagreements about risk get resolved in the room.

Then file the sheet.

Related work: Sutton\|Place

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎