> For the complete documentation index, see [llms.txt](https://docs.cortex.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cortex.aic.io/getting-started/training-and-demos/demo-accounts.md).

# Demo Accounts

**Open this area:** In the CORTEX menu, select **Operations & workspaces → Choose workspace**.

Use the retained Demo tenant or a customer trial's detailed fictional scenarios to explore connected training workflows.

**Who uses this:** Administrator, Analyst, Reviewer, Recipient.\
**Open in CORTEX:** `/workspaces`.\
**In-app guide:** `/help?topic=demo-accounts`.

**Expected result:** You can navigate three synthetic lifecycles with ready professional evidence and leadership appointments, customise the safe trial workspace and understand what deployment upgrades preserve.

## Before you start

* Obtain the account's individual password through the authorised operator. Each environment has separate credentials.
* Select a Demo workspace and use fictional training data.
* Use the original Demo owner to manage the organisation. Named workflow roles retain separate responsibilities.

## What to do

{% stepper %}
{% step %}

## Customise the organisation

As the Demo owner, open Organisation settings to change the name, description and default protective marking. OFFICIAL is normally Online; OFFICIAL-SENSITIVE defaults Offline.

An organisation administrator may explicitly override connectivity only within the deployment boundary.
{% endstep %}

{% step %}

## Customise the workspace

Open Manage workspace to change its purpose, context, operating profile and enabled features, or manage membership.

The owner has the tenant capabilities and Manager membership needed for these controls. Feature selection changes presentation; it does not grant another user authority.
{% endstep %}

{% step %}

## Choose your personal layout

Each active role account can use its own dashboard Layout and notifications controls, reorder cards, set filters and pin supported working views. Preferences belong to that user and workspace.

Each scenario includes current synthetic Mission and Operations lead appointments so the corresponding role accounts can open leadership views immediately.
{% endstep %}

{% step %}

## Walk through the workflow

Use the named coordinator, collection, processing, analytical, release and recipient accounts at their respective steps.

Source authority, independent review, approval and distribution remain explicit decisions. The owner can administer the full Demo configuration, but cannot bypass separation of duties.
{% endstep %}

{% step %}

## Compare the three scenarios

Use LANTERN QUAY for intelligence coordination, NORTHBRIDGE for law-enforcement cargo analysis and GLASS HARBOR for a cyber/critical-infrastructure decision.

Each retains a plausible benign explanation, gaps and low or moderate confidence.
{% endstep %}

{% step %}

## Continue after deployment

Deployment updates the original Demo accounts with current role capabilities and the required untouched seeded memberships. It also fills missing professional-framework, competence and leadership-appointment records in retained scenarios.

Passwords, identity IDs, saved settings, preferences and retained investigation records stay in place. Sign out and back in, then reselect the workspace if the page still reflects older access.
{% endstep %}
{% endstepper %}

## Check the result

* Am I in the intended Demo organisation and workspace?
* Does my named account hold the capability and active membership for this step?
* Is the workspace feature enabled?
* Did the current release complete the scenario's leadership upgrade?

## If you get stuck

<details>

<summary>Why is a control still unavailable after upgrade?</summary>

Check the role, grant expiry, workspace membership, feature selection and handling scope. Deliberate restrictions remain in force.

Ask the Demo owner or operator to review the exact missing capability; do not delete the seed marker or recreate the organisation.

</details>

<details>

<summary>Will deployment change my password or reset my work?</summary>

No. The upgrade uses the original tenant and account IDs. It preserves passwords, expiry, organisation settings, workspace configuration, personal preferences and completed scenario records.

</details>

<details>

<summary>Who can change everything in the Demo configuration?</summary>

Use the original Demo owner for organisation settings, users, grants, workspaces and feature selection. Other accounts can customise their own presentation and perform their assigned duties.

Node-wide configuration and independent workflow decisions retain their normal controls.

</details>

## Responsibility and limits

* The owner manages its own organisation; Demo provisioning does not grant global administration or node configuration inspection.
* Deployment never renews expired access, re-enables disabled accounts or restores deliberately removed permissions or modified memberships. Review those through normal administration.
* Changing layout or deploying an upgrade does not approve, release, acknowledge or rewrite retained workflow records.

**Reference and scope:** Implementation guidance. Demonstration duties follow the intelligence lifecycle; they are not operational appointments or legal authority.

**Related workflows:** [Start in the right workspace](broken://pages/276a1df8f3daaf34f78f7031b8a9d14c1edcfdb0); [Use your dashboard and tasking lifecycle](broken://pages/485c81fe64ee565fd4e9c6dc4601826f7ba1af8b); [Manage accounts, grants and workspace membership](file:///7397340/assurance/access.md); [Work through connection and deployment limits](file:///7397340/assurance/offline.md); [Oversee authorised workspaces and retain shift handovers](file:///7397340/direction/mission-operations.md).