Plan-based feature access and requests
The console now shows which features are included in a team's plan and lets them request access to locked ones from wherever they'd use them.
From the changelog: Plan-based feature access and requests
Authdog Team
A gated module that only said "contact us" left operators guessing whether Lidar, impersonation, or another add-on was already on the team's plan. The console now compares plan tiers against current entitlements, and a locked surface can take an access request from the place you would have used the feature.
This is the longer note behind the August 19 changelog entry.
How it works
Authdog subscriptions sit on the organization. Environment configuration does not unlock a sales-gated product by itself. The console now has two complementary pieces:
- A features matrix that compares plan tiers against the entitlements the organization already has
- Feature access requests that are no longer Lidar-only. Any gated module can collect a request from its landing page
Lidar still shows a locked landing until the lidar feature is approved. The same pattern applies to other gated modules (for example Plans & Billing, enterprise SSO, user impersonation, and HRIS provisioning). After approval, the module opens on its normal first tab.
Requests land in a staff inbox for review. That queue is not a tenant-admin screen. Operators submit from the locked module; Authdog staff grant or deny.
Set it up
No separate toggle. Open a module your plan does not include:
- Sign in to the Authdog console with an organization that does not have that feature.
- Open the module (for example Lidar in the sidebar).
- Use Request access on the locked landing.
- After staff approve, reload and use the module as documented.
Check the features matrix from the organization / plan surfaces the console already shows for your subscription. Do not look for Access Requests in the tenant footer unless you are Authdog staff; that inbox is the review side of the same flow.
Trust boundaries
A request is a sales signal, not a permission grant. Until the organization entitlement is written, the module stays locked. An approved Lidar request does not change Authentication policies, and a Billing entitlement does not open Lidar.
Staff review is out of band from tenant RBAC. A tenant owner cannot approve their own feature request in the staff inbox.
Do not treat a visible sidebar label as proof the feature is entitled. Lidar's label can appear while the page is still the request landing.
Try it
Open Lidar (or another gated module) on an organization that does not include it and submit a request from that page. Lidar itself is documented in Lidar concepts. The original release note is in the changelog.