access-requests

Access Requests

The Access Requests page (/access-requests, "Early Access" in the nav) is the operator's approval queue — who applied to migrate onto the platform, what they'd bring, and where each application stands. It requires the early_access.manage privilege; without it the page shows a locked state ("You need the early_access.manage privilege to review the approval queue."). See the god-mode overview for how the gate works. A badge by the title reads persisted (real DB) or demo (seeded, in-memory), so you know whether the rows are live applicants or seed data.

Where applications come from

Applications are created by the public Request early access form (/early-access, in the (auth) route group). An applicant provides:

FieldNotes
NameRequired
EmailRequired, validated
CompanyOptional
What would you migrate?The use case — required
Fleet size1–3 / 4–10 / 10+ / 50+ servers

The apply action validates the input, refuses emails that belong to a control-plane operator (they should sign in instead), and creates a pending application. A related funnel, full registration, additionally creates a pending user with a password and an application at once — either way the application lands in this queue as pending.

What the page shows

A KPI row counts the queue by status: Pending (accented when any await review), Approved, Rejected, and Total. The Early Access table below defaults to the Pending filter (you can switch to Approved, Rejected, or All), and shows each applicant with their name, email, company, fleet size, when they applied, and current status. Selecting a row opens a detail drawer — the use case shows there.

Reviewing applications

You can act on one application from its drawer or on many at once with the bulk bar:

ActionWhat it does
ApproveMarks the application approved and activates the linked user — or, if none is linked, creates an active product user from the application's details. Records who reviewed it and when.
RejectMarks the application rejected (an already-approved application is left alone). Records the reviewer and timestamp.

Both actions re-check the early_access.manage privilege server-side, so they can't be called around the locked page. Approving is the bridge into the product: an approved applicant becomes an active account visible on the Users directory. In demo mode the seed set includes a few sample applications (e.g. Lumen Health, Brightmesh, Northwind MSP) so the queue is populated without live data.