> For the complete documentation index, see [llms.txt](https://help.resouris.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.resouris.com/set-up-what-you-schedule/manage-spaces.md).

# Spaces — the catalogue

**Organisation → Spaces**

Every place work happens, scoped to a roster area. Rooms, bays, wards, and the channels that are not places at all.

## Why "spaces" and not "rooms"

Because not all of them are rooms, and a catalogue that calls them all rooms cannot describe a department that runs a ward round or reports from home.

A space is anything a session can be scheduled into. The catalogue holds all of them together, and each one carries its own word.

## The three columns that matter

### Name

What this particular space is called. *Echo 1*. *Cath Lab 2*. *Working @ Home*.

### Type — the department's own word

Free text, and yours. *Cath lab*, *Bay*, *Ward*, *Reporting room*, *Ward round*.

Underneath, every space has a **category** from a fixed set — `room`, `bay`, `ward`, `channel` — which is what the scheduler reasons about when it works out that two sessions cannot occupy the same place at once. The type name sits on top of that and changes nothing about the scheduling; it changes what people read.

**Leave it empty and the space uses its category's word.** An unnamed room shows "Room", an unnamed channel shows "Channel". The label is never blank, and clearing the box puts the fallback back rather than leaving nothing.

This matters more than it sounds. Ticking eligible spaces for a service line against a list of codes — `echo1`, `echo2`, … `echo7` — asks you to remember which one is the stress lab. Against a list that says *Stress lab*, you do not have to.

### Assignment

**Trust-assigned** — reliably available to this department. **Ad-hoc** — borrowed, shared, or available only sometimes.

## Where a space sits in the estate

The Spaces catalogue is a flat list scoped by roster area. To see or change where a space physically sits — which floor of which building on which site — use [Estate](/how-it-works/the-estate.md).

The two pages show the same 22 spaces arranged differently: Spaces answers *"what do we have?"*, Estate answers *"where is it?"*.

## Add a space

**Organisation → Spaces → + Add space**

| Field               | Notes                                                         |
| ------------------- | ------------------------------------------------------------- |
| Name                | what people call this particular space                        |
| Space ID            | the immutable join key; lowercase, digits, underscore         |
| Space type          | physical or virtual                                           |
| What this is called | the free-text type name — optional                            |
| Target roster       | primary, secondary (out of hours), or tertiary                |
| Capacity            | how many concurrent sessions; 0 means unlimited, virtual only |

The Space ID cannot be changed afterwards, because rosters, sessions and fixed commitments all reference it. The name can be changed whenever you like.

## Import many at once

**Organisation → Spaces → Import (CSV)**

Headers: `roster_area_code` and `code` are required; `name`, `space_type`, `description` and `capacity` are optional.

Rows whose `code` already exists for that roster area are **skipped, not overwritten**, and the summary tells you how many. If you meant to change existing spaces, edit them — an import that silently overwrote your catalogue would be a bad way to find out.

## Make a space eligible for a service line

A space is not usable by a service line until the two are mapped, and until then the scheduler will never pick it. The Spaces list flags any space with no service lines as **Unmapped**.

Map them from **Organisation → Services → \[the service line] → Spaces**, which lists every space in that roster area with its type name — so you are ticking *Stress lab* rather than `echo1`.

## Archive rather than delete

Archiving keeps the space in the catalogue and out of the scheduler. Service lines can keep their eligibility tick, and history still reconstructs.

Deleting is refused outright if the space is referenced by a roster or a fixed commitment. That is not an obstacle to work around — a deleted space would orphan the record of work that genuinely happened in it.

## Related

* [The estate](/how-it-works/the-estate.md) — where each space physically sits
* [Create a service line](/set-up-what-you-schedule/create-a-service-line.md)
* [Space and service-line scheduling](/set-up-what-you-schedule/room-sl-schedule.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.resouris.com/set-up-what-you-schedule/manage-spaces.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.