Why a dashboard control is missing: roles, plans, flags, and browser checks

TL;DR — If you cannot see a control you expected, the most common cause is that you are signed into the wrong account, workspace, or role, so the UI is hiding it. Start by checking your profile, current workspace/environment, and permissions in your provider's dashboard; if those are correct, the next most likely causes are plan limits, feature flags, browser caching, or the item being in a state where that control is intentionally hidden. Reading time: ~6 min

The scenario

It is Tuesday afternoon and you are trying to change a setting you have used before: maybe the "Delete" button for a project, the "Add domain" button, or a billing tab your teammate told you to open. You are definitely on the right website, but the control is just not there. Your teammate can see it in their screenshot, your client is waiting for an update, and now you are wondering whether the app is broken or your access changed. Before you open a support ticket, you can usually narrow this down in a few minutes.

Symptoms

• A button, tab, or menu item shown in docs or a teammate screenshot is missing from the page.
• The page loads normally, but a specific action is absent, disabled, or replaced with read-only text.
• You may see messages like:
  • "You do not have permission to perform this action"
  • "Contact your administrator"
  • "Upgrade to access this feature"
  • "This setting is managed by your organization"
  • "No actions available"
• The same URL shows different controls for different users.
• The control appears in one project, site, or environment, but not another.
• In browser developer tools (the browser's built-in debugging panel), the page request may return:

403 Forbidden

or a feature/config request may include:

{"enabled":false}

• After a hard refresh or opening the page in a private/incognito window, the control appears or disappears.

Likely causes

Step-by-step diagnosis

1. Check that you are in the right account, workspace, project, or environment.

   • Dashboard path: click your avatar/profile menu, then look for account/workspace switcher; also check the page breadcrumb and URL.
   • What confirms the problem: the current workspace, project, or environment name does not match the one where the control should exist (for example, you are in "Staging" instead of "Production").
   • Jump to: Fixes → Wrong account, workspace, project, or environment.

2. Check your role on the current workspace or project.

   • Dashboard path: your provider's dashboard → Settings or Admin → Team, Members, Users, or Access.
   • What confirms the problem: your role is Viewer, Analyst, Billing-only, Read-only, or similar, while the action usually requires Admin, Owner, Editor, or Project Admin.
   • Jump to: Fixes → Role lacks permission.

3. Check whether the feature is part of your plan.

   • Dashboard path: Settings → Billing, Subscription, or Plan.
   • What confirms the problem: the plan page labels the feature as unavailable, locked, or upgrade-required, or the UI shows "Upgrade to access this feature".
   • Jump to: Fixes → Feature not included in your plan or license.

4. Check feature flags and organization policies.

   • Dashboard path: Settings → Features, Labs, Organization, Security, or Admin Policies.
   • What confirms the problem: the feature is toggled off, limited to certain workspaces, or disabled by an org policy such as "Only owners can manage domains".
   • Jump to: Fixes → Feature flag or organization policy disables it.

5. Rule out browser cache or extensions.

   • Fastest check: open a private/incognito window and sign in again. If your browser supports it, disable extensions for that window.
   • What confirms the problem: the control appears in private browsing, in another browser, or after a hard refresh.
   • Jump to: Fixes → Browser cache, extension, or stale frontend.

6. Check the item's current state.

   • Dashboard path: open the specific item and look for status badges such as Draft, Archived, Locked, Disabled, Pending verification, or Deleted.
   • What confirms the problem: the action is intentionally hidden for that state, such as no "Publish" button on an archived item or no "Delete" on a locked record.
   • Jump to: Fixes → Item state hides the control.

7. Compare docs/version/region if all else looks correct.

   • Dashboard path: Help, About, or page footer; note region/version if shown.
   • Optional browser check: open developer tools → Network, reload the page, and click the request that loads feature/config data.

Look for 403 responses or config values like enabled:false

• What confirms the problem: the docs are for a different UI version, region, or product tier.
• Jump to: Fixes → Docs, version, or region mismatch.

Fixes

Wrong account, workspace, project, or environment

Switch to the correct scope in the dashboard.

• Click your avatar/profile menu.
• Use the account/workspace switcher.
• Open the correct project/site/app.
• If the app has environment tabs, switch from Development/Staging to Production, or vice versa.

If the URL contains an ID or slug, compare it to a teammate's working URL. For example:

https://app.example.com/org/acme-prod/projects/web-store/settings

If yours says acme-sandbox, you are in the wrong place.

Verify it worked: reload the page and confirm the missing control now appears in the expected location.

Role lacks permission

Ask an owner or admin to review your access on the exact workspace/project, not just the organization.

• Dashboard path for the admin: Settings/Admin → Team/Members → select your user → change role.
• Typical role changes that restore controls: Viewer → Editor, Billing-only → Admin, Member → Project Admin.

If your provider supports granular permissions, the admin should enable the specific capability, for example "Manage domains", "Delete projects", or "Edit billing settings".

If you need a message template, send this:

Please check my role on <workspace/project name>. I cannot see the <missing control>. I am currently listed as <your role>, and I likely need <required role/permission>.

Verify it worked: sign out and back in, then reopen the page; the control should be visible without using a direct URL.

Feature not included in your plan or license

Open the billing/subscription page and confirm whether the feature is plan-gated (restricted by subscription level).

• Dashboard path: Settings → Billing/Subscription/Plan.
• If the feature is locked, either upgrade the plan or use the supported alternative shown in the UI.

If you are an admin and need to upgrade, follow your provider's billing path. Because vendor screens vary, use the billing page's own upgrade button rather than guessing a menu path.

If you are not an admin, send this to the billing owner:

The <feature name> control is not visible on our current plan. Please review Settings → Billing and confirm whether our subscription includes it.

Verify it worked: after the plan change is active, refresh the page and confirm the control is no longer marked as locked or upgrade-only.

Feature flag or organization policy disables it

Check whether the feature is turned off centrally.

• Dashboard path: Settings → Features/Labs, or Admin/Organization → Policies.
• Search for the feature name or the area it belongs to, such as domains, SSO, API keys, billing, or deletion.

Common examples:

• A beta/preview feature must be enabled before its control appears.
• An organization policy hides self-service controls from non-owners.
• A security policy disables destructive actions like delete/export.

Change the toggle or policy only if you understand the impact.

⚠️ Changing organization policies can affect every user in the workspace and may expose sensitive actions like deletion, export, or billing changes.

Verify it worked: refresh the page and confirm the control appears for the intended users only.

Browser cache, extension, or stale frontend

First, retry in a private/incognito window. If that fixes it, clear cached site data in your normal browser.

• Browser path: open the site → click the padlock/site settings icon in the address bar → clear/reset site data.
• Then hard refresh the page:

Windows/Linux: Ctrl+Shift+R
macOS: Cmd+Shift+R

• If you use ad blockers, privacy extensions, or script blockers, disable them for the site and reload.

If you need a command-line check from a machine with browser access, compare the page headers before and after a deploy:

curl -I https://app.example.com/path/to/page

Look for changed asset references or cache headers.

Verify it worked: the control appears in your normal browser after clearing site data or disabling the interfering extension.

Item state hides the control

Open the specific item and change it to a state where the action is allowed.

• Examples:
  • Unarchive an archived item before editing it.
  • Complete domain verification before DNS/TLS controls appear.
  • Unlock a record before deleting it.
  • Switch from read-only audit view to edit mode.

Because labels vary by product, look for a status badge near the item name and an action menu such as "More", "Actions", or the three-dot menu.

If the item is locked by a workflow or approval step, ask the approver to complete or cancel that step.

Verify it worked: after the status changes, reload the item page and confirm the expected action is visible.

Docs, version, or region mismatch

Open the docs page your teammate used and compare three things: product name, region, and UI version/date.

• If the docs are for a different region or product edition, switch docs versions if the site offers a version selector.
• Check release notes or changelog for renamed or moved controls.

If you need evidence for support, capture:

- Full page URL
- Workspace/project name
- Your role
- Screenshot of the missing area
- Screenshot of Billing/Plan page
- Browser name/version

Verify it worked: you find the renamed/moved control, or you have enough exact detail to open a support ticket without guesswork.

Prevention

• Keep a short internal access matrix for each workspace/project. Example:

{
  "production": {"owners": ["ops@example.com"], "admins": ["lead@example.com"], "editors": ["dev1@example.com"]},
  "staging": {"owners": ["ops@example.com"], "admins": ["qa@example.com"]}
}

• Add a release checklist item for UI-gated features: confirm role, plan, and environment before handoff.

Before sending instructions, include: exact workspace, exact role required, exact plan required, exact menu path.

• Pin important browser checks in your team docs so people do not lose time to cache issues.

1. Open private window
2. Sign in again
3. Hard refresh
4. Disable extensions for the site
5. Clear site data

• For admin-managed apps, review organization policies quarterly and document which controls are intentionally hidden.

Policy review fields: feature name, enabled/disabled, who can change it, affected workspaces, last reviewed date.

• In CI/CD or release notes, record UI changes that move or rename controls.

{"date":"2026-10-01","change":"Moved Domain settings from Project Settings to Infrastructure","affected_roles":["Admin","Owner"]}

• When opening support tickets, always include the exact scope and role first. This avoids the most common back-and-forth.

I am in workspace <name>, project <name>, environment <name>, role <role>, plan <plan>, and the missing control is <control name> on URL <url>.

This article was written by an AI system and published pending human review. Verify anything you intend to act on.