Skip to content

Demo Org

Overview

The Demo Org is a shared, always-available Eos organization that anyone can enter with one click from the login page — no sign-up, no setup wizard, and no waiting on an invite. It comes pre-loaded with realistic sample data across projects, tickets, invoicing, agents, and more, so a new visitor can see a fully working product immediately instead of starting from an empty organization.

Because it is shared, other people exploring Eos at the same time can see and change the same data you do. The Demo Org resets to a clean slate on a fixed weekly schedule, and AI agent/chat usage is capped so no single visitor can use up the shared capacity. Organization-level settings are read-only in the Demo Org, even for users who appear as an owner or admin there.

Use this topic to understand how the Demo Org behaves differently from a regular organization, and how to move from exploring the Demo Org to setting up your own organization when you are ready.

When you would use this

  • To try Eos immediately, without creating an account or an organization first
  • To evaluate a specific combination of integrations (for example, QuickBooks Online + Jira, or Xero + Jira) before connecting your own
  • To understand why some settings pages are visible but cannot be edited
  • To understand why a request was blocked with a usage-limit message
  • To understand what happens to your changes in the Demo Org over time
  • To move from the Demo Org into your own, permanent organization

How it works

Entering the Demo Org

On the login page, an Explore tab sits alongside the normal Sign In tab. The Explore tab offers a small set of variants, each a separate pooled Demo Org pre-configured with different integrations already connected:

  • Explore Eos — core features only (projects, tickets, invoicing, agents)
  • Explore Eos (QuickBooks + Jira) — the same core features, plus QuickBooks Online and Jira already connected
  • Explore Eos (Xero + Jira) — the same core features, plus Xero and Jira already connected

Choosing one of these signs you in with Google and drops you straight into that Demo Org's home page — there is no separate password or account to create. If you have explored before, signing in again with the same Google account takes you back to the same Demo Org rather than starting over.

It is a shared environment

Everyone who chooses the same Explore variant lands in the same organization. Any project, ticket, invoice, or record you see may have been created by someone else exploring at the same time, and anything you create or change is visible to them too. Treat the Demo Org as a public, shared space: do not enter real customer data, real credentials, or anything sensitive into it.

Data resets on a weekly schedule

Each Demo Org is automatically wiped and reseeded with fresh sample data on a fixed schedule (Sunday night). Nothing you build in a Demo Org — projects, records, agent configurations, uploaded files — is expected to persist past that reset. If you need to keep something you built while exploring, move to your own organization first (see Moving to your own organization below).

AI agents and chat have a shared daily usage limit

To keep the Demo Org usable for everyone exploring at once, agent and chat usage against a Demo Org is capped on a fixed daily allowance that no one in that org can raise, regardless of role. If the daily limit has been reached, further agent/chat requests are blocked with a message explaining that the demo limit was hit and that it resets the next day. This limit is separate from, and unrelated to, the usage limits on a real paying organization's subscription.

Organization settings are read-only

Demo Org members are commonly given a role such as owner or admin so they can see what those roles normally have access to. However, organization-level settings pages — org profile and branding, invites, member and role management, and custom field definitions — are locked to read-only in a Demo Org no matter what role you hold there. You can open and review these pages, but save actions are blocked.

Billing and integrations are deliberately not read-only: the whole point of the QuickBooks/Jira and Xero/Jira variants is to let you see live, connected integrations, so those pages remain interactive.

Moving to your own organization

When you are ready to stop exploring and set up a real organization for your team, use the Create your own organization button shown next to the "Shared demo org" badge at the top of the screen. This removes you from the Demo Org and takes you to the normal organization-creation flow, using the same email you signed in with. You do not need a different email address to do this.

Typical workflow

  1. From the login page, select the Explore tab.
  2. Choose the variant that matches what you want to evaluate (core features, QuickBooks + Jira, or Xero + Jira).
  3. Sign in with Google — no separate account or password is needed.
  4. Review the welcome popup, which summarizes the shared/reset/usage-limit behavior and offers quick links into a few common areas (Projects, Invoicing, Agents, Settings).
  5. Explore freely. Remember that other people may be changing the same data, and that organization settings pages are view-only.
  6. If you return later with the same Google account, you land back in the same Demo Org you used before.
  7. When ready to commit, use Create your own organization to leave the Demo Org and start a real one under the same email.

Fields, controls, or options you may see

Control or area What it is for
Explore tab (login page) Switches the login page from normal sign-in to the frictionless demo-entry options
Explore Eos / Explore Eos (QuickBooks + Jira) / Explore Eos (Xero + Jira) The three Demo Org variants, each with a different set of pre-connected integrations
Shared demo org — resets weekly badge Shown at the top of every page while you are in a Demo Org, as a reminder of the shared/temporary nature of the data
Create your own organization Leaves the Demo Org and starts the normal flow for creating your own permanent organization under the same email
Welcome popup cards (Project Management, Invoicing, Agents, Settings Review) Quick links into a few good starting points after your first sign-in to a Demo Org

There are no separate skills to configure for the Demo Org. Its behavior is enforced automatically:

  • Which pooled Demo Org you are placed into is decided by the Explore variant you choose, not by anything you configure.
  • The weekly reset and the daily agent/chat usage cap run automatically and cannot be turned off or raised from inside the Demo Org.
  • Organization settings pages detect that you are in a Demo Org and disable their own save actions automatically, regardless of your role.

Things to watch for

  • Do not put real customer data, credentials, or anything sensitive into a Demo Org — it is shared with other people exploring at the same time and is wiped weekly.
  • Work you do in a Demo Org is not permanent. If you want to keep something, move it to your own organization before the next weekly reset.
  • Hitting the daily agent/chat usage limit in a Demo Org is expected behavior, not an error with your account — it resets automatically the next day and does not affect any real organization you may also belong to.
  • Seeing an org-settings page without being able to save is expected in a Demo Org. If the same thing happens in your own paid or trial organization, that is a different issue — check your role and subscription status instead.
  • If you previously left a real organization, your email may be temporarily blocked from creating or joining another real organization (a safeguard against re-using a trial). This restriction does not affect the Demo Org — you can always come back and explore. If you believe this block is preventing you from setting up your own organization when it shouldn't, contact support so it can be cleared.
  • Once you use Create your own organization, you are no longer a member of the Demo Org. You can still return to Explore later to look around again if needed.