Admin screens

Everything lives under the top-level RedeemID menu in wp-admin.

Overview

A setup checklist: connect the store, Test connection, permalinks, Create the page for the sign-in callback, register webhooks, define levels, and tag members with Flow. It folds away once everything is done. Below it, status cards cover configuration, sign-in, the Admin API, webhook delivery health, linked customers and failures in the last 24 hours.

The levels step compares each level’s tags with the tags Shopify’s customers actually have, and lists any tag no customer has. That is usually a typo.

Settings

The Shopify connection values (see Configuration), membership settings such as shared devices, and webhook alerts. A field set in wp-config.php is locked here.

Customers

Every WordPress user linked to a Shopify customer, with their levels.

• Search by WordPress name or email, Shopify email or name, or customer ID.
• Filter by level, disabled customers or failed syncs, then Export CSV of the filtered list or bulk disconnect.
• Activation compares, per level, the customers Shopify tags for it with those who have signed in here.
• Resync all customers re-reads everyone in the background. It is paced to use only the spare half of the store’s API budget, and can be paused, resumed or cancelled. There is no scheduled bulk sync.

Row actions open the customer in the Shopify admin, edit the WordPress user, resync, or switch to the user when the User Switching plugin is active. Each customer’s page shows the synced data, lists their recent events and webhooks, and edits their tags. Tag edits are written to Shopify, then read back, so Shopify stays the source of truth.

Webhooks

The Delivery health panel with a Check now button, the endpoint, whether the signing secret is set, the registration result, a Register webhooks with Shopify button, rejected deliveries, and every delivery received with its outcome. Dead-lettered deliveries can be retried. See Connect Shopify.

App events

A log of every call RedeemID made to Shopify (label, endpoint, HTTP status, duration) and what it did: resyncs, sign-ins, linking, webhook outcomes and admin actions, with who triggered each and from where. No request or response bodies, tokens or secrets are recorded. Entries are kept 30 days, capped at 20,000 rows.

Reports

Levels joined and left, purchases that unlocked access, plan card checkouts and sign-ins for the last 30 days, plus weekly and per-level trends. Counting starts when the plugin is installed and keeps 400 days. No user IDs are kept with the counts.

A level is joined or left when Shopify adds or removes its tag. “Unlocked access” is a purchase whose tag reached WordPress while the buyer was signed in.

Access

• Levels: named access levels, each a customer-tag condition that rules point at, with a health check and a count of matching customers.
• Content rules: the site default, how term rules combine, and the controls for each post type and taxonomy.
• Features: the registered features and who gets each one, with a preview for a tag set or user.
• Test: pick an item and a viewer (a guest, a level, a set of tags or a real user) to see every rule layer, the effective rule and its source, what that viewer gets, and every feature they hold.

Debug

Each configuration value and where it comes from (wp-config.php, Settings, or unreadable), never the value itself. Platform checks for PHP, WordPress, Blockstudio, the plugin’s blocks and permalinks. The Shopify connection and granted scopes, with buttons to refresh discovery, request a fresh Admin token, and run a dry-run entitlement check.