The Brain is a workspace's shared context: a description of your organization (its voice, what it does, its terminology) and a list of audience profiles, which are named descriptions of the learners you build for. A simulation can use the organization context (the description of your organization and its terminology), one audience profile, both or neither. What a simulation uses is shown as chips on the simulation, and it is added to the character's instructions during text conversations. The organization's voice is never given to a character: a character's personality and way of speaking come only from its own design.
There is no plan requirement for any of this. Two things decide what you see:
- The chips appear on every plan, in the full creation form and in the simulation editor.
- The Brain tab in Studio, where you edit the organization voice and manage audience profiles, is shown only in workspaces where devlin.ai has turned it on. It is not tied to a plan. If your Studio has no Brain tab, you cannot edit the organization voice or the list of profiles in the app, but simulations you generate from the full form can still get an audience profile, as described below.
What a simulation can use
Each simulation stores two choices:
- Whether the workspace's organization context is used. This is on only when it has been explicitly turned on for that simulation.
- Which audience profile is linked, if any. A simulation links at most one profile.
A simulation starts with neither. This is the case for a simulation started from scratch, one generated from the Studio create dialog, and one created by an AI tool over MCP. Only the full creation form sets them at creation.
Audience profiles from the creation form
The full form (the page titled Create New Simulation, described in Creating a simulation) has an optional field, Who is the learner?. When you type in it, a chip appears under the field that reads Using: followed by the first 6 words of what you typed.
If you leave the chip in place and generate the simulation:
- devlin.ai names an audience profile after the first 6 words of the field (with an ellipsis if you typed more).
- If the workspace already has a profile with that name, the simulation is linked to it (the oldest one, if several share the name), and that profile's description is the one that is used. Nothing new is saved.
- Otherwise a new profile is created, with your text as its description (up to 2,000 characters), and the simulation is linked to it.
To generate without a profile, select the × on the chip before you generate. No profile is created or linked. Leaving Who is the learner? empty has the same effect.
If the workspace's organization voice has About or Terminology filled in, the form also shows a Using: Org context chip, which is on to begin with. Leave it to turn organization context on for the new simulation, or select its × to create the simulation with it turned off. After you remove it, the chip changes to a dashed button that reads "+ Org context", which turns it back on. A workspace with neither field filled in shows no such chip, and the new simulation gets no organization context setting at all.
Creating the profile and saving these choices happens after the simulation is generated. If that step fails, the simulation is still created, without them.
The chips in the editor
Open a simulation, select the Design stage and the Simulation section. The chips are under the Learner Role field. Nothing is shown there when the simulation has no linked profile and there is nothing to offer.
- A chip that reads Using: followed by a profile's name means that profile is linked. Select its × to unlink it. The profile itself is not deleted.
- A Using: Org context chip means organization context is on for this simulation. Select its × to turn it off.
- A dashed button that reads "+ Use org context" appears when the workspace's organization voice has About or Terminology filled in and this simulation has never had the setting turned on or off. Select it to turn organization context on.
A change to a chip is saved immediately. It does not use Save Changes. If the save fails, the chip goes back to how it was.
The editor's chips can only remove a linked profile and turn organization context off, or turn it on the first time. The editor has no control for linking a profile to an existing simulation, for relinking one you removed, or for turning organization context back on after you removed its chip.
How the context reaches the character
When a learner sends a message in a text conversation, devlin.ai reads the simulation's two choices and, if either is set, loads the current organization context and the linked profile and adds a block to the character's instructions for that reply. The block is placed after the character's own description and instructions and before the learner's role. It can contain:
- The description of the organization and its preferred terminology (each only if that field is filled in), marked as background that does not change the character's personality or way of speaking. The Voice field is not included.
- The learner audience: the linked profile's name and description.
Because this is read for each reply and is not stored in the simulation:
- Editing the organization's About or Terminology, or a profile's description, changes every simulation that uses it from the next learner message, including published simulations and conversations already in progress. You do not need to save or republish those simulations.
- Removing or adding a chip takes effect from the next learner message too.
- The same happens in a text preview in the editor's Test stage.
- If loading the context fails, the conversation continues without it.
Limits of what it reaches:
- Voice conversations do not get this block. A simulation that shows a Using: chip applies it in text conversations only.
- Generating a simulation from your description does not read the organization voice or existing audience profiles. They shape the live text conversation, not the generated draft.
- Evaluation does not receive this block.
- Coaches have no such setting. This page applies to simulations only.
The Brain tab
In a workspace where the tab is on, open Studio and select Brain. The tab has several sections. This page covers Organization voice and Audience profiles. The other sections of the tab are not part of this page.
Organization voice
A workspace has one organization voice, made of three text fields: Voice, About and Terminology. Each holds up to 4,000 characters and each is optional. Fill in the fields and select Save. Saving an empty field clears it.
Simulation characters use only About and Terminology, and only in a simulation whose own Org context chip is on. Saving the organization voice does not turn that chip on for existing simulations. Voice never reaches a simulation's character.
Audience profiles
To add a profile, select Create audience. In the New audience dialog, enter a Name (required, up to 120 characters) and, optionally, a Description (up to 2,000 characters), then select Create.
- To change a profile, select the pencil icon on its row, edit it in the Edit audience dialog, and select Save.
- To delete a profile, select the trash icon on its row. The profile is deleted at once, with no confirmation.
- A profile created by the creation form carries a From wizard tag.
- The list shows the newest profile first. There is no limit on the number of profiles in a workspace.
A profile you create here is not linked to any simulation, and neither the tab nor the editor has a control for linking it. A simulation links to it only when the creation form produces exactly the same name, as described above.
Deleting a profile that a simulation uses
Deleting a profile does not change the simulations that were linked to it, but they stop using it: the audience line is no longer added to the character's instructions, and the chip no longer appears in the editor.
Who can change these
- In the app, any member of the workspace can view and save the organization voice and create, edit and delete audience profiles, when the Brain tab is shown. There is no owner or admin requirement.
- The chips on a simulation can be changed by anyone who can edit that simulation.
- The organization voice and the profiles belong to one workspace. Switching workspace shows that workspace's own.
- Saving the organization voice is rate limited for each member. Creating, editing and deleting profiles share a separate limit, also for each member. Above a limit the action fails with "Too many requests". Wait, then try again.
Copies and versions
- Duplicating a simulation copies its linked profile and its organization context setting to the copy.
- These choices are part of a simulation's saved versions, so restoring an earlier version brings back the choices that version had. See Version history, undo and restoring a version.
AI tools over MCP
An AI tool connected through the MCP server has no tool for choosing a simulation's audience profile or organization context setting, and cannot create, edit or delete audience profiles or the organization voice. These stay in the app.
Related
- Creating a simulation
- Building a simulation: character, scenario and editor
- Knowledge bases: uploading and managing documents
- Grounding simulations and coaches in a knowledge base
- Source materials: building from documents and links
- Version history, undo and restoring a version
- MCP server and AI tool connectors