Check current feature availability
Use surface, availability state, verification date, and observable result before following a procedure.
- Available
- The surface and user path are present; required permissions and data still apply.
- Configuration dependent
- The path exists but depends on a template, catalog, integration, authorization, client, or organization setting.
- Deferred public
- Content can eventually be public but is not published before the surface meets its readiness gate.
- Private SuperAdmin
- Content requires separate authenticated delivery and never belongs in the current public output.
Open the article for your surface.
Check its state and last verification date.
Confirm that the control exists in your account and organization.
Perform a low-risk action and verify its result before important use.
Read the dates correctly
Updated is the editorial modification date. Guidance reviewed records the last review against the referenced implementation. Neither date guarantees that your organization has enabled the feature. Confirm the visible controls, permissions and outcome in your own environment. Screenshots illustrate the language and state captured; they do not establish availability in every account.
Was this article helpful?