Linkr
Home Resources Tools Documentation Blog Demo
FR
  • What is Linkr?
  • Deployment modes
  • Quick start
  • Local install
  • With Docker
  • Manual install
  • Client-only
  • Your first project
  • Workspaces and projects
  • The data pipeline
  • Entities and sharing
  • Versioning and collaboration
  • Overview
  • Projects
  • Wiki
  • Plugins
  • Members and roles
  • Settings
  • Schemas
  • Databases
  • Derived sub-databases
  • Data quality
  • Data catalog
  • SQL script collections
  • ETL pipelines
  • Overview
  • Mapping projects
  • Global view
  • Target concepts
  • Mapping editor
  • Suggestions
  • Evaluation
  • Export
  • Overview
  • Concepts
  • Cohorts
  • Patient data
  • Pipeline
  • Datasets
  • IDE
  • Web apps
  • Versioning
  • Overview
  • Tabs and widgets
  • Built-in widgets
  • Analysis widgets
  • Control charts (SPC)
  • Surveys and eCRF
  • R and Python code
  • Filters, settings and export
  • Overview
  • Presentation mode
  • Exporting a report
  • Agents
  • Model providers
  • Skills
  • Authoring through MCP
  • Import and export
  • Git versioning
  • Community catalog
  • Publishing content
  • Production install
  • Configuration
  • Authentication and permissions
  • Files on the server
  • Backup and restore
  • Glossary
  • Keyboard shortcuts
  • Release notes
Documentation Workspace Settings

Settings

A workspace's settings: identity, members, badges, default environments, AI assistant and deletion.

Summary

Workspace settings gather what applies across all its projects: its identity and organization, its members, the badges used to file projects, the default environments every new project inherits, and the approved language model. Only an owner gets in.

Client Available in client-only mode — runs entirely in the browser, no backend. Backend Available with the FastAPI backend.

General

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.

This is also where the git repository the workspace is linked to is configured.

Members

Who gets into the workspace and with which role. The subject has its own page: Members and roles.

Badges

Badges label projects — a domain, a unit, a funding source — to keep things findable as they multiply.

Here you declare the badge categories, that is, the filing axes that make sense in your setting. Each project then picks from them.

Default environments

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. A project remains free to diverge from it afterwards.

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.

AI assistant

The language model available in this workspace, and the uses it is approved for. A Tests tab lets you check that a model answers properly before making it available.

The subject, with its confidentiality implications, is covered in Model providers.

Delete workspace

The last tab, 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.
PreviousMembers and rolesNextSchemas

Product

  • Home
  • Demo

Resources

  • Documentation
  • Resources
  • Tools
  • Blog

Community

  • Framagit source code
  • Github source code

About

  • InterHop.org
  • Contact

2021–2026 InterHop — CC BY-NC-SA 4.0 (site) · GPLv3 (software)