Workspace profiles and editor sessions
A workspace profile decides how the code editor opens: how much memory it gets, which extensions it carries, and what settings it starts with. Both pages are under Development in the console.
It is a different thing from a workstation profile, which binds a customer instance to a local copy on a developer workstation.
Who may open an editor
Every server is installed with a Default profile, assigned to the admin account, so the
administrator can open the editor on a fresh server without configuring anything first.
Every other account needs a profile assigned before it can open the editor at all. Assignment is a column on the account, under Access in the user editor.
That is the access control for the whole feature: the editor runs inside a customer's container with a terminal in it, so who may open one is a decision somebody makes deliberately, not a side effect of being an administrator.
What a profile carries
| Setting | What it decides |
|---|---|
| Memory | The editor's memory limit, per profile rather than one figure for the server |
| Extensions | Exactly what an editor opened with this profile carries |
| Editor settings | VS Code settings, typed or uploaded, put into every editor opened on the profile |
| Reload on edit | Whether the instance reloads as files are edited |
A new profile starts from the extensions the editor already carries, so the list begins useful rather than empty. Add follows the text box as you type, and Enter adds. Validate checks the extensions and clears the previous verdicts as it goes, so what you see is this run's answer.
Duplicate opens a copy of a profile to rename and save, which is the quick way to give one team a variation of another's.
The Default profile
There is always a Default profile. It cannot be renamed and it cannot be removed, and Reset to default puts its memory, its settings and its extensions back to what the product ships. Assign it to other accounts as you would any profile.
Editor sessions
Development > Editor sessions lists every editor session on the server: who opened it, on which instance, and when.
A session outlives the browser tab that opened it, so this page is where you find the ones nobody is using. Delete one here, or use Delete this editor session on the Code tab's own panel.
They are cleaned up on a schedule
The Configuration tab sets the number of days after which a session is cleaned up. The Editor session cleanup maintenance task is on by default and runs weekly on servers where the editor is available.
That default matters: an editor session holds a copy of the editor in the instance's data directory, so sessions nobody deletes are disk that quietly disappears.