The complete demo lifecycle

Everything needed to run a flawless client demo, end to end: create a fresh tenant, seed it with realistic data in one click, present the populated platform to the client, then end the demo and purge every trace. Each step below has the exact screen you will see.

Phase 1 · Create the tenant Phase 2 · Seed demo data Phase 3 · Present to the client Phase 4 · End & purge

Who does this: the Platform Operator (super-admin). Sign in at the shell URL, e.g. https://<host>:9443, with the operator account. Everything in Phases 1, 2 and 4 happens in the Platform Console (/admin/console).

Phase 1 — Create the tenant

Sign in as the Platform Operator

Open the platform and sign in with the operator (super-admin) account. Email + password; the platform supports Arabic and English and switches direction automatically.

Login screen — **Sign in.** The bilingual login screen (RFID / email / password).

Open the Platform Console

Go to Administration → Platform Console. The Overview tab is the operator’s control room: tenant counts, MRR, users, storage, dedicated databases, subscriptions by status, and recent billing activity.

Platform Console overview — **Platform Console · Overview.** Live KPIs across every tenant.

Go to the Tenants section

Click Tenants in the console sidebar to see the list of customer organizations. Each row shows the tenant’s user and module counts. Use the + button to onboard a new one.

Tenants list — **Tenants.** Search, select, or onboard a tenant.

Onboard the new tenant

Fill the Key (URL slug, e.g. acmedemo), the Name, the owner email, and pick a plan (Free / Starter / Professional / Enterprise). The plan sets the seat caps, storage limit and which modules are included.

Onboard a new tenant dialog — **Onboard a new tenant.** Key, name, owner email and plan.

Copy the one-time owner password

On Create, the platform provisions the tenant, its owner account, and a subscription in one step, and shows a one-time password for the owner. Copy it now — it is shown only once.

Tenant created with one-time password — **Tenant created.** The owner can sign in immediately with this one-time password.

Phase 2 — Seed the demo data (one click)

A brand-new tenant is empty. Rather than hand-craft data for a demo, one button populates it with a realistic organization and sample content in every module.

Open the tenant and find the Lifecycle card

Select the new tenant from the list. Its detail panel shows usage meters, plan, databases, add-ons, billing, and — at the bottom — the Lifecycle card with Seed demo data and a Danger Zone (Soft-delete / Restore / Purge).

Tenant lifecycle card — **Lifecycle card.** Seed demo data · Danger Zone (Soft-delete / Restore / Purge) · module entitlements.

Click “Seed demo data”

The platform creates the full demo cast and content in seconds, and returns the generated stakeholder credentials once. It seeds:

Organization — a sector, a 3-department tree, sample persons, and enables every module.
One user per stakeholder role (see the roster below).
Module content — My Work items & a calendar event (Hub), a KPI activity, 2 news posts, a chat room with messages, and Drive folders.

Seeding in progress on the lifecycle card — **Seeding.** The demo org, stakeholder accounts and per-module content are created in one call.

The seeded stakeholder accounts

Emails follow <role>@<tenantKey>.demo; the passwords are shown once in the seed result dialog — copy them for the demo. For the Acme Demo Inc tenant:

Account	Role	What they demonstrate
`admin@acmedemo.demo`	Admin	Tenant administrator — full access; authors the demo content
`manager@acmedemo.demo`	Manager	Department manager — approvals, department views
`hr@acmedemo.demo`	HRAdmin	People registry & org structure
`receivedesk@acmedemo.demo`	ReceiveDesk	Registers incoming correspondence
`reviewdesk@acmedemo.demo`	ReviewDesk	Reviews & approves correspondence
`secretary@acmedemo.demo`	SecretaryDesk	Final processing & archiving
`employee@acmedemo.demo`	User	An ordinary employee’s day-to-day view

Tip. Seeding is idempotent — running it again on an already-seeded tenant safely does nothing (it reports “already seeded”).

Phase 3 — Present the platform to the client

Sign out and sign back in as a seeded account — admin@acmedemo.demo is the best “tour guide” because it authored the content and can see every module. The workspace now carries the tenant’s name and brand.

The Home “My Day” dashboard

The landing page aggregates the user’s day across every module: inbox, tasks/approvals, today’s events, news, storage, and quick-create actions — all driven live from the modules.

The app launcher — every module in one place

The waffle launcher (top-left) shows every module the tenant is entitled to. The left rail gives one-click access to Home, My Work, Tasks, Calendar, Meetings and each module.

My Work — the unified inbox (the differentiator)

Every task, reminder, follow-up and approval from every module, in one list, grouped Late / Today / Upcoming. The seed created three items you can point to live.

My Work with seeded items — **My Work.** A reminder, a task, and a follow-up — from the seed — one click from the thing itself.

The unified calendar

Meetings and appointments from chat, mail and workflow, plus a deadline overlay from My Work — one calendar. The seed added a “Weekly team sync”.

News

Internal announcements. The seed published two posts (“Welcome to the platform”, “Quarterly all-hands”).

KPIs

Performance indicators. The seed created a demo activity, a KPI and measurement periods; open the Activities tab to show them.

Chat

Real-time messaging, presence and calls. The seed created a “Team General” room with a couple of messages.

Drive

Files & folders with sharing and in-browser co-editing. The seed created “Shared Documents” and “Projects” folders.

HR / Organization

The people registry and org structure the seed created — sectors, a department tree, and sample persons.

Presenting other roles. To show a stakeholder’s specific view (e.g. a correspondence desk, or a manager’s approvals), sign in as that seeded account — the platform tailors what they see to their role.

Phase 4 — End the demo & purge the data

When the demo is over, the tenant and all of its data can be removed cleanly — from Identity and every module (mail, chat, drive, KPIs, news, hub) — so nothing is left behind.

Two ways to end a demo.

Soft-delete (reversible): blocks login immediately and hides the tenant; a background job hard-purges it after the retention window. Restore rolls it back within that window.
Purge permanently (irreversible): deletes everything now.

Purge — the safety confirmation

Back in the Platform Console, select the tenant and, in the Danger Zone, click Purge permanently. To prevent accidents you must type the tenant’s key to enable the button.

Purge confirmation dialog — **Purge confirmation.** Type-the-key safety — the button stays disabled until the key matches.

Purge — the result

The platform deletes the tenant’s Identity data and calls every module to wipe its own, reporting exactly what each removed. The tenant then disappears from the list and its accounts can no longer sign in.

Purge result dialog — **Tenant purged.** Deleted Identity rows + a per-module breakdown (chat, correspondences, kpis, media, news, notifications, workflow).

Verified. A seeded tenant’s content is fully removed — e.g. a purge of a seeded tenant reported deleting the exact rows the seed created in each module (Hub work items + tags + event, KPI activity, news posts, chat room + messages, Drive folders).

Quick reference — the whole flow

Phase	Where	Action	Result
Create	Console → Tenants → +	Key, name, owner email, plan → Create	Tenant + owner + subscription; one-time password
Seed	Tenant → Lifecycle	Seed demo data	Org + 7 stakeholder accounts + content in every module
Present	Sign in as `admin@<key>.demo`	Tour Home, My Work, Calendar, News, KPIs, Chat, Drive, HR	A fully populated, branded workspace
End	Tenant → Danger Zone	Soft-delete (reversible) or Purge permanently	Login blocked / all data removed everywhere