Requests and approvals

The Requests inbox is one queue for the approvals your team handles in the dashboard. Pending registrations, subscriptions waiting for approval, and access (scope) requests all land under Consumers, Requests, where you approve or decline each one. The sidebar shows a pending count next to Requests.

What is the Requests inbox?

The Requests inbox is the Consumers, Requests page in the dashboard. It lists every pending registration, subscription approval, and access request in one queue, newest first. You approve or decline each one without leaving the page.

Open it from Consumers, Requests in the sidebar. The page title is Requests, and the count next to the sidebar entry tells you how many are waiting. Once your organization is past its onboarding, the dashboard opens on Requests when you sign in.

What request types appear in the inbox?

Three types of request flow into the inbox. Each row carries a badge so you can tell them apart at a glance.

Each row also shows the requester's name, a subtitle (the email, or the team or subscription and the email), and how long ago the request was made.

Registration requests exist only when you set a registration approval group under Settings, Portal settings, Portal details, in Registration process approval. Without one, sign-ups are approved immediately. See Registration and details.

Subscription requests exist only for plans that have an approval group and no sandbox. A sandbox plan starts the subscription active in the sandbox, and its approval happens in Pipeline. A subscription you create from the dashboard skips approval, so it never appears here.

How are requests grouped into tabs?

The inbox has tabs that filter the same queue by type, each with its own count. All shows every pending request together.

A selection you make on the All tab is kept when you switch to a filtered tab. The rows that show change; the underlying selection does not.

How do I approve or decline a request?

Each row has Approve and Decline. Approve acts at once and the row shows Approved. Decline opens a Reason (optional) field, and Confirm Decline finishes it, after which the row shows Declined.

1. Find the request in the inbox. A Restricted access request shows the consumer's justification quoted on the row.
2. To grant it, click Approve. The row confirms with Approved and the pending count drops.
3. To turn it down, click Decline, optionally type a reason in Reason (optional), then click Confirm Decline. The row confirms with Declined.

What each decision does depends on the type:

Can I approve or decline several requests at once?

Yes. Select the rows you want and a bar appears at the top reading {count} selected. Use Approve Selected to grant them all, or Decline Selected to add one shared reason and Confirm Decline. Each request is processed on its own.

During a batch, each row moves through its own states: Queued, then Approving… or Declining…, then Approved or Declined. If a row fails, it shows Failed with the error and stays selected, so you can retry it without reselecting the rest. Use the select-all checkbox in the list header to select every visible row at once, and Clear selection to start over.

Who can approve requests?

Anyone who can open Requests in your dashboard can approve or decline there. The inbox does not check approval groups.

Approval groups decide who is emailed about a request, and who sees Approve and Reject on a subscription's or a consumer's own page. Keep dashboard access limited to people who should decide on requests. See Approval groups and Members and roles.

What is the number next to Requests in the sidebar?

It is the pending count across all request types. The badge sits on the Requests entry in the Consumers group. It hides when the count is zero and collapses to 99+ above ninety-nine.

The count refreshes every 30 seconds, and right after you approve or decline. It is the fastest signal that something is waiting, without opening the page.

How does this relate to the per-subscription and per-consumer Requests tabs?

A subscription's or consumer's page shows its own Requests (n) tab while it has pending items, where n is the count. The tab uses the same rows and the same approve and decline behavior as the inbox, scoped to that subscription or consumer.

A consumer's tab covers their registration and the requests on subscriptions they own.

Use the inbox under Consumers, Requests to clear the whole backlog, and the per-entity tab when you are already working inside one subscription or consumer. See Subscriptions and Consumer accounts.

Troubleshooting

Match the empty state or message to what it means:

Where to next