Navigate the Humind workspace
Learn where configuration, conversations, customers, analytics, Helpdesk, deployment, and company settings live.
The Humind workspace separates Agent configuration from daily customer operations. Knowing where each kind of work belongs helps you fix the source of a problem instead of changing an unrelated setting.
This guide maps the main navigation, explains the permission-aware AI Agent sidebar, and gives new teammates a practical first tour. Labels described here reflect the current B2B workspace; a role can intentionally hide sections and actions.
How this fits into Humind
Humind separates configuration, daily operations, customer data, and measurement so that each change can be reviewed in the right place. The navigation is permission-aware: two teammates in the same company may legitimately see different areas.
Treat configuration as a controlled workflow. Confirm the active company, make one coherent change, test the customer journey, and only then use the live channel. This makes unexpected behavior easier to trace and avoids mixing content, design, and deployment problems.
Before you start
Access: Every signed-in company member sees only the areas allowed by their company role. The owner and administrators can review access in Settings, Company, Teammates.
- Confirm the selected company in the workspace switcher.
- Know your company role or ask an administrator which responsibilities you have.
- Use the command palette with Command K or Control K when you know a destination but not its menu location.
Step-by-step workflow
Understand the top-level areas
Home summarizes the company workspace. Inbox contains shopper conversations and human support. AI Agent contains the customer-facing Agent configuration. Contacts contains customer and visitor records. Analytics contains dashboards and reports. Helpdesk manages the public help center. Merchant Assistant is the internal Humind copilot. Settings contains company, team, integration, catalog, and account administration.
The profile menu also exposes account actions and a Playground entry. Use the navigation destination that owns the data you intend to change rather than relying on a shortcut alone.
Tour AI Agent by job
Train includes Knowledge, Catalog products, Filters, Collections, Promotions, Guidance, Tools, and Escalation. Test includes Batch testing, Test product, and Playground. Deploy includes Sales channels and AI widget surfaces such as Entry point, Collection Quiz, Product Q&A, and AI Gift Generator. Analyze includes optimization, topics, and product analysis where access allows. Settings includes Chat interface, Chat survey, and Chat invitations.
Some entries are admin-only and Procedures is currently displayed as unavailable. Do not build a team workflow around a disabled item.
Follow a safe first tour
Start with Knowledge and Catalog to see what the Agent knows. Review Guidance, Tools, and Escalation to understand behavior and support. Open Playground for a test conversation. Then open Inbox to see the operational result and Analytics to understand measurement.
Finish in Settings by reviewing company languages, allowed domains, Shopify, teammates, roles, and any store-specific configuration relevant to your responsibilities.
- Do not edit during the first pass unless you own the area.
- Write down missing access separately from missing functionality.
- Use one test question to follow the same journey across test, Inbox, and Analytics.
Use permissions as part of the workflow
Humind uses section access with none, read, and write levels. Write includes read. Built-in roles provide common matrices, while custom roles can combine levels for the company's operating model.
When a page or button is missing, confirm the permission before troubleshooting the feature. Permission changes should be deliberate and tested from the affected teammate's account.
Permissions and important caveats
- Top-level navigation and command-palette results are both filtered by access.
- Operators and supervisors do not receive full Agent configuration or Analytics access by default.
- The active company controls which Agent, catalog, Inbox, contacts, Helpdesk, and settings you are viewing.
- Visible disabled or coming-soon entries are not supported production workflows.
Verify the result
Use this checklist before considering the work complete:
- You can name the source area for content, catalog, behavior, support, deployment, and measurement changes.
- The active company and role match the work you intend to perform.
- You can open the test surface and find the corresponding conversation in Inbox when appropriate.
- Missing pages have been classified as access, company context, or actual product issues.
Troubleshooting
A page mentioned in a guide is missing
Check the active company and ask an administrator to compare your role with the required section. Refresh after an access change so navigation and the session use the current matrix.
The workspace shows data for the wrong store
Stop editing, switch to the intended company or Shopify market, and reopen the page. Changes are company-scoped and should not be copied between markets without review.
A command-palette result does not appear
Search by its current label, then verify the underlying permission. The palette does not reveal destinations that the role cannot access.