Summary
Workspace settings gather what applies across all its projects, in four tabs: its members, the badges used to file projects, the default environments every new project inherits, and deletion, reserved for the owner. The workspace’s identity — name, description, organization — is edited separately, from its menu.
Identity and git repository
These two are not tabs of the page: they open from the workspace menu, by clicking the workspace’s name at the top of the screen.
- Edit opens the Edit workspace dialog: the name, the description and the publishing organization — hospital, university, institute, consortium. The organization is not decorative: it travels with every entity exported from this workspace and acts as a signature when the work circulates. See Entities and sharing.
- Export and Versioning open the workspace’s Versioning & export page — its git repository and its ZIP archive. See Git versioning.
Members
Who gets into the workspace and with which role. The subject has its own page: Members and roles.
Badges
Badges label projects and the workspace’s other items — a domain, a unit, a funding source — to keep things findable as they multiply. A badge starts as free text; it gains a category when written Category::value, like Source::MIMIC.
Here you declare the categories, that is, the filing axes that make sense in your setting. A declared category has a colour, shows in two tones on the badges that carry it, and appears in the category picker when adding a badge.
Workspace Settings
Declare badge categories to organise the badges used across this workspace. A badge written Source::MIMIC shows its category, and an exclusive category holds only one value per element.
Click a value to put it on the project.
- Exclusive — an item can carry only one value of the category: picking another replaces the first. Useful for a single-valued axis, such as the data source.
- Renaming a category rewrites every badge that carries it, across the whole workspace — Linkr asks for confirmation first.
- Deleting a category touches no badge: they keep their label and simply stop being displayed as a category.
Default environments
This tab exists in server mode only: the backend is what installs environments. See Deployment modes.
A project running code needs libraries: pandas, ggplot2, whatever your team uses day to day.
Rather than installing them project after project, you declare here the list every new project inherits: one box for Python packages, one for R packages, one per line, with or without a version (pandas==2.1.4). Load defaults offers a common data-science set. A project remains free to diverge from it afterwards.
Below the two boxes, the install options — the PyPI index, the CRAN repository, a trusted host — are mostly for pointing at an internal mirror when the server has no Internet access.
A team decision more than a technical setting
This list implicitly states what your team works with. Keeping it short and current stops every project starting out with a cluttered environment nobody can account for.
Delete workspace
The last tab, visible to the owner only and flagged in red.
Deleting a workspace takes everything with it
Its projects, its databases, its mappings, its wiki, its plugins. The operation cannot be undone. If any of that work has value, export it or push it to a git repository first.
Going further
- Members and roles — who can do what.
- Configuration — settings for the whole instance, beyond a single workspace.
- Agents — the language model is not set in Linkr but in the chat client, LibreChat or OpenCode.