Create and prepare your organization's workspace¶
Draft guide: the intended journey and labels follow Figma's
06 Final Screens. The frontend is still being built. Implementation differences that affect these steps are called out below; a live-environment walkthrough and your initial user/business review remain pending.
This guide is for the person creating a customer workspace and for administrators or support staff helping that person finish setup. The feature overview explains the commercial and access rules behind these steps.
Before you begin¶
Sign in with your own active, activated account and open Workspace Access. The creator becomes the first organization administrator. Platform-staff accounts cannot use this self-service customer-creation flow.
Have the organization's name, desired workspace link, company name, contact email, phone number and country ready. Decide which plan and starting seat count to request. Have the person responsible for payment review the final amount when a payment is required. A trial or no-payment result still creates an organization with ongoing administration responsibilities.
If your organization already has a workspace, use the relevant invitation or joining process. Creating another workspace creates a separate organization boundary; it is not a way to obtain access to the existing one.
Enter workspace details¶
- Open Create workspace from Workspace Access.
- Enter Workspace name, Workspace link, Company name, Contact email and Phone number.
- Choose Country from the available list. If the countries cannot load, refresh the page. The form will not continue without a country that exists in the loaded catalog.
- The intended design also shows Region. The current form omits that field; hosting region is configured for the environment. Selecting the organization's country does not select its hosting region.
- Add Website (optional) and Address (optional) if needed.
- Select Continue to plan.
For the workspace link, use a short lowercase label such as example-team. Use letters, numbers and hyphens, start and end with a letter or number, and stay within 63 characters. The label must be unused. A display name with spaces is acceptable, but the workspace link has stricter rules.
The current application keeps temporary workspace details for your signed-in account and login session. Check that the saved details are yours before continuing, especially after changing accounts. This draft is a convenience for moving between steps, not a submitted workspace or a backup. It can expire or become unavailable. If Saved workspace details unavailable appears, reload and check again; do not assume that a workspace or quote was created.
Select a plan and starting seats¶
- Wait for the live plan catalog to finish loading.
- Select an available self-service plan and review its included entitlements, seat limits and storage description.
- Enter a positive whole number in Seats to start with, within that plan's current allowed range.
- Select Continue to review.
If Live plans unavailable appears, check the selected country and refresh. Wait for its live catalog before continuing to review or creating the workspace. The current form clears old plan choices when the country changes and requires a valid live selection; an unavailable price is not a free offer.
Use Request a quote for the quote-only or higher-volume path shown by the product. Review the minimum starting seat count displayed on the current quote form. Its published policy can change; the design's 251-seat example is not a permanent eligibility rule. Other self-service seat allowances and prices must also come from the current catalog.
Request an Enterprise Plus quote¶
This is an alternative to self-service creation. It records a commercial request; it does not create a workspace, take payment or enable Private Cloud.
- From Choose a plan, select Request a quote.
- On Request Enterprise Plus quote, check any prefilled workspace recap and enter or correct Organization name, Primary contact name, Contact email and Country. The current application labels the contact field Contact name.
- Enter the required total in Requested seats. Use a whole number at or above the minimum displayed by the current quote policy.
- Add Commercial notes (optional) to explain rollout needs. Select Include Private Cloud in this quote request only if you want to discuss it. This records interest, not an activation or availability commitment.
- Select Request quote once and wait for the result.
- Review the returned request details and submission time, and retain the request reference where supplied. The intended confirmation is Enterprise Plus quote requested; the current application opens Quote request status and retrieves your saved request. Select Back to Workspace Access when finished. Commercial follow-up must occur before any later workspace setup or checkout.
Use your actual organization and contact details. The current form limits organization and contact names to 200 characters, contact email to 256, and commercial notes to 2,000. Use a valid email address and select a country from the loaded active-country catalog. A quote request does not confirm later workspace eligibility or service availability in that country.
Current application behavior: When saved workspace details are available, the form uses them for the organization, email, country and starting seats, and shows the real recap. Check every value before submitting. If Live quote policy unavailable appears or the countries cannot load, refresh and wait for the required data. A positive seat count alone does not establish eligibility; the current published minimum still applies.
The status page retrieves the request for the account that submitted it. It shows the organization, country, seats, Private Cloud interest, submission time and last update when that read succeeds. It can check again automatically for a limited period, and Refresh status requests another read. A page title or a copied address alone is not confirmation. No quote request in this session or Quote status unavailable means that the page has no verified result to show; it does not establish that the original request failed.
If submission or the status read has an uncertain outcome, keep the original reference, stay with the submitting account, and ask support or your commercial contact to check your organization, contact email and approximate time before resubmitting. A temporary recovery-state failure can occur after the request is saved; it does not undo that request. Reopening or changing the form can start a separate submission, so do not rely on repeated attempts to update the original. An acknowledgement confirms a saved request, not an approved price, confirmed notification delivery, a response deadline or an active subscription.
Review and submit once¶
Check the organization details, plan and Starting seats in Review your selection. The intended design shows Seat price and Estimated total today. The current application obtains a server preview and shows Initial seats, Seat price, Monthly amount and Amount due now in its returned billing currency. Wait for that preview before submitting. If Billing preview unavailable appears, resolve it or refresh; the application disables creation without a usable preview. This read does not reserve a price or create a workspace. The later payment checkout can include configured country tax, so review its final currency and amount too.
For an initial paid subscription, the current application also offers I authorize saving my card for automatic subscription renewals. Select it only if you authorize that use. The control explains that card payment requires this choice and otherwise directs you to an available manual method. A free start or trial does not collect this authorization through this creation path. Selecting it records your choice for the payment request; it does not by itself confirm that a usable card was saved or that a future renewal succeeded. The subscription and payment guide explains how to review billing records and seek payment recovery; its full renewal and expiry reconciliation remains pending. This consent control is an implementation difference from the inspected review screen and remains part of the open design follow-up.
Select Create workspace. The button shows Creating workspace... while the request is in progress. If a validation message appears, correct the named problem. If the request times out or the outcome is unclear, return to Workspace Access and check whether the workspace or checkout already exists before starting again.
A successful creation saves the workspace and initial administrator. It does not mean the workspace is already ready for everyday work. For a paid start, follow its current checkout. The intended no-payment design shows Checkout summary; the current application uses Workspace status when free/trial creation has no payable workflow. Return through Back to Workspace Access while preparation continues. A no-payment summary is not a payment or checkout reference.
Follow the returned checkout state¶
| What you see | Meaning | Your next step |
|---|---|---|
| No payment required | The current creation path requires no initial payment | Choose Back to Workspace Access while preparation continues |
| Secure checkout link is being prepared or Check payment status | The workspace was saved, but the current payment step is not yet usable | Use the available status-refresh action; stay with this workspace rather than creating another |
| Secure checkout is ready or Continue to secure checkout | The current saved payment permits the displayed handoff | Review plan, seats, currency, line items and Amount due now, then continue when ready |
| Latest checkout status unavailable or Current status unavailable | A fresh lookup could not confirm the result | Refresh or ask support to confirm the current state before another payment; the current application clears older checkout results after a failed read |
| Checkout details unavailable | No usable current summary can be shown; this can also follow a failed read with a valid reference | Reopen the existing checkout from Workspace Access or ask support to check the original reference; this message does not prove that creation or payment failed |
After payment, return through Workspace Access and check the current workspace state. A payment-provider confirmation and an active Zerohive workspace are separate results. Payment verification and background preparation must complete. If payment succeeded but access remains pending, retain the existing reference for support; do not assume a second payment is needed.
The intended preparing-checkout screen says that it will keep checking for the link. The current workspace/checkout view checks pending states about every ten seconds for up to fifteen minutes while the view remains open. A failed read stops that sequence. Use Refresh status, Check status or the available refresh action to obtain another read and start a new checking window. Leaving the page, an expired session or an unavailable service can interrupt checking. This is not a promise that setup or payment will complete within fifteen minutes.
The current hosted payment view can show Checking your payment, Payment confirmed, Payment did not complete, Checkout link expired or Payment needs review. Follow that current message. If it asks you to wait or seek review, do not start another payment. Payment confirmed concerns billing; open Workspace Access to confirm that preparation and product access are ready too. Available payment methods depend on the current checkout, currency and environment. If no usable payment step appears, refresh or contact support instead of reusing an old link.
Return to a saved checkout¶
In the intended journey, Workspace Access separates ready Workspaces from Checkout recovery. Open Checkout recovery, identify the existing organization, and follow its current state:
| Intended state | Action shown | What to do |
|---|---|---|
| Payment needed | Resume checkout | Review the saved checkout and amount before continuing to payment |
| Preparing checkout | Check again | Obtain a newer status; creating another workspace is unnecessary |
| Payment issue | Review status | Read Payment needs attention and use Refresh status before considering another payment attempt |
| Checkout expired | Review status | Read the expired-link explanation and refresh the status; confirm that the existing workspace can still be recovered before beginning again |
| Under review | View status | Read Checkout verification under review and refresh later for the next step; do not assume that payment needs to be repeated |
The current frontend uses a shared checkout/status view rather than reproducing every separate intended screen. It retrieves current account-owned details and clears older results after a failed read. Its status routes can recover temporary references for the same account/login session when no explicit reference was supplied. A copied address, expired temporary session or title alone cannot establish a saved checkout.
If Checkout details unavailable appears, select Check status when it is offered for your original request. Wait for that check before relying on an earlier amount or payment link. If the original reference cannot be recovered or no check action is available, return through Workspace Access with the submitting account, or give support the complete original reference. A failed read does not establish that creation or payment failed. If the state and offered action disagree, have the outcome checked before paying again.
Where the current application offers Retry saved checkout, select it only after reviewing the current failure or expiry message. The application rechecks the saved payment before requesting recovery. Wait for its result, then use Refresh checkout status to inspect the resulting checkout and quote before paying. A saved replacement request is not a payment confirmation. The action is deliberately unavailable for some payment paths and uncertain outcomes; its absence is a reason to check status or seek help, not to create another workspace.
An expired initial checkout can lead to the still-unpaid workspace being deprovisioned. The intended Checkout expired screen is not a promise that every expired workspace remains recoverable. Likewise, a ready payment link is not proof that the workspace has finished preparation.
Checkout recovery is available to eligible workspace administrators. Being able to review its payment does not itself give access to the workspace. The recovery list shows selected initial-payment requests, rather than every purchase or every historical state. A missing entry can reflect a changed state, the limited result window or changed membership; retain the original reference before deciding that a request is missing.
Checkout status unavailable means the current application could not read the recovery list. Select Refresh checkout status when offered. This differs from No checkout recovery items, which describes the selected recovery view after a successful read. Neither message is a complete payment history or a reason to recreate the workspace or pay again. If the result remains unclear, ask support to check the original request.
The Workspace Access recovery card can still show Payment needed or Resume checkout for an expired, failed or review record. Those labels alone do not confirm that another payment is appropriate; open its current status. The current checkout uses the saved summary's currency and displays Unavailable for missing/invalid amounts or currency. If these remain unclear, ask support to confirm the record and payment outcome; do not guess the currency or reuse an expired link.
Prepare for a trial ending¶
Confirm the trial's recorded end date and the plan you intend to use afterward. The trial clock begins at subscription creation, including time spent preparing the workspace. Do not assume that every plan has the same duration or that a trial restarts when the workspace becomes accessible.
Make sure the organization has an active administrator with a usable email address. Reminder emails are requested by a background process, but your adoption plan should not depend on an email arriving at a precise time.
Before expiry, review the fallback plan's products and seat allowance. A downgrade can remove product access and deactivate excess licensed memberships. Discuss the continuing plan with the people responsible for administration and billing. A successful account sign-in after expiry does not mean all earlier product access has been retained.
Troubleshoot the specific stage¶
| Problem | Likely boundary to investigate | Action |
|---|---|---|
| Creation is rejected before a workspace is saved | Account eligibility, active country, unique link, plan eligibility or seat bounds | Correct the displayed requirement; use the customer account or quote route that applies |
| The workspace link is taken after an uncertain submission | An earlier attempt may have saved it, or another workspace uses it | Check Workspace Access before choosing a different link or creating another organization |
| The estimated currency or amount differs from checkout | Country-based pricing, configured tax or fallback presentation | Review the latest checkout and seek clarification before paying if it is unexpected |
| Payment link never appears | Billing preparation or the payment provider may need attention | Use the existing checkout reference and ask support to investigate |
| Payment is confirmed but workspace preparation remains pending | Verified billing and infrastructure completion are separate | Give support the payment/checkout reference and approximate time; avoid duplicate payment |
| Trial reminder did not arrive | Recipient, background processing or email delivery | Check the recorded trial date and contact an organization administrator |
| Product is unavailable after creation | Product entitlement, permissions or environment delivery | Review the product's availability and access requirements; creating another workspace is not a fix |
| An unpaid initial checkout expired | The still-unpaid workspace may have been deprovisioned | Ask support to confirm its state before reusing an old checkout link or recreating it |
For support, provide the environment, workspace name/link, checkout reference when available, approximate time, visible state and exact error message. Use the authorized support process for any payment evidence. Passwords, login codes and browser session credentials are not needed in documentation feedback.
For an uncertain original payment, read what the hosted payment-status check can establish. The check uses the saved reference and does not create another charge or checkout. A retained link, failed read or unconfirmed response is not proof that paying again is safe; return to the original request and follow the recovery guidance above.
