Gated and Specialized Sections
Find out why an admin page is hidden, redirected, feature-gated, or unavailable.
Some admin pages are intentionally conditional. If a section is missing from your sidebar, it does not always mean the page is broken. It may be hidden because the organization does not have the feature, your role does not include the permission, or the page is part of an internal rollout.
Use this guide when an admin asks, "Why can't I see this page?" or when you need to decide whether the next step is a permission change, plan change, feature enablement, or a different guide.
Before you begin
Check three things before troubleshooting a missing section:
- Your current organization. Admins with access to multiple organizations may be looking at the wrong tenant.
- Your role and permissions. Some pages require feature-specific permissions, not just general admin access.
- The organization's plan, entitlement, or rollout flag.
If a page is feature-gated, changing the sidebar will not expose the workflow. The organization must have the feature enabled and the user must have the required permissions.
What to check first
Start with the simplest explanation:
- Confirm the admin is in the correct organization.
- Confirm their role includes the section's read permission.
- Confirm the organization has the feature or plan access.
- Confirm the route is not a legacy redirect or placeholder surface.
Use this order before escalating to rollout flags or engineering investigation.
Why a section may be hidden
Common reasons a page is missing
| Reason | What it means | What to check |
|---|---|---|
| Role permission | The user does not have the permission required to view or manage the section. | Review the user's role and the role permission set. |
| Plan or entitlement | The organization has not purchased or enabled the feature. | Check Subscription Plan or the feature-specific upgrade prompt. |
| Feature flag | The workflow is being rolled out selectively. | Ask a platform admin to confirm rollout status. |
| Redirected legacy route | The old route exists only to send admins to the current page. | Use the destination page, not the legacy URL. |
| Placeholder route | The route exists but the product does not yet expose a complete workflow. | Do not document it as self-service until the UI is real. |
| Internal diagnostic page | The page is for debugging, audit, or schema inspection. | Limit access to admins who need operational investigation tools. |
Feature-gated and specialized areas
Feature-gated admin areas
Monetization
Monetization pages are hidden unless the organization has commerce access.
When enabled, Monetization includes:
- Setup.
- Products.
- Orders.
- Coupons.
- Subscriptions.
- Reports.
Use Monetization when Built LMS is used to sell or manage paid learning products. Do not expose Monetization docs to admins who are not using commerce; the concepts create confusion when the feature is unavailable.
See Monetization for the overview, Monetization Setup for payouts and currency, and Products and Prices for paid product publishing.
Community
Community has two admin surfaces:
| Route | Use |
|---|---|
/admin-dashboard/community | Moderate community content and manage experts. |
/admin-dashboard/settings/organization/community | Configure discussion forums and organization community features. |
The management page includes:
- Moderation Queue
- Experts
The settings page is guarded by the community:configure permission. If an
admin can see community content but cannot configure it, review their role
permissions before assuming the page is unavailable.
Document Community as a normal workflow only when the organization has the feature enabled and there is a confirmed support or success need for community setup docs.
AI and intelligence areas
AI settings, operations, and tools
AI-related admin pages are split across several areas:
| Page | Use |
|---|---|
| AI Analytics | Monitor usage, quality, users, exports, and rate-limit risk. |
| AI Operations | Start and monitor bulk generation operations and exports. |
| Settings > Features > AI | Configure the AI assistant, course generation (source materials, generation profiles, learning blueprints, and compliance policies), and AI course updates. |
| Pending briefs and outlines | Review generated course planning work before it becomes course content. |
| Course AI Update sessions | Review proposed updates to an existing Course Builder course. |
Some AI routes require permissions such as ai:view_analytics,
ai:manage_operations, ai:*, admin:*, or settings permissions. Some also
depend on feature entitlements or preview flags.
Use these guides for the primary workflows:
Source materials
The old source-materials route redirects to Settings > Features > AI > Course Generation with the source materials section selected. If an admin asks where source materials went, send them there.
Only source materials that are ready can be selected for generation workflows.
Intelligence settings
Learning Intelligence has two kinds of pages:
- Intelligence dashboards and analysis pages.
- Settings > Features > Intelligence, which controls the intelligence pipeline.
The settings page can control:
- Pipeline enabled or disabled.
- Pipeline schedule: daily or weekly.
- Automation mode: recommend, suggest with approval, or automatic.
- Privacy mode: individual, team, or anonymous.
- Alert verbosity: quiet, normal, or verbose.
View access requires analytics-read permission. Update access requires analytics-manage permission. Each setting saves when changed.
Use Learning Intelligence for the dashboard and analysis workflows. Document the settings page separately only if admins are expected to operate the pipeline themselves.
Specialized settings areas
Gamification settings
Settings > Gamification controls how learners earn points and progress through gamification features.
The page loads:
- Organization gamification settings.
- Point rules.
- Badges.
Treat this as a specialized settings area. If gamification is not part of the organization's learner experience, the page may be hidden, empty, or irrelevant to most admins.
Before writing or using a gamification guide, confirm that the organization has gamification enabled and that badges or point rules are actually being used.
Live learning settings
Live learning has both an operational page and a settings page.
| Page | Use |
|---|---|
| Live Learning | Create and manage events, sessions, attendance, monitoring, and series. |
| Settings > Live Learning | Configure organization-wide live learning defaults. |
The settings page can control:
- Default session duration.
- Default completion threshold.
- Recording auto-archival.
- Email reminders.
- Public recordings.
The page requires course-write or settings-write permission. Use Live Learning for event operations, and document settings separately when the organization needs a policy-level setup guide.
Subscription plan
Settings > Subscription Plan shows the organization's plan features, special overrides, and monthly active learner usage.
Use it when an admin needs to answer:
- Which features should be available on the current plan?
- Is a missing feature caused by plan access?
- How much monthly active learner usage has the organization consumed?
- Are special overrides active?
This is not a billing operations guide. For paid learning commerce, use Monetization and Products and Prices.
Exceptions and operational pages
Integrations that need special handling
Some integration routes are broad, external, or partially specialized.
| Route | Notes |
|---|---|
/admin-dashboard/integrations/[integrationId] | Shared detail page for HRIS, CRM, support, messaging bot, credential, and legacy sync integrations. |
/admin-dashboard/integrations/credly | Credential integration page. The current page contains a placeholder organization ID, so verify implementation before treating it as production-ready. |
/admin-dashboard/integrations/live-learning-platforms | Dedicated live learning platform integration setup. |
/admin-dashboard/integrations/api-access and /webhooks | Covered by the API Access and Webhooks guides. |
Use API Access for API keys and OAuth applications. Use Webhooks for webhook setup and delivery review. Use Connect a Live Learning Platform for Zoom, Google Meet, Microsoft Teams, and Livestorm.
For other integration detail pages, confirm the exact integration type before writing a dedicated guide. HRIS setup, CRM sync, support tools, messaging bots, and digital credentials should not be merged into one generic article.
Diagnostics
Diagnostics pages are intended for investigation, audit, and debugging.
They can include:
- Audit Trail
- Schema Inspector
- Telemetry
- Integration audit logs
- API access audit logs
Use these pages when an admin needs to investigate security-relevant events, schema shape, API access, or navigation telemetry. They are not normal daily admin workflows.
See Audit Trail and Diagnostics.
Legacy redirects
Some routes exist only to redirect admins to the current page:
| Legacy route | Redirects to |
|---|---|
/admin-dashboard/auth | /admin-dashboard/settings/users-access/auth |
/admin-dashboard/settings | General Settings, or Appearance when ?tab=appearance is present. |
/admin-dashboard/settings/organization/learning-assistant | /admin-dashboard/settings/features/ai |
When documenting the product, link to the destination page rather than the legacy route.
Placeholder or incomplete surfaces
Some routes exist before the complete admin workflow exists.
Known examples:
- Shared Page Sections currently opens a placeholder rather than a full reusable-section editor.
- AI Operations > Reports & Analytics currently shows a placeholder card.
- Credly Integration should be verified before production docs rely on it because the current page uses a placeholder organization ID.
Do not tell admins to complete a task on a placeholder page. State clearly that the page is not yet a self-service workflow, or route them to the current working alternative.
Verify and support gated access
Verify success
A missing or specialized section is explained when:
- The admin is confirmed to be in the correct organization.
- The route exists or is known to redirect, be feature-gated, or be incomplete.
- The user's role permissions match the section's access requirements.
- Plan access, entitlement, or rollout flag status explains feature visibility.
- Placeholder and diagnostic pages are not described as normal self-service workflows.
- The admin is routed to the current working guide or page.
Troubleshooting
- Confirm the admin is in the correct organization.
- Confirm the route exists in the current product.
- Check whether the route redirects to a newer route.
- Check the admin's role and permissions.
- Check feature entitlement or plan access.
- Check rollout flags for preview features.
- If the route is diagnostic or placeholder-only, do not treat it as a normal workflow.
Use the destination page in docs and support replies. Some old admin routes exist only to preserve bookmarks or old links.
Check whether the page is listed as a placeholder or diagnostic surface. Do not write self-service instructions for a page that does not expose the real form, list, editor, or save action.
Compare organization, role permissions, plan access, and rollout flags. If those do not explain the difference, ask a platform admin to confirm whether the page is feature-flagged or restricted to a specialized role.