Skip to main content
A workspace is the container Galagos uses to group everything a team works with: projects, shared files, Skills, members, billing, and audit history. Every account starts with a personal workspace for solo work. When you need to share with a lab, a department, or external collaborators, you create a team workspace and invite people in.

Personal vs team workspaces

Personal workspace

The default workspace on every Galagos account. Your projects, files, and Skills live here. Suitable for solo research, exploration, and any work you don’t need to share.

Team workspace

Created deliberately when you want to share projects with named collaborators. Every member sees the same projects, the same library, the same Skills, and the same audit trail.
Don’t create a team workspace for solo work. The single-member overhead — roles, audit, member tab — adds friction without benefit. Use your personal workspace until you actually need to share.

The nine workspace tabs

Every workspace surfaces the same nine tabs in the left sidebar. They are the same for personal and team workspaces, although a few only become useful once you invite people in.
The list of project sandboxes that belong to the workspace. Each card shows the project name, role, last activity, and chat count. Use the table view at the workspace level to rename, share, move between workspaces, or delete projects.
A workspace-wide file bucket for assets that more than one project needs: reference genomes, panel BED files, gene lists, sample sheets. Upload once at the workspace level; pull a file into any project with a single click, by asking the agent, or push a result back from a project the same way. Full walkthrough in Workspace library.Seed the library before you invite anyone. The first thing a new teammate does is open a project and look for the lab’s reference files.
Invite people, change roles, and remove access. One invitation gives access to all projects in the workspace, the library, and the Skills set — there is no per-project invite step.Three roles are supported:
  • Owner — manages the workspace, billing, and seats.
  • Admin — invites members, configures Skills, library, and endpoints.
  • Member — uses the platform: creates projects, runs analyses, attaches Skills.
An optional tab for teams that need to route inference through their own LLM provider — most often for compliance or to keep activity inside an existing approved vendor. Most teams skip this tab entirely. For setup details, see Bring Your Own LLM.
Workspace-level Skills configuration. Two switches change how members interact with each Skill:
  • Pinned — the Skill becomes a default for new sessions in the workspace. New projects start with it enabled.
  • Required — members cannot turn the Skill off. Useful for QC thresholds, privacy policy guardrails, or citation conventions you want enforced across every project.
Pin two or three Skills, not twenty. Members can always attach more from the catalogue inside a project.
A full record of workspace actions — workspace and project creation, member invites and role changes, library uploads, Skill pinning, endpoint configuration. Each entry shows the actor, the action, and the timestamp. You can filter by event type and export to CSV. Owners see the log by default; admins can export it.Use the audit log to answer review questions like “who added that reference panel?” or “when was this Skill required?”.
A real-time view of compute spend and credit consumption across the workspace, broken down per project and over time. Use it to plan capacity, spot run-away analyses, and decide when to upgrade.
An opt-in store of long-term facts about how the team works — the strain panel you always use, the gene-symbol convention, the supplementary-table format you export. Galagos consults memory before running, so members don’t need to repeat conventions in every prompt. See Memory for details.
Workspace name, description, default access level for new members, and the default LLM model for the team. Changes apply to new sessions; in-flight work is unaffected.

Member roles in practice

A few tips

  • Seed before you invite. Upload the lab’s reference files to the library and pin two or three Skills before sending invitations. The first thing a new teammate does is look for them.
  • Use Required sparingly. Required Skills override member judgement, so reserve them for non-negotiable rules like a QC threshold or a citation policy.
  • Memory beats repeated instructions. If you find yourself typing the same caveat into every prompt (“we always use GRCh38, not T2T-CHM13”), promote it to a memory entry instead.
  • Check the audit log before review meetings. It is faster than asking around when you need to know who changed a Skill or added a panel.

Projects

How a project sandbox works inside a workspace.

Workspace library

Shared files across every project in the workspace, usable from the UI and from chat.

Skills

The catalogue and per-project Skill toggles.

Memory

Persistent facts about how the team works.

Enterprise plan

SSO, pooled credits, and dedicated infrastructure for larger teams.