# Where everything is

A quick way to answer "where is…?". Each screen below says where it is, what it has, and what you see if something is missing (no team, a revoked key). The kit, file by file, is in [Your kit](/docs/access/kit/).

## The header

On every page of DevLab (signed out it has a sign-in link instead of the account menu):

- **Documentation**: a menu with the pages of these docs. **Search the docs** opens the search (Ctrl or ⌘ + K).
- **Playground** and **Your integration**. Your integration is there with any account; if your account has no team, the page says so.
- **Theme**: a button that rotates **Auto**, **Light** and **Dark**. **Language**: a menu with English and Español. DevLab remembers both in your browser.
- **The assistant**, when this DevLab has it (Ctrl or ⌘ + I).
- **The account menu** (your initials): your email and your team, **Your account and API key**, **Your integration**, **Invite person** (organization admins only), **What's new**, **Legal** and **Sign out**.

On a narrow screen the same links are in the ☰ menu.

## For developers

You belong to a team. Everything on this page you can open, with the limits each screen explains.

### Playground

#### Playground › Measure

Runs a capture with the SDK (default) or the HTTP API and shows the calls it makes.

**What it has**

- A switch between the SDK and the HTTP API, and a choice of source: sample video, camera or synthetic sample.
- Two controls choose what to measure: Context (Measurement first, each context with its number of protocols) and then Protocol, with only that context's protocols; a context with one protocol shows it fixed.
- A panel with the calls your backend would make.
- When the protocol has an interpretation, it appears in the result card.
- If Engine takes longer than the playground waits for the interpretation (by the SDK or the HTTP API), the result card says Engine is still interpreting and offers Ask for the interpretation again.
- With a context that has audiences, an Audience control chooses who the interpretation is written for (from your kit), and the result card says who it was written for.
- After a reload, the result card shows Restored session: the latest session of your test person, read again from Engine.

**If something is missing**

- Not signed in or without an active team, you only see the recorded example.
- Measure is disabled, with the reason under it, when the protocol's longest case does not fit in the playground's 10 min per session (a step without its own maximum counts 1 min).

#### Playground › Flow

Shows every real call in its lane and at its instant: Your app, Your backend and Events.

**What it has**

- The sequence of calls of the run you made in Measure.

#### Playground › Baseline

Captures the baseline of a person, which comes before any protocol.

**What it has**

- The same SDK or HTTP API switch and the same source as Measure.
- The state of the baseline: ready only when Engine says so.
- When you come from Measure, a You came from Measure strip with Go back and measure: it takes you to Measure without starting a capture.

**If something is missing**

- Not signed in or without an active team, you only see the recorded example.

#### Playground › Results

Shows what a session measured (by default the latest) and lets you download it.

**What it has**

- Counts, one small chart per indicator, a table and local downloads.
- A Session selector with your sessions of the last 24 h, grouped by test person; choosing one reads it again from Engine. The latest always follows Measure.
- A strip at the top that says where what you see comes from: Recorded example, Your session, a session you chose or Restored session.
- A range selector: Whole session, one question or one step; the tiles, the series, the table and the downloads follow it, each mean with who gives it (Engine or DevLab). With a question or a step, the question and What they said. Not the text of the interpretation.
- Back to Measure, when you came from Measure.

**If something is missing**

- Measure a session in Measure first, or look at the recorded example. The interpretation is not here: it appears in the result card of Measure and in Deferred.

#### Playground › Deferred (server-side)

Records on the device, uploads the recording and lets a server process it later (Preview).

**What it has**

- Four phases: record, upload, process and results.
- Record works with the sample video or the camera.
- The same Context and Protocol controls as Measure, with the same choice; a context this environment does not record in deferred appears disabled, with the reason.
- As in Measure, a step without its own maximum closes itself after 1 min and a session stops at 10 min; a session stopped at 10 min is not uploaded.
- The results include the interpretation when there is one.
- The same Audience control as Measure, with the same choice.

**If something is missing**

- Not signed in, without an active team or when recording is unavailable you see the recorded example and no Record button.
- In a DevLab with recording, if your organization does not have deferred processing turned on, the section says so, explains what it is and shows the recorded example, with no Record button; Neurologyca turns it on, and then it works in the playground and in your integration.
- Record is disabled, with the reason under it, when the protocol's longest case does not fit in 10 min, or when its kit has no assigned context.

#### Playground › SDK and API

The code behind each piece of the playground: the SDK first, the HTTP API as the complement.

**What it has**

- Cards for the camera view, the time chart, the result tiles, reading later from your backend, checking the device before measuring and when to load the face and speech models.
- A button to download the live starter (the whole Measure flow; the pieces it does not include are copied from Code).

**If something is missing**

- Download the live starter is disabled without a session ("Sign in to download") or when your team has no active key.

#### Playground › SDK and API › Camera view

The code and data of the camera view.

#### Playground › SDK and API › Time chart

The code and data of the time chart.

#### Playground › SDK and API › Result tiles

The code and data of the result tiles.

#### Playground › SDK and API › Store and read later

What your backend stores at enrolment to read the results of a capture afterwards, how long Engine keeps them and how to delete the person.

#### Playground › SDK and API › Check the device

What this browser can do on this device before measuring: the device check by check, the preflight code and the session-rate rule. Check now works without signing in, asks for no permission and never calls Engine.

#### Playground › SDK and API › Load the models

The five ways to load the face and speech models (no preparing, the previous screen, speech after consent, warming the cache, several sessions with keepPrepared), when to choose each one, their tested code and how your own sessions in this tab loaded. It loads nothing.

### Your integration

#### Your integration › Protocols

The protocols of your organization, read from the catalogue, each with its Protocol view and its Kit. Which indicators you receive is in each protocol's Protocol view, in «Indicators you receive in this context».

**What it has**

- A list with a filter, Baseline first, and the protocols whose context is not resolved at the end.
- Two views per protocol: Protocol (positions, availability, steps) and Kit.
- In the Protocol view, «Indicators you receive in this context»: the list of indicators your context gives you, the ones you receive out of the public ones.

**If something is missing**

- Without a team there is nothing to show.
- If your team has no active key the protocols are read only and have no kit.

#### Your integration › Protocols › Kit

Open Your integration › Protocols, choose the protocol in the list and press Kit: that protocol's files to copy or download, and the starters.

**What it has**

- One tab per file: neuro.config.json, .env.example, .npmrc, KIT.md and AGENTS.md. Each has a Copy button and an icon button, Download the file; a file whose name starts with a dot is saved without it, and a notice says what to rename it to.
- A side column with what is pending, what is optional and the ways to integrate (SDK recommended, HTTP API complementary). Role and audiences appear only for protocols that are interpreted; one that only measures says so.
- Under the ways, Versions: the versions of @neurologyca/capture and @neurologyca/capture-server the kit is made for, with the command npm ls @neurologyca/capture @neurologyca/capture-server and Copy, and the changelog. For 30 days after a version is published its row says New (compatible: the npm i command and what changes) or Breaking (a version of those days, up to the kit's, is incompatible: the migration guide). DevLab does not see the project, so it cannot say which version the person has installed. KIT.md says the same versions under its DevLab line.
- Starters at the bottom: an on-device one and a recording one (Preview), each a .zip, with an Include my key option that asks for your password. Without the processing service in your organization, the recording card says that starter will not start.
- KIT.md, in the kit and in the starters, carries no list of indicators, only a link to Your integration › Protocols, where the list of your context is.

**If something is missing**

- Baseline has no kit: it comes before any protocol.
- A protocol whose context is not resolved has no kit either.
- Without an active key for your team there is no kit.
- The list of indicators is not in the kit: it is read in Your integration › Protocols, on the protocol.

#### Your integration › Status

How far your integration has got.

**What it has**

- Developer: the milestones of your team, the next step, and the counts of users, users with Baseline and users enrolled, with an Update button. A chip tells you when your key is no longer active in Engine.
- Organization admin: a table by team with the last activity and the key with its expiry, a notice about the other keys of the organization, and the People section below it.
- To check when your key expires, use Check in Your account and API key › Engine keys.

**If something is missing**

- Without a team there is no status to show.
- Without an active key only the milestones DevLab already had are shown; nothing is checked in Engine.
- Only the organization admin sees People.

### Your account and API key

#### Your account and API key

Your profile and the Engine keys you can see.

**What it has**

- Profile: your email, role, organization and team, with links to Your integration and to the documentation.
- Engine keys.
- Deferred processing, when it is available.

**If something is missing**

- Without a team the page says your account has no team yet and there is no key to see.

#### Your account and API key › Engine keys

The keys of your team, never shown in full until you ask.

**What it has**

- A table with team, key (a hint only), rotation date and expiry.
- Reveal shows the key in a dialog after you type your password: 5 per hour, failed attempts included, and it is recorded.
- Check, on each row, asks Engine for the expiry date and warns when the key expires soon or has expired.
- The organization admin sees the keys of all the active teams of the organization.

**If something is missing**

- Without a team there is no key to see.
- If your team was revoked or has no key, the page shows a notice and no Reveal for your team. An organization admin still sees Reveal for the other active teams.

#### Your account and API key › Deferred processing

The hosted service that processes your recordings and tells your backend with a signed webhook (Preview). It needs an active team key and a DevLab that offers it.

**What it has**

- For everyone: the address of the service and the outbound IP of the processor, each with Copy.
- The organization admin team also manages the processor key and the webhook secret: Reveal, Generate new values, Activate and Discard.

**If something is missing**

- The section appears only when your team has an active key and this DevLab offers hosted processing.
- If you are not on the admin team, the section only shows the address and the IP: download the key and the secret in your own recording starter with Include my key and the processor credentials (Your integration › Protocols › Kit).

#### Your account and API key › My agreements

The DevLab Terms you have accepted, each version with its date and the exact documents you accepted.

**What it has**

- A table with version, date and time (UTC), how you accepted (activation, a new version…) and links to the documents in the version you accepted.
- The organization admin also sees what the organization accepted, including a signed agreement recorded by Neurologyca.
- All the documents and their previous versions are public at /legal, without signing in.

**If something is missing**

- If your organization has not accepted the terms, Your account and Your integration show a notice, and Reveal and Include my key are disabled until it does.

### What's new

#### What's new

What changed in DevLab, in the versions published so far.

**What it has**

- Also reachable from the account menu.

## For organization admins

You are in your organization's admin team.

An organization admin sees everything a developer sees, plus:

### Your integration

#### Invite person

Opens the dialog to invite a developer to one of your teams.

**What it has**

- The email, the team and the language of the email.
- The person joins as a developer of that team and gets an activation link.
- The same button is in the header of Protocols and Status (when inviting is enabled), in the People section of Status and in the account menu.

**If something is missing**

- Only the organization admin can invite.
- Inviting is off when the admin team has no active key or when this DevLab does not send email.

## Your profile

In **Your account and API key**, the **Profile** shows your email, your role, your organization and your team (a chip says **Organization admin** when you are one). DevLab has no screen to change your email or your name: ask Neurologyca. Your password changes only with **Forgot it?** on the sign-in page ([Your DevLab account](/docs/access/account/#forgot-your-password)).

## The pages before you sign in

- **Sign in**: your email and password, **Forgot it?**, and "to continue to…" when you came from a page that needs a session.
- **Activate your account**: the page the invitation link opens. Choose a password and accept the DevLab Terms ([Terms and your agreements](/docs/access/account/#terms-and-your-agreements)).
- **Reset password**: the page the reset link opens.
- **Unsubscribe**: the link at the end of the DevLab news email. It asks you to confirm, and it only stops the emails: you keep seeing **What's new** inside DevLab.

## Which message tells you what is missing

| You see | What it means | Where it is explained |
| --- | --- | --- |
| "Your account has no team yet" | Your account is not assigned to a team | Ask who invited you; [Access model](/docs/access/model/#errors-from-devlab) |
| "Your team has no active Engine key" and your team shown as **Revoked** | The key was revoked or never created | [Your DevLab account](/docs/access/account/#reveal-your-teams-key) and [Keys](/docs/access/keys/) |
| Protocols "read only" | Same cause: you can read your protocols, but there is no kit | [Your kit](/docs/access/kit/#where-to-find-it) |
| "Baseline has no kit" | Baseline comes before any protocol | [Your kit](/docs/access/kit/#where-to-find-it) |
| "Not signed in: nothing is measured or stored" or "No team: nothing is measured or stored" | The playground shows the recorded example only | [The playground](/docs/start/testing/#the-playground-in-devlab) |
| "Inviting is unavailable: this DevLab does not send email" | Nobody can be invited here | [Your DevLab account](/docs/access/account/#invite-developers-organization-admin) |
