> 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/first-session.md).

# First Session

Use this page when you open CORTEX for the first time. It takes you from sign-in to the first saved intelligence record. It also shows where the later steps of the intelligence cycle start.

CORTEX checks your organisation, workspace, role, permission, and handling access as you work. Your screen can show fewer menu items than another person's screen. A menu item shows where to start. It does not give you permission to make a decision.

## Before you start

You need an account from an authorised organisation or platform administrator. You also need access to a workspace. Ask your study lead which workspace and example task to use. Use the handling marking that the task requires.

Keep your browser connected to the CORTEX node while you enter or save work. A change is saved only when CORTEX confirms it. If the connection stops, reopen the record and check its latest saved version before you try again.

## Sign in

{% stepper %}
{% step %}

### Open CORTEX

Open the CORTEX address that your organisation gave you.
{% endstep %}

{% step %}

### Enter your credentials

On **Sign in to CORTEX**, enter **Email address** and **Password**.
{% endstep %}

{% step %}

### Choose whether to remember this device

Select **Remember me for 30 days** only if your organisation allows it on this device.
{% endstep %}

{% step %}

### Sign in

Select **Sign in**.
{% endstep %}
{% endstepper %}

If sign-in fails, read the message headed **We couldn't sign you in**. Check the address and password that your administrator gave you. Ask that administrator for an account or access change. There is no self-service account creation on this screen.

## Choose the workspace

{% stepper %}
{% step %}

### Open workspace selection

In **Operations & workspaces**, select **Choose workspace**. If CORTEX opened the **Workspaces** page after sign-in, stay on that page.
{% endstep %}

{% step %}

### Find the assigned workspace

On **Your workspaces**, find the workspace that your study lead named. To narrow the list, enter its name in **Find a workspace** and select **Search**.
{% endstep %}

{% step %}

### Check the workspace card

Read the card's name, purpose, and handling marking. Open **Context and setup** if you need to check its operating profile or area.
{% endstep %}

{% step %}

### Open the workspace

Select **Open workspace** on that card.
{% endstep %}
{% endstepper %}

**Open workspace** selects the workspace for your work. **Manage workspace** opens its details and members. Use **Manage workspace** when you need to check setup or membership. [Choose and manage workspaces](/getting-started/workspaces.md) gives the full steps.

If the workspace is absent, clear the search and check the list again. Your account may lack membership or handling access. Ask a workspace Manager to check your membership and expiry. Do not use another workspace as a substitute for the assigned task.

## Check where you are

After you open a workspace, CORTEX shows **Workspace overview**. The header shows the selected workspace. The handling banners show the current handling context. Select the workspace name in the header to return to **Choose workspace**.

If you must inspect the setup, select **People & settings** → **Workspace settings**. Its **Workspace details**, **Operating profile and features**, **Connectivity**, and **Members** sections explain the current workspace. A Manager can change some of these settings. Opening them does not change a record.

## Find the next action

**Workspace overview** has four tabs:

| Tab                  | Use it to                                                                      |
| -------------------- | ------------------------------------------------------------------------------ |
| **My work**          | See assigned work, team opportunities, deadlines, and **Act from here** links. |
| **Lifecycle**        | Scan requirement readiness and open the record that needs work.                |
| **Map preview**      | See a small geographic preview of the selected workspace.                      |
| **Tasking evidence** | Select one requirement and inspect its linked stages and blockers.             |

On **Tasking evidence**, enter a term in **Find a visible requirement** and select **Find tasking**. Then choose a record in **Tasking to inspect**. CORTEX does not select a requirement for you. Open **Evidence, blockers and next action** under a stage to read its source links. Select **Open Direction workflow**, **Open Collection workflow**, **Open Analyse workflow**, **Open Product workflow**, or **Open Feedback workflow** for the work you need to do.

You can also use the sidebar to open an area. The sidebar names the main tasks. [Find a page and use the menus](/getting-started/navigation.md) explains the search controls. [Full menu map](/reference/table-of-contents.md) lists every current sidebar item.

## Follow one task through the intelligence cycle

Use this path when the study asks you to work from a question to feedback. Each step saves a separate record. Your role may stop you at a review or approval step. In that case, note the visible state and pass the task to an authorised person.

{% stepper %}
{% step %}

### Create a requirement

Select **Intelligence cycle** → **Direction**. Select **Create requirement**. State the question, decision need, owner, due date, and handling. Save the requirement and check its retained version.
{% endstep %}

{% step %}

### Create a collection plan

Select **Intelligence cycle** → **Collection**. Open **Tasks** and select **Create collection plan**. Link the plan to the requirement. If you need more than one requirement, select **Plan across requirements**. Assign tasks and record results as the plan progresses.
{% endstep %}

{% step %}

### Register sources or acquire material

If your task needs a source, select **Sources & evidence** → **Sources**, then **Register source**. If it needs a file or text record, select **Evidence memory**, then **Acquire material**. Check processing state before you use extracted content.
{% endstep %}

{% step %}

### Create an analytical workspace

Select **Intelligence cycle** → **Analyse**. On **Analytical workspaces**, select **Create workspace**. This creates an analysis workspace inside the selected CORTEX workspace. Link the requirement, use authorised evidence, and record the judgement and review.
{% endstep %}

{% step %}

### Create a product draft

Select **Intelligence cycle** → **Products**. On **Product drafts**, select **Create product draft**. Draft the product against the requirement and its authorised evidence. A product draft is an internal record.
{% endstep %}

{% step %}

### Draft a release

Select **Release & sharing** → **Releases**. On **Controlled releases**, select **Draft a release**. Review the exact product revision and audience. An authorised person must complete the required review and approval before distribution.
{% endstep %}

{% step %}

### Record feedback

After a recipient acknowledges a release, select **Intelligence cycle** → **Feedback**. On **Recipient feedback**, select **Record feedback**. Link it to the acknowledged package. Record usefulness, timeliness, and corrections. A rating does not change the requirement status.
{% endstep %}
{% endstepper %}

Other tasks have their own menu paths. They include source protection, UK sharing, governance, security, police tasking, defence context, people, and settings. Use the [full menu map](/reference/table-of-contents.md) to find the right start page.

## Check your saved work

After you save, return to the record. Check its title, current state, version, handling, and visible history. If CORTEX reports a validation error, correct the named field and save again. If it reports a version conflict, reload the current record, compare the latest version with your draft, and then make the intended change again.

If a page says that access or a service is unavailable, do not treat the empty page as proof that there are no records. Check the selected workspace. Use **Help & node** → **Help & user guide** for task guidance. Ask a workspace Manager about membership and permissions, or a node operator about node availability.

## End the session

Select **Sign out** in the header when you finish. If you changed a form but did not save it, check the unsaved-change warning before you leave.

## Researcher observation sheet

For each task, record the workspace name, the menu item the participant selected, the screen heading they saw, the step where they paused, the exact message shown, and the saved record state or version. Do not copy restricted source content into a research note unless your study has authority for that content. Distinguish a hidden menu item from an empty result and from a failed page load.