Your DevLab account
Invitation, sign-in, sessions, revealing your team's key, and what DevLab records about you.
Accounts are by invitation
Section titled “Accounts are by invitation”Neurologyca, or your organization admin, invites you to a team; there is no self sign-up. The email link works once and expires in 72 hours. A new invitation replaces the previous one; if yours expired, ask for another (your organization admin can resend it).
To activate the account, choose a password of 12 to 200 characters and accept the DevLab Terms (Terms and your agreements). Activating signs out any other session of the account.
Invite developers (organization admin)
Section titled “Invite developers (organization admin)”If you are the organization admin, Your integration → Status lists the people of your organization under People, and Invite person invites someone as a developer of one of your active teams. You also have Invite person at the top of Your integration (in both views) and Invite person in your account menu (the avatar in the header); all three open the same dialog. They get an activation link by email (72 hours, single use) and, once active, see that team’s key.
- You choose the email, the team and the email’s language. The role is always developer: you cannot invite another organization admin, and you cannot invite to a revoked team.
- Resend sends a new link to a pending invitation and cancels the previous one, even one Neurologyca sent.
- Limits: 20 invitations a day per organization; 5 resends an hour per invitation and 20 a day per organization.
- An email that already has an account in your organization is reported (active, or pending with Resend it; a pending invitation in a revoked team, without it). For any other email the answer is always Invitation sent: “if the email is valid, they get an activation link”. DevLab never says whether an email has an account outside your organization, and in that case it sends nothing.
- DevLab never shows the activation link. If the email did not go out (or has not gone out after 10 minutes), the row says so (the email did not go out · Resend). A DevLab that does not send email cannot invite.
- To remove someone or move them to another team, ask Neurologyca. Every invitation and resend is recorded in the activity that Neurologyca sees.
Sign in and sessions
Section titled “Sign in and sessions”- Sign in with your email and password. After too many failed attempts, sign-in pauses for up to 15 minutes.
- A session lasts 7 days without activity, and 30 days at most. Sign out, in your account menu, ends it.
- Resetting your password, or Neurologyca disabling your account, signs you out everywhere.
- If you open a DevLab page without a session, signing in takes you back to that page; otherwise you land on this documentation, in your language (a Neurologyca admin, on the admin panel). With a session already open, the sign-in page takes you to that destination instead of showing the form.
- To sign in with another account, sign out first. Activating an account or resetting a password in this browser closes the session it had open: then you sign in with the new password.
Forgot your password
Section titled “Forgot your password”Use Forgot it?, next to the password field on the sign-in page. The link works once and expires in 1 hour. There is no other way to change your password today.
Reveal your team’s key
Section titled “Reveal your team’s key”In Your account, under Engine keys, choose Reveal and enter your password.
- Up to 5 reveals per hour per account; attempts with a wrong password count. The quota is shared with the deferred processing credentials and with Include my key and the processor credentials, the starter zip download: a download with your keys counts as a reveal, and so does a failed one.
- Every reveal is recorded. If DevLab cannot record it, it does not show the key.
- The key appears only in that dialog. Copy it into your backend’s secrets and press Done; you can reveal it again later with your password.
- Your team shares this key: anyone in the team can reveal it.
- While the admin team is active, an organization admin sees and can reveal every active key of the organization, including the admin key (scope
admin); if the admin team is revoked, they see only their own team, as revoked, with nothing to reveal. Ask Neurologyca to rotate or revoke any of these keys: changing them outside DevLab leaves DevLab with an old copy. - If your team has no active key, Your account says so and shows your team as revoked (or without a key), with nothing to reveal. If you are the organization admin and only the admin team lacks a key, you still see and can reveal the active keys of the other teams (without Check).
Deferred processing credentials
Section titled “Deferred processing credentials”Deferred processing is on for a new organization unless Neurologyca turned it off when creating it; Neurologyca turns it on or off. Your account has a Deferred processing section (Preview). Everyone with an active team sees the service URL and its egress IP, to copy. Limit your three routes to that IP as defense in depth: the IP does not authenticate. Verifying the signature is mandatory, and the SDK does it for you. See Deferred processing.
The processor key and the webhook secret are your organization’s, one pair shared by every team, and only your organization’s admin team manages them (reveal, rotate, activate). A member of any active team gets the current pair in their own recording starter with Include my key and the processor credentials, next to their own Engine key, so nobody needs the admin team’s zip, which carries the admin key. Neurologyca does not reveal them either: if your organization runs out of people in its admin team, Neurologyca invites someone to it.
- Reveal shows the key and the secret together, after your password. It counts against the same 5 reveals per hour as the Engine keys and Include my key and the processor credentials, failed attempts included, and it is recorded; if DevLab cannot record it, it does not show them.
- Generate new values is step 1 of the rotation: choose the key, the secret or both, enter your password (it counts as a reveal) and copy the new values. They stay pending: the service keeps accepting the current ones.
- Activate is step 2: deploy the new values in your backend first, then type your organization’s name to confirm. DevLab sends them to the service and the section says “Sending the new values to the service…” until the service confirms them. If you rotate the secret and there are recordings in progress (or DevLab cannot tell), it asks you to confirm again: their notices will be signed with the new secret. Rotating only the key has no such risk.
- Discard deletes the pending values; they never reached the service.
- If the new values do not reach the service, the section says so: the service keeps accepting the previous ones and Neurologyca retries. If your backend already uses the new ones, go back to the previous ones until the section says the values are active.
While deferred processing is turned off for your organization, the section says so and the service rejects what your backend sends; your organization’s admin team can still reveal, rotate and discard, and the new values are used when Neurologyca turns it back on. Your teams can’t record in Deferred in the DevLab playground either: in an environment with deferred processing, Deferred says your organization does not have it turned on (in one without it, Deferred shows its usual Preview with the recorded example). If a credential leaks, follow the procedure in Keys.
In the kit, the recording starter carries the service URL and IP in its .env. With Include my key and the processor credentials, any active team also gets the processor key and the webhook secret (the current ones, never the pending ones); when they cannot be included (the service is not set up yet, or it is turned off), those two lines come empty, with the reason. Every recording zip carries a new random UPLOAD_URL_SECRET, which DevLab neither keeps nor records: downloading the zip again changes it, and the video URLs already signed with the previous one stop working.
Your integration
Section titled “Your integration”Under Your integration, DevLab shows your organization in two views. Protocols lists its contexts, their published protocols and Baseline, which comes before any protocol; choose a protocol to open it in the viewer, with its positions, when each one is available and its steps. DevLab reads all of it from Engine with your team’s key, on the server, without creating users: the key never reaches your browser. Each view has its own address, so you can bookmark it or share it with your team.
Each protocol also shows Indicators you receive in this context: the public indicators your context gives you (the same for every protocol of that context), either the whole public catalogue or how many of them you receive; then the ones Available by agreement, which you can ask Neurologyca for, and the four that need previous sessions, which do not depend on your agreement (not in Measurement, which is not interpreted). It always ends with two lines: the payload can carry more undocumented keys, which you should not build on, and “This list can change with your organization’s agreement; treat every indicator as optional.”, with how to prepare. With your team revoked it is shown too, read only. KIT.md and the starters link to it, without the list. What each indicator is: HCIs and results.
Kit, next to Protocol at the top of a protocol, gives you its kit: neuro.config.json, .env.example, .npmrc, a KIT.md guide and AGENTS.md, the rules and the docs index for your coding agent (the same block as Build with your coding agent), each in its tab, ready to copy or download. KIT.md opens with a DevLab: line that names the DevLab the kit comes from, and links the docs with full URLs. The starter zips carry the same KIT.md and AGENTS.md. Baseline, and a protocol whose context DevLab cannot resolve, have no kit. It already includes the decisions Neurologyca sets for your organization (the subcontext of each mechanic, the role and the audiences); what is still missing appears as pending, with “Ask Neurologyca”. A subcontext, a target HCI or a role that is not set appears as optional instead: you can capture without it. Without a subcontext Engine applies the mechanic’s own, constellationSubcontextId, or else the default subcontext of the context; a context with no subcontexts to choose from shows none. The role has no effect today: it will have one later. If you set one, it must be one of the roles Engine accepts (agree it with Neurologyca): with any other, Engine rejects creating the user with a 400 (E_ROLE_UNKNOWN in @neurologyca/capture-server). The kit always lists the interpretation audiences of the protocol’s context, each with its scope (the whole context, a target HCI or a situation), and so does its KIT.md: send one as audience in POST /analyze. The ones Neurologyca sets for your organization appear apart; a context with none says so. A protocol without interpretation (like Measurement) also has its neuro.config.json, with triggerAnalysis: false: its kit says it only measures. The kit never holds your key: its key variable comes empty, and you reveal the key in this account. Every file, variable and key of the kit, where to find it and how to run a starter are in Your kit; every screen, by role, is in Where everything is.
Status answers “is my integration working?”. It lists your team’s seven milestones in integration order (first call, first user created, first enrolment, first capture sent, first position captured, first interpretation and first use of the key outside DevLab), each with the date of the first time or pending; the first pending one is your next step, with the page of the docs that explains it (and the playground for the first call). A team whose protocols are all without interpretation (like Measurement) has six: the first interpretation does not apply. Below, how many users your team has created and how many have Baseline and an enrolment, with the time of the check and Update; if Engine no longer has your key active, it says so. The milestones count what you do from DevLab (reference, playground) and DevLab’s own checks; “first position captured” is checked in Engine, and the first use Outside DevLab (your backend or any other tool with the key) is a use of your key more than 5 seconds after a DevLab check. Counts are recalculated every minute and stop at 500 users (“500+”); if DevLab cannot check every user in time it says so and you can update. When your key expires you check in this account (Check). An organization admin sees, instead, only the activity of the whole organization, one row per team and longest inactive first: its last activity (the latest of its milestones and the last use of its key, in calendar days; when that last use is the latest, whether it came from DevLab or from outside) and its key (“Expires …”, with a warning 30 days before, or that it is no longer active in Engine). The admin key does not count, because DevLab reads this status with it, and the admin team only appears when it has activity of its own; the keys that are not from DevLab appear only as totals. If your team has no active key, you see a notice, the milestones DevLab already had (without checking Engine) and, when DevLab can read them, your organization’s protocols in read-only mode (“Your organization’s protocols, read only”): you can open each one in the viewer, but there is no kit until your team has a key again.
Profile, language, theme and news
Section titled “Profile, language, theme and news”- Profile. Your account opens with your Profile: email, role, organization and team (a chip says Organization admin when you are). DevLab has no screen to change your email or your name: ask Neurologyca. Your password changes only with Forgot it? (above).
- Language. The Language menu in the header switches the interface and the documentation between English and Español. DevLab remembers the choice you make in your browser.
- Theme. The Theme button in the header rotates Auto (your system’s), Light and Dark, and remembers it in your browser.
- What’s new. What’s new, in the account menu, lists what changed in DevLab. Neurologyca may also email an update, in English, to the people it chooses. The email ends with Unsubscribe from these updates: the page that opens asks you to confirm and only stops those emails; you keep seeing What’s new inside DevLab. Neurologyca can restore an address that unsubscribed.
Terms and your agreements
Section titled “Terms and your agreements”To use DevLab, the Engine API and the SDKs you accept the DevLab Terms: the Terms of Service and the documents they incorporate (the Acceptable Use Policy, the Preview Terms, the Biometric and Emotion-Inference Addendum, the SDK License and the Agent Skills License). The Privacy Notice is for you to read; you do not accept it. Every document, with its previous versions, is public at /legal, without signing in.
- When. You accept them when you activate your account; an account that was already active is asked once, in a dialog, the next time it signs in. The boxes start unticked, and Not now, sign out signs you out without accepting.
- Your organization. Your organization admin accepts them for themselves and on behalf of your organization, including the Data Processing Addendum. Until your organization has accepted the current version, its developers cannot reveal keys or call Engine from DevLab: Your account and Your integration say so and Reveal is disabled. If your organization signed an agreement with Neurologyca instead, Neurologyca records it and the effect is the same.
- A new version. When the terms change, DevLab first shows a banner with the date, See the changes (the new version of the document that changes, in /legal) and Accept now; on that date it asks you to accept the new version before you go on, with a summary of what changes.
- My agreements. Your account › My agreements lists every version you accepted, with its date and time (UTC), how you accepted it and links to the exact documents of that version; the organization admin also sees what the organization accepted. DevLab emails you a copy each time you accept.
What DevLab records
Section titled “What DevLab records”DevLab records your activity (sign-ins, key reveals, management actions and your team’s integration milestones) and, for sign-in, activation and password reset, and for key reveals, the IP address you used (key reveals include the deferred processing credentials). It keeps it for 12 months, to support you and for security. Your team’s milestones stay, but after 12 months they no longer record who triggered them.
DevLab keeps a record of each acceptance of the terms (your email and account, your team and organization, your role, the capacity in which you accepted, the version, a fingerprint of each document and of the text of the boxes, the language, the time, and your IP address and browser). It cannot be edited, it is kept for the life of the account and 10 years after it closes, and the IP address and browser are cleared after 12 months (Privacy Notice).
DevLab’s activity log never contains request bodies, keys or your end users’ data. To apply the per-team limits inside DevLab, DevLab keeps the identifiers (externalId, enrolment and interruption ids) of the end users your team reaches through DevLab, for 24 hours after it last checked them with Engine.
If you use the playground, DevLab also records that you accepted its consent (version, language and a hash of the text), kept 12 months like the rest of your activity; after that, the playground asks for it again. The test people it creates on your team’s organization are deleted in Engine after 24 hours, or when you or your organization admin press Delete now (your organization admin is first asked to confirm, with your team named); DevLab then keeps each run only as a count, without ids. So that you can go back to any session of the last 24 hours, DevLab’s server also keeps a few closed metadata for each session you measure: when it was enrolled, the audience it was enrolled with and the one Engine applied, the way (SDK or HTTP API), whether it was live or deferred and the state of its deferred job, and how it ended (whether the interpretation arrived, the number of steps, the duration and the state of the baseline). Only fixed values and numbers, never text or the transcript; they are deleted with the test person: after 24 hours, with Delete now or, if deleting it in Engine fails, when a retry succeeds.
If you use the assistant, DevLab records that you accepted its notice (with its version; accepting the DevLab Terms counts as accepting it, because the Privacy Notice they link covers the assistant) and, for each question, that you asked, when, from which page and in which language, which docs pages the answer cited, whether it answered from the docs, which destination it proposed, if any, whether something was removed, how it ended, the model and how much work it took (rounds, characters read, timings, tokens and an estimated cost) and your rating with its reason (from a fixed list), never the text, kept for 12 months like the rest of your activity. Your questions, the latest turns of the conversation, the language of the answer, the page you ask from and the docs pages it reads to answer go to Google, and DevLab cannot delete what has already been sent. Of a docs page, its text goes; of a DevLab screen, its name and, if «Where everything is» describes it, that description; you can remove the page before asking. With each question, DevLab also sends your role (developer, organization admin or Neurologyca admin), the state of your team (no team, inactive or active) and whether this DevLab offers invitations and hosted processing: values with no names or identifiers, so that the answer fits your situation. More in Privacy and data.
To delete your account, contact Neurologyca. Your activity becomes anonymous; the end users you created in Engine stay in your organization.