Publication

Spaces, rooms, and access rights in Matrix: the company’s communication structure

How to organize Matrix spaces by departments and projects, configure rooms and roles, separate private and open discussions, and manage the lifecycle through to the archive.

Messenger 3 min
Infographic of the structure of spaces, rooms, and access rights in Matrix

When a messenger on Matrix and Element is launched without structure, rooms quickly turn into a chaotic list where it is hard to find the right discussion and understand who has access to it.

Spaces, rooms, and roles let you lay in the communication structure in advance: by departments and projects, separating private and open discussions, with a clear lifecycle through to the archive.

Communication structure

How to organize spaces and access

  1. 01Spaces
  2. 02Rooms
  3. 03Roles and rights
  4. 04Archive
  • Spaces group rooms by departments and projects
  • Private and open rooms are separated in advance
  • A room lifecycle ends in an archive, not deletion

Spaces as the framework

Spaces are containers that group rooms by meaning: a separate space for a department, project, or area. An employee immediately sees where their work discussions are rather than searching for them in a general list.

A good space structure reflects the company’s real organization. If it has sales, production, and support, it makes sense to lay in separate spaces and, within them, topic-based rooms.

  • a space for a department
  • a space for a project
  • company-wide rooms
  • separate spaces for contractors

Private and open rooms

Rooms can be open to all employees or private, with only the needed participants added. It is better to set this split at the start rather than sort it out later, once a confidential discussion has ended up in the open.

Privacy in Matrix is complemented by E2EE, which encrypts the content of messages. Remember that encryption closes off the content but not all the metadata, so access rules are still needed.

Roles and access rights

Roles define who can invite participants, change room settings, and moderate the discussion. The basic split into administrator, moderator, and participant covers most working scenarios.

Rights should be granted on the principle of least necessity: the fewer people who can change critical settings, the more stable the structure. This matters especially in spaces with external participants.

The room lifecycle

Projects end, and rooms should not hang around forever. Controlling the lifecycle means a room has a clear ending: important discussions go to the archive, and the room itself is moved to an archived state.

KMVSG helps design spaces, roles, and an archiving procedure for a specific company’s structure, so communications stay manageable as the team grows.

Quick checklist

  • Describe spaces by departments and projects
  • Separate private and open rooms
  • Assign roles on the principle of least privilege
  • Define what goes to the archive
  • Set the room archiving procedure

What to do next

KMVSG designs spaces, rooms, and roles in Matrix for your company’s structure and helps build a clear discussion lifecycle.

Discuss your task