A control in a guide is not visible
Check the view, access messages and feature availability when a guide names a missing control.
- What you're seeing
- A guide names a control that does not appear on your screen.
- What it means
- The guide may describe another view, a permission you lack, or a control that is unavailable. A missing control alone does not identify the cause.
- What to do
- Confirm the page and channel, check the view's access message, and ask a workspace admin to check the relevant permission.
- If you do nothing
- The control can remain unavailable for days. Waiting does not grant access or make an unavailable feature appear.
Check the view
Confirm the guide’s prerequisites and the object you have open. A channel conversation, an issue detail pane and a connected repository expose different controls. A narrow window can also change where a menu appears.
The role label under a guide’s title identifies its intended reader. It does not establish your role or guarantee access to every control on that page. Settings describes the available settings pages.
Check access and availability
Read any access or connection message in the affected view. Channel access, repository access and permission to change an object are separate checks. An admin can check the relevant permission; refreshing the page cannot grant it.
Some views offer information without editing controls. A disabled or absent action can also reflect an unavailable feature. Do not infer a permission setting from an action that the application does not offer.
Ask for help
Give a workspace admin the guide address, the control’s name and the channel or object you opened. Include any visible failure reference. Avoid sharing credentials or private document contents in the report.
If the guide promises a control that the application lacks, report the guide address and the differing screen. An access change cannot correct a documentation error. These docs provide no separate public support destination.