Distinguish an unavailable feature from a route hidden by company role or section permission This guide keeps the work focused on workspace access and provides a repeatable path that a new Humind user can follow without changing unrelated configuration.

When customer-facing behavior is missing or stale, isolate the layer that owns it: source content, visibility, indexing, Agent configuration, deployment, permissions, or publication. Checking one layer at a time produces a useful diagnosis and avoids broad changes that hide the original cause.

Before you begin

Access: Any teammate can report the symptom. Role and permission review requires company administration access.

• Confirm the active company and signed-in account.
• Record the expected page and business task.
• Ask whether another approved role can see the same area.

Work in the smallest owning area described below and keep the current customer-facing state available while you prepare the change. Before clicking any final action, confirm the active company, Agent, store, language, and market shown in Humind. A missing control can indicate read-only access or a capability that is not configured for this company. In that case, record the intended task and ask an administrator to review the exact permission or dependency. Do not bypass the boundary by sharing an account, copying data into another area, or promising a capability that the workspace does not expose.

Step-by-step workflow

1. Confirm the scope and current state

   Reload the workspace and confirm you are in the intended company before treating a missing navigation item as a product issue.

   • Confirm the active company and Agent before editing.
   • Record the current state so the result can be compared after the change.
   • Stop if the screen or permission does not match the intended task.

2. Prepare the change

   Compare the required business task with your current built-in or custom role and its section-level read or write permissions.

   • Use the smallest change that completes the customer task.
   • Keep authoritative information in its owning source.
   • Review labels, dates, language, and customer-visible wording before saving.

3. Save and allow required processing to finish

   Have an administrator make the smallest approved role change, or document that the feature is not available for this company. Do not share accounts to bypass access.

   • Wait for the interface to confirm that the change is saved.
   • If synchronization, indexing, or publication is required, wait for its final state.
   • Reload the area and confirm the saved values persist.

4. Test the complete customer journey

   Start a new session and test both navigation and the specific read or write action, because seeing a page does not prove edit permission.

   • Use a fresh session and a realistic customer scenario.
   • Check desktop and mobile when the result appears on a storefront.
   • Capture the exact failing step if the outcome differs from the expectation.

Important limits and operating notes

• A successful save confirms persistence, not every downstream synchronization or public update.
• Workspace permissions can hide an area or allow reading without allowing changes.
• Do not copy volatile catalog, account, or customer facts into narrative content as a workaround.
• Test only supported capabilities that are visible and configured for the current company.
• Keep changes in workspace access separate from unrelated Agent, Knowledge, catalog, Inbox, or Helpdesk work.

Verify the result

• The active company and account are correct.
• The role decision is documented and follows least privilege.
• The intended action succeeds or fails with an explainable permission boundary.
• No unrelated section permission was broadened.

Keep a short record of what you tested, which customer scenario you used, and what changed. This makes later troubleshooting more precise and helps another teammate reproduce the result without relying on memory.

Troubleshooting

The page appears but controls are disabled

Review write permission for that section and any resource-specific rule. Read access commonly allows inspection without mutation.

A role change has no visible effect

Refresh the session and verify effective company membership, role assignment, and custom-role state. Report the exact section and action if the mismatch remains.

Related guides

• choose roles and permissions
• review account access and sign in methods
• navigate the humind workspace
• troubleshoot a missing page answer or product in humind