Understand HiveAI availability and get help¶
Use this guide to understand how you are intended to enter HiveAI, whether it can currently be used in your workspace and who can resolve an access problem. The intended steps and screen wording follow Figma's 06 Final Screens; the frontend is still work in progress.
Current availability: The account application's product chooser displays a listed HiveAI product as Not ready yet, with its opening action disabled. Supporting access and navigation services exist, but the current chooser cannot open a HiveAI application. The welcome and recovery steps below describe the intended experience for a compatible client when delivered. This guide remains a draft awaiting reader, technical and live-environment review.
Start with the correct workspace¶
- Sign in to your Zerohive account and select the organization you intend to work in.
- Complete any extra verification required for that workspace. See workspace entry.
- Check the products shown for that organization. If HiveAI is listed as Not ready yet, the current chooser cannot open it.
- Ask the workspace administrator or support contact whether an approved HiveAI client has actually been delivered for your environment. A listed entitlement does not establish that delivery.
Switching organizations changes the scope of access. An option or permission in one workspace does not entitle you to the same information in another. If the workspace itself cannot be opened, resolve that account or membership issue before treating it as a HiveAI provider failure.
Refreshing the browser cannot implement a missing client. Repeated sign-ins or credit purchases are not a remedy for Not ready yet in the current product chooser.
Choose where to begin in the intended HiveAI experience¶
Once a compatible HiveAI client is delivered and opened in the correct workspace, the final designs provide this sequence:
- Wait while Checking Your Access is shown. The check may take a moment; it has not yet confirmed that every feature is available.
- On Welcome to HiveAI, choose the kind of work you want to do.
- Select New Conversation under Start with a conversation for help with work, business questions or approved support guidance.
- Alternatively, under More Ways to Work, select Open beside the relevant area:
| Area | Intended purpose |
|---|---|
| Proposals | Review proposed changes and their progress |
| Reusable Workflows | Explore saved workflows and their definitions |
| Organization Intelligence | Explore insights about the organization's work |
On a narrow screen, these areas appear one below another; scroll to find the relevant Open action. Use Back to Workspace Access to return to the account's workspace choices.
The welcome page is an entry point. Opening a conversation does not send a question, and opening Proposals does not approve a proposed change. Source access and available credits are checked when you send work. The conversation, proposal, workflow and intelligence journeys have further rules; the welcome screen does not grant permission to every action in those areas.
Follow the intended access or recovery message¶
Some messages affect a single area while others replace the welcome page. Follow the message for the affected area rather than assuming every HiveAI feature has the same availability.
| Intended message | Your next step |
|---|---|
| This feature isn't available for your account or an area says you do not have access | Ask the organization administrator to review your access to that area |
| Conversations Aren't Available Yet | Ask the administrator to finish setting up the approved AI service |
| Conversations Are Paused | Ask the administrator to review the suspended AI service |
| Conversations Aren't Available | Ask the administrator to review AI service approval and configuration |
| Conversations or another feature are turned off | Ask the administrator to review that feature's availability |
| Proposals, reusable workflows or organization intelligence are temporarily unavailable | Use another available area if it meets your need, or ask the administrator to investigate the affected feature |
| Access to This Organization Is Paused | Ask the administrator to resolve the organization restriction |
| This Organization Is No Longer Available | Select Back to Workspace Access and choose another organization if you have access to one |
| Your Organization Isn't Ready Yet | Wait briefly, then select Try Again |
| Your Session Has Expired | Select Sign In Again and complete sign-in |
| We Couldn't Verify Your Access | Select Try Again; if the problem continues, sign in again |
| We Couldn't Check Your Access | Select Try Again; contact support if the failure persists |
| We couldn't check available areas | This overview needs conversation access. Return through Back to Workspace Access and ask the administrator to review that access. Existing saved work may still be available through an authorized workspace entry, where its own access checks apply |
These are the intended final-screen messages. They are not evidence that the current account application already displays a connected HiveAI welcome page. A failure to load this overview also does not prove that all your saved work has been deleted or that every other area is denied.
What an administrator needs to check¶
An administrator investigating access should establish the following facts. These checks may involve the access administrator, governance owner and technical support team.
| Check | Why it matters |
|---|---|
| The account, organization profile and organization are active | HiveAI checks these before authorizing work |
| The organization has the appropriate Basic or Advanced entitlement | Commercial inclusion is checked separately from feature configuration |
| The person has the relevant HiveAI permissions | A subscription does not grant every person access automatically |
| The workspace policy enables the capability and requested feature | An override or parent-feature restriction can disable a feature |
| Current governance information is available | The capability, approved purpose, provider and applicable jurisdiction context must be verifiable |
| The underlying work is accessible | HiveAI access does not grant access to every manual or source product |
| The selected model profile is approved and operationally allowed | A configured but unapproved or suspended model cannot be treated as ready |
| A compatible client and provider infrastructure exist in the intended environment | Code and checked-in configuration do not prove a usable deployment |
Basic permission is needed for the capability-discovery and knowledge-navigation entry points. Advanced operations have additional requirements. The organization-intelligence dashboard also needs metrics permission and the required administrative or organization-head authority. Use the person's actual assigned access, rather than their job title, when investigating.
Do not remove a governance or source restriction merely to make a product card appear available. Identify the reason and route it to the person responsible for the organization's policy, commercial access or operational configuration.
Understand a capability result¶
An integrated client can obtain a current availability summary from the backend. The final designs translate that information into the welcome and recovery messages above; the checked-in account chooser does not yet provide that connected view. The following explanations describe what the underlying result establishes, rather than additional buttons or messages guaranteed to appear on the welcome page.
If a result says that a provider is configured but has not been checked, it means the configuration and approval checks passed without making a live model request. Sending an authorized conversation still requires provider connectivity, source access and credits. A later failure can therefore be consistent with the earlier readiness result.
If a feature read does not require a provider, that applies to the read being evaluated. It does not promise that a later conversation, generated answer or action can run without a provider or commercial controls.
If access changes while a request is loading, the service can reject the old result. Refresh the workspace's access before trying again. If the denial persists, ask the administrator to inspect the current grant; do not rely on a previously visible option as evidence of continuing permission.
Troubleshooting by symptom¶
| Symptom or explanation | First response | Who should follow up |
|---|---|---|
| HiveAI says Not ready yet in the product chooser | Confirm which frontend has been delivered; the current chooser has no working opening action | Product delivery owner or support |
| Your organization does not include HiveAI | Ask which entitlement applies to this organization and operation | Workspace commercial administrator |
| Your account is not permitted to use HiveAI | Check the current user's Basic or Advanced permission and active organization profile | Workspace access administrator |
| Permissions changed or expired | Refresh access in the correct workspace, then retry once | Access administrator if the result persists |
| The organization is inactive or unavailable | Resolve the organization restriction through the workspace access process | Workspace administrator or platform support |
| Feature disabled | Check the feature override and any disabled parent capability | Workspace administrator |
| Governance or jurisdiction information cannot be verified | Have the responsible policy owner correct or approve the applicable configuration | Governance administrator, with operator support where needed |
| Provider not approved or configuration unavailable | Confirm the approved provider and model deployment configuration | Governance administrator and operator |
| Model profile suspended | Escalate the active operational restriction through the approved support process | Authorized operator or platform staff |
| Configured provider fails when a conversation is sent | Investigate actual connectivity and the operation's source and credit checks | Support and the relevant administrator |
| A prepared manual destination no longer opens | Request a fresh destination; the source, access or conversation may have changed | Knowledge owner or support if the current manual should still be available |
For a support request, include the workspace, approximate time, the visible explanation, the action you were attempting and whether the problem affects one person or several. Include a request reference if the application presents one. Do not send access tokens, passwords, verification codes or restricted document contents in a general support description.
Knowledge navigation in a compatible client¶
The navigation service prepares a location for an application to open. Its current supported knowledge destinations are the published library and a specific accessible manual. The following describes the implemented contract's expected handoff; it is not a claim that these controls have been delivered in the current product chooser.
- A client asks to prepare a destination in an owned conversation.
- The service checks the person's current workspace and source access.
- The client receives a destination with a limited lifetime and rechecks it before use.
- The client reports whether opening succeeded, failed or was cancelled.
A prepared destination lasts no more than 15 minutes and can become invalid sooner. A new permission context, changed conversation, source withdrawal or manual update may require a new preparation. The service rechecks these conditions instead of treating an old destination as permanent access.
Prepared means the service has produced a currently usable destination. Opened means the client reported opening it. Neither means the person has read the manual, completed training or approved its contents. A failed or cancelled opening should remain distinguishable from success.
An example: an employee prepares a link to a maintenance manual, then the knowledge owner withdraws that version. Rechecking the prepared destination makes it unavailable rather than continuing to reveal the old manual's title as an available destination. The employee should obtain a current destination after the owner makes an appropriate version available.
For managers and business reviewers¶
Before announcing HiveAI to a team, establish an actual successful journey in the intended environment with an appropriately permitted test user and approved, non-sensitive material. Check a denied-access case as well as a successful one. Confirm that users know where to obtain help and that the wording does not confuse an available backend capability with a deployed application.
For business planning, treat these as separate questions: Is the capability included? Is this person allowed to use it? Is the provider operational? Is the application delivered? Does this particular operation have the access and spending capacity it needs? The answers can differ without contradicting one another.
A reader review should check whether a nontechnical person can explain Not ready yet, distinguish an entitlement from a permission, identify the right help owner and understand why a prepared destination can expire. Reader feedback complements the separate domain, implementation and environment checks.
The feature overview explains the access model and its current limits in more detail.