Custom Apps From the Admin Now Live in the Dev Dashboard – What You Need to Know

Legacy custom apps created in the Shopify admin are now visible in the Dev Dashboard, giving merchants and developers richer security controls, IP restrictions, and activity logs. Learn what changed, who’s impacted, and how to migrate your apps today.

Custom Apps From the Admin Now Live in the Dev Dashboard – What You Need to Know
6 sections

Shopify just rolled out a game‑changing update: custom apps that were originally built directly in the Shopify admin are now listed in the Developer Dashboard. This move bridges the gap between merchant‑created apps and the robust tooling developers have been using for years, adding IP‑based access controls, detailed request logs, and webhook monitoring. In this post we’ll break down exactly what changed, who it affects, and the concrete steps you should take to keep your integrations secure and running smoothly.

What’s Changed?

Until now, legacy custom apps built from the Shopify admin lived in a separate “admin‑only” silo. They could generate API credentials but offered limited visibility into how those credentials were used. The new update migrates those apps into the Dev Dashboard, the same interface where public and private apps are managed. Once there, you gain access to three core features: IP address restriction, API request logs, and webhook activity logs. In short, you get the same security toolbox that Shopify’s own app partners have enjoyed.

Who Is Affected?

Both merchants and developers feel the impact. Merchants who previously created “custom apps” for bespoke integrations now see those apps under Settings → Apps → Develop apps → Your apps. Developers who manage stores for clients will notice the same apps appear alongside their own private apps, making it easier to audit permissions and usage. If you’ve ever used a custom app to push orders to an ERP, sync inventory, or generate custom discounts, you’ll now have a single pane of glass for monitoring and securing that traffic.

Key New Controls in the Dev Dashboard

  • Restrict Access by IP Address – You can whitelist specific IP ranges so that only servers you trust can use the app’s API key. This is especially valuable for on‑premise integrations that run from a static data center.
  • Monitor API Activity – The request log shows each API call made with the app’s credentials, including endpoint, response status, and timestamps. You can filter by method (GET/POST) or by specific resources (orders, products, etc.).
  • Webhook Activity Log – Every webhook payload received by the app is recorded, making it trivial to trace unexpected spikes or failures.
  • These tools turn a “black box” custom app into a transparent, auditable component of your tech stack.

    Steps to Transition Your Legacy Custom Apps

    Step 1 – Verify the App Appears in the Dev Dashboard

    Log in to your Shopify admin, go to Settings → Apps → Develop apps, and confirm the legacy custom app is listed. If it isn’t, click “Refresh” or reach out to Shopify Support.

    Step 2 – Review Existing Permissions

    Open the app details and check the OAuth scopes it requests. Update any overly broad scopes (e.g., read_all_orders) to the minimal set required for your integration.

    Step 3 – Enable IP Whitelisting

    Navigate to the “IP Restrictions” section, add your server’s public IP or CIDR block, and save. Example:

    Allowed IPs:

  • 203.0.113.45/32
  • 198.51.100.0/24
  • Step 4 – Enable Activity Logging

    Toggle the “Log API requests” and “Log webhook deliveries” switches. Logs are retained for 30 days by default; you can export them as CSV for longer retention.

    Step 5 – Test the Integration

    Run a few API calls from your server and verify they appear in the logs. If you see “403 Forbidden” errors, double‑check the IP list and OAuth scopes.

    Step 6 – Communicate with Stakeholders

    Inform your internal teams or agency partners that the app now lives in the Dev Dashboard and that future changes (e.g., rotating API keys) should be performed there.

    Best Practices & Sample Configurations

  • Rotate API credentials regularly – The Dev Dashboard lets you generate a new API key without downtime. Update your server environment variables and test before deactivating the old key.
  • Use environment‑specific IP lists – For staging environments, create a separate IP whitelist so you can safely test changes without affecting production.
  • Leverage webhook retries – The dashboard shows retry counts; if you notice many retries, investigate your endpoint’s response time or SSL configuration.
  • Audit logs weekly – Set a calendar reminder to review the API and webhook logs. Look for spikes in “unauthorized” responses or unexpected endpoints.
  • Document the migration – Keep a simple markdown file in your repo that records the app ID, current scopes, and IP whitelist. Example snippet:
  • # Custom App Migration Log

  • App ID: 1234567890
  • Scopes: read_orders, write_products
  • Whitelisted IPs: 203.0.113.45/32, 198.51.100.0/24
  • Last credential rotation: 2024‑10‑01
  • Following these habits will keep your custom integration secure, compliant, and easier to troubleshoot.

    Conclusion

    Shopify’s decision to surface admin‑created custom apps in the Dev Dashboard is more than a UI tweak—it’s a security upgrade that gives merchants and developers the same visibility and control they expect from native apps. By reviewing permissions, enabling IP restrictions, and monitoring activity logs, you can protect credentials, quickly spot anomalies, and ensure your integrations run without interruption.

    Ready to tighten up your custom app? Log in to the Dev Dashboard today, enable the new controls, and start tracking activity. Need help with the migration? Reach out to your Shopify Plus manager or drop a comment below—we’re happy to walk you through the process.

    Tags
    Sources

    Related Articles

    Why Network Access Declarations Are Now Mandatory for Online Store Apps

    Why Network Access Declarations Are Now Mandatory for Online Store Apps

    Shopify now requires apps that run on the online store to declare their network access in shopify.app.toml. Learn what changed, who’s affected, and how to update your app before the December 2026 deadline.

    November 19, 20264 min
    Understanding the New applyResult Field in RolloutChange: What Developers Need to Know

    Understanding the New applyResult Field in RolloutChange: What Developers Need to Know

    Shopify’s GraphQL Admin API now returns an applyResult field on RolloutChange, letting apps track rollout outcomes in real time. Learn what changed, who it affects, and how to update your code to handle success, failure, and in‑progress states.

    November 19, 20264 min

    November 19, 20261 min
    Store Credit Now Powers Shopify Subscriptions with allowStoreCredit

    Store Credit Now Powers Shopify Subscriptions with allowStoreCredit

    Shopify’s 2027-01 API adds store‑credit support to subscriptions via the allowStoreCredit flag. Learn what changed, who’s impacted, and how developers can enable this new feature in minutes.

    November 19, 20265 min