Skip to content

Temporary Orgs

Temporary Orgs let your organization experiment with EosHQ configuration, test integrations, and train people in a private org with a fixed expiry. The feature is available to active Admins and Owners of a qualifying Enterprise parent organization.

Every Temporary Org is either a Scratch or a Sandbox. It has its own configuration and data, while its metered usage contributes to the parent organization's normal usage. A small Scratch or Sandbox pill identifies the org. Hover over the pill on the web, or tap it in the mobile header, to see the parent, exact expiry and usage charging. The mobile popup has a Close button.

Choose Scratch or Sandbox

Choice Starting point Typical use
Scratch Standard EosHQ configuration, initially blank or with sample data if selected Try a fresh configuration or run training without copying your parent data.
Sandbox A creation-time copy of your parent configuration, with optional parent business data and a separate file-copy option Test configuration changes and integrations using a copy of your existing setup.

Both choices use the same allowance. Parent changes after creation do not update the Sandbox automatically. Changes in a Temporary Org do not automatically change the parent. The org runs the shared EosHQ application; it does not represent a separately deployed version of EosHQ code.

Understand creation allowances

Your parent organization can have at most two concurrent Temporary Orgs. Its Admins share that limit; it is not two per Admin. An org being created reserves a slot. A successfully created org suspended because of parent subscription eligibility still occupies a slot while its term remains open.

With monthly billing, the parent receives one creation entitlement at the first qualifying payment, then another after every two continuously paid months: months 0, 2, 4, 6, 8, and 10. A full entitlement year provides a maximum of six. Annual billing provides six for the paid annual term. Unused entitlements do not carry forward. Configuration shows your actual available balance and allowance expiry.

A successful creation consumes one entitlement. Disabling an org stops access and automation but retains its data and concurrent slot until its original expiry and cleanup. Sample resets and Standard user replacements do not consume another creation. Billing cadence changes, downgrade/upgrade and rejoining do not reset consumed allowance.

A technical creation failure does not consume a successful-creation entitlement. Partial setup may need cleanup before its temporary reservation becomes available again. Configuration shows the true reservation and cleanup state.

Create a Temporary Org

  1. Sign in to the qualifying parent as an Admin or Owner and confirm the active organization.
  2. Open Configuration > Temporary Orgs and open the Orgs subtab, and select New at the top right. The creation fields appear in a popup.
  3. Enter a name that describes what you want to test.
  4. Choose Scratch or Sandbox.
  5. For Scratch, optionally select Include sample data.
  6. For Sandbox, choose whether to include eligible business data and attachments. Review the copy exclusions.
  7. Review the fixed duration, parent usage charging, disconnected integrations and paused copied automation. Your current verified sign-in email becomes the Admin login and notification address.
  8. Submit the request once.

Creation runs in the background. You can continue working, refresh, or close the page. The status row shows the current phase, such as copying configuration, copying data, copying files or setting up access. Counts appear where meaningful; the page does not promise a percentage or completion time it cannot measure.

The org becomes ready only when all required selected setup finishes. Its lifetime starts then. You receive a detailed email with your login email, content summary, exact expiry, next steps, and links to open/manage the org and this guide. A delayed email does not prevent a Ready org from appearing in Configuration.

Open the org and sign in

Use the org link in the ready email or the normal organization switcher. Sign in with the exact email shown in that message, using your existing EosHQ account and normal sign-in method. You do not need a new password specifically for the Temporary Org.

If the browser is signed into a different account, switch to the email named in the message and reopen the link. A forwarded email does not grant access to another person. Normal authentication and membership checks still apply.

Creating the org does not automatically move you out of your parent organization. Switch deliberately and check the Scratch/Sandbox pill before making changes. On supported mobile versions, the pill in the existing header opens a details popup with a Close button.

Manage license allocations and assignments

The creator initially holds an Admin role and Manager license. A new Temporary Org starts with one Manager and one Standard license. Licenses and login seats are separate: allocating or assigning a license never grants another login seat.

In the parent, open Configuration > Temporary Orgs > Orgs, click the org name, then open Licenses in the details popup. The table shows Allocated, Assigned and Available for Manager, Standard and each add-on. Edit the allocation and select Save allocation. Organization-wide switches use Enabled; integration capacity uses a quantity. Inactive add-ons are read-only.

Temporary Org allocations do not consume parent licenses or affect subscription pricing. All licenses expire with the Temporary Org. Metered usage still accrues to the parent. A reduction below the assigned quantity is rejected; unassign licenses inside the child first. Keep at least one Manager for its Admin. Assignments reserve inventory, including pending login invitations. A concurrent change requires refreshing before saving. The allocation view shows who last changed it and when; changes are audited.

Inside the Temporary Org, open Subscriptions > Users & Licenses. The same license grid is available in permanent orgs. Select Columns to choose which assignable licenses to display. A checked box means that license is assigned. Admins can change the boxes, search, sort, choose rows per page and move between pages. Unsaved changes remain selected across pages, searches and hidden columns. A user can hold one base license; changing it removes incompatible add-ons from the pending selection.

Select Save, immediately after Refresh, to review a confirmation popup listing every changed user and each assignment or removal, including edits on hidden pages and columns. Cancel retains the unsaved edits; Confirm and save applies the whole reviewed selection together. If another Admin changed an affected user, refresh and review before retrying. There must be enough allocated licenses for the final selection. Close active time sessions before removing a base license.

The Temporary Org Admin can assign only the parent-allocated licenses. Ask the parent Admin for more capacity if needed. Procurement requires a Manager license. Inactive add-ons cannot be newly assigned. Existing login licenses remain protected; manage login seats separately. Purchasing, plan changes, renewal, cancellation and payment settings are unavailable in the child.

The normal login policy remains one Admin login and one Standard login. The Admin can manage the Standard login from the login-seat link on the Temporary Org subscription page; an invited colleague or consultant can already belong to other EosHQ orgs. A pending invitation reserves a Standard license. Any Provider-approved extra logins remain separate from license allocation.

Sample and copied personnel records are initially unlicensed reference records. They can receive available licenses for kiosk check-in without receiving app login access. Sample email addresses are not supplied login accounts. The Temporary Orgs area inside Configuration remains locked in a child org.

Expired, disabled or parent-ineligible Temporary Orgs cannot change licenses. A parent Admin can still inspect the allocation while the child data is retained.

Know what a Sandbox copies

A Sandbox copies supported parent configuration, including custom objects and fields, layouts, roles, navigation, reports, Agent definitions, business profile and applicable process settings. Optional business-data copying includes eligible records and their supported relationships. Files are a separate choice.

The completed job's details describe the source boundary and the content actually prepared. A source-copy or required-file error prevents a falsely successful Ready state. Parent and child configuration/data are independent after creation.

The copy excludes login credentials, OAuth tokens and connection secrets, payment methods, billing balances, external webhook registrations, active sessions/timers, pending sends and jobs, and historical execution/diagnostic logs. Copied member references do not inherit real login or license grants. If files were excluded, the result must not present a private parent file as though it had been copied into the child.

Test integrations and automation

Integrations start disconnected, including in a Sandbox. Connect an appropriate test account through the normal integration setup. Some providers require a separate sandbox or test subscription; an EosHQ add-on does not supply a third-party subscription or pay its external transaction fees.

Copied schedules and event-triggered Agents start paused. Review their targets, data, approval rules and external effects before enabling them. The automation capabilities are available under normal permissions and parent usage controls, but copied historic jobs and sends are not automatically replayed.

Connecting a provider that is already linked to the parent may create a provider-specific ownership conflict. Follow the connector's guidance or use an independent test tenant rather than moving the parent's webhook/account connection unintentionally.

Install or reset sample data later

An Admin can use the normal supported sample-data installation and purge controls. Those operations do not extend the lifetime, return a consumed creation entitlement, or grant more login users.

Temporary Orgs are separate from EosHQ's shared demos. They remain configurable and do not undergo the shared-demo weekly reset. Your changes remain until you deliberately remove them or the org expires/is deleted.

Understand parent usage charging

Tokens, Agent runtime and other existing metered transactions in the Temporary Org contribute to the parent organization's normal usage period, allowance, budget and recharge rules. Temporary Org license allocations do not create another independent usage allowance or billing wallet.

The parent's Configuration > Temporary Orgs > Usage subtab lists dated usage records, latest first by default. Search, sort any column, change rows per page, and scroll the table. Token and call records are daily totals; runtime records show each agent run's latest metered usage. These records contribute to the parent's normal billed totals. Creating/copying the org, sample installation and lifecycle cleanup are included service operations rather than customer-billed Agent runtime. Customer automation enabled after setup uses the normal metered rules.

If the parent reaches its normal usage limit, metered work in its Temporary Orgs is subject to that same limit. A child Admin without parent billing authority cannot change the parent's recharge/billing controls or inspect unrelated parent business data. Ask a parent Admin to review usage when necessary.

Watch the fixed expiry

The default term is 30 elapsed days from successful setup. A Provider can change the default for future creation requests, so review the duration shown on your request and the exact expiry in the ready message or pill details.

An existing org cannot be extended or converted to a paid org. Resetting data, changing users, renaming, switching billing cadence, or restoring parent eligibility does not move the date. The clock continues while access is suspended.

Reminders normally arrive seven days and one day before expiry where applicable to the term. The pill details and Configuration remain the source for the actual date even if an email is delayed. At expiry, access and automation stop and deletion begins.

Recover after parent downgrade or expiry

If the parent loses qualifying Enterprise access, all its Temporary Orgs lose entry and execution access. Their original expiry clocks continue. Current parent Admins can still view the Temporary Orgs management page, read dates/status and disable a running org. The emails link directly to that page for the affected parent.

The downgrade/expiry email lists the affected orgs and individual deadlines visible to its recipient. Upgrading the parent again restores access only to surviving orgs still within their original terms that have not been manually disabled and whose deletion has not begun. Review and explicitly resume paused schedules and outbound work; missed automation is not replayed. Restoring access cannot recover deleted data, revive an expired org, extend a deadline or reset consumed creation allowance.

An end-of-term cancellation takes effect according to the parent's normal paid-through access. A parent usage-budget stop is different from losing subscription eligibility: normal usage controls apply to metered operations even while the parent remains on the qualifying tier.

View org details and disable a running org

Open Configuration > Temporary Orgs > Orgs in the parent. Every Temporary Org has one row, including orgs being created, disabled orgs and completed history. Search, sort columns, change rows per page, or scroll the table. Select Refresh for the latest setup and usage status.

Click an org name to open its details popup. It shows the org's management fields, creation options, parent, Admin and Standard seat addresses, setup status, copy warnings, exact dates and email status. Close dismisses the popup.

For a running org, Disable is the only lifecycle action offered. Read the confirmation: login access closes immediately, automation is paused or cancelled, and active runs receive cancellation requests. An external operation already in progress may finish before cancellation is observed. Data and files remain until the original expiry, when normal cleanup starts. Disable cannot be undone, does not refund a creation entitlement and does not release the concurrent slot early. There are no rename, takeover, export, resend or early-delete actions in this management popup.

Temporary Orgs belong to the parent organization. Any current parent Admin can view details and disable a running org without taking a child login seat, even if the creator has left or the parent no longer qualifies for creation.

Understand expiry deletion

At expiry, EosHQ closes access independently of the cleanup worker. Cleanup removes the org's organization data, owned files and associated active-system resources, and verifies its work. Failed cleanup is retried; the org remains inaccessible during retries. Disabled orgs follow the same original expiry and cleanup process.

Deleting a Temporary Org preserves your shared EosHQ login and other org memberships. Minimum parent billing/quota/deletion receipts remain to explain usage and entitlement history. Final verification waits at least 65 minutes after access stops so earlier workers can finish; external provider and reporting cleanup may take longer and are retried. Backups and operational logs follow the service retention policy; the expiry timestamp is not a promise of instantaneous erasure from all retained copies.

Deleting the parent organization also disables and schedules deletion of its Temporary Orgs. A Temporary Org cannot create another Temporary Org.

Troubleshoot common situations

Situation What to do
Create is unavailable Check your current parent, Admin role, Enterprise access, available creation balance, concurrent slots and any pending cleanup protection.
The page was closed during setup Return to Configuration > Temporary Orgs. The job runs independently of your browser.
The email has not arrived Check the Ready row, its details and email status. Use the normal organization switcher or ready-email link; notification failure does not undo creation.
The link shows the wrong account Sign in with the exact login email in the ready/invitation message, then reopen it.
A sample person cannot log in Sample/copied reference records are not supplied login accounts. Assign the available real Standard seat or invite the intended person.
A second invitation cannot be created Check an existing Standard assignment or pending invitation reservation; replace/revoke it through Configuration > Temporary Orgs.
The Sandbox integration is disconnected Connect an appropriate independent test account; connection secrets are intentionally excluded from copying.
Automation is paused Review copied schedules/event Agents, connections, approvals and targets, then explicitly enable the intended work.
Work stops at a usage limit Ask a parent Admin to check the combined parent usage and normal budget/recharge policy.
Access stopped before the displayed expiry Check parent subscription eligibility and current membership. Upgrading can restore access only within the remaining original term.
Creation failed Review the failed stage and cleanup/reservation state. Transient failures retry automatically. After final cleanup, submit a new creation request.
The org expired or deletion began It cannot be extended or reopened. Use a future available creation entitlement for a new org.