Understand missing or disabled features
Distinguish a role, context, configuration, or availability issue without bypassing access controls.
In this article
Check in this order
Confirm that you are using Studio, Word, or Outlook rather than a different surface.
Verify the account, active organization, and private or shared project side.
Verify that your affiliation and role are still active.
Look for a configuration, permission, or unavailable-feature message.
Refresh the view once, then reproduce the issue without changing several settings at once.
Interpret the state
- A missing command may belong to another surface or may not be offered in the active release.
- A disabled command may require a project, selection, role, or specific configuration.
- An empty list can be valid when no authorized item matches the current context.
- Access denial must be corrected by the role or affiliation owner, not through a technical workaround.
Practical guidance
Compare the command’s state with its prerequisites: a saved conversation, selected project, active affiliation or editable section may be required. A control that is visible but disabled does not imply that another browser or repeated clicks will enable it.
Advanced tips
When requesting access review, identify the affected resource and intended action rather than asking for broad administrator rights. This helps the responsible person distinguish missing membership from an unavailable feature or a read-only lifecycle state.