Browse articles

Adding an office

Split project ownership across studios or businesses without splitting the firm into separate workspaces. Create entities, assign projects to them, and know which entity a new project lands in by default.

What you'll achieve

Turn on entities so projects can be organised by studio or business instead of firm-wide, without disturbing anything for a firm that only ever needs one.

You'll end up with: One or more active entities, with projects assigned to the right one and new projects defaulting sensibly.

Before you start

One entity until you say otherwise

An entity is a part of your firm that owns its own projects. It can be an office, a studio or a separate business. Every organisation in Monument already has an entity, whether you've ever looked at one or not. It's created automatically the moment the organisation exists, and every project you've ever made already belongs to it. For a firm working out of a single location, that's the whole story: nothing about entities shows up anywhere, because there's nothing to choose between yet.

Entities exist to answer one question: which studio or business does this project, invoice or report actually belong to? A firm with one entity already knows the answer without asking, so Monument doesn't ask. The entity picker on a project, the option to run a separate invoice sequence per entity, the ability to connect a second accounting system, all of it stays out of sight until you create a second entity. The single exception is the Entities page itself in Settings, which is always there, waiting for the day the firm outgrows one address.

Northlight Architects has been running Melbourne and Sydney studios out of one Monument workspace for a while, tagging projects and people Melbourne Office and Sydney Office to tell them apart in reports. Entities give the same practice a proper home for that split: a real record a project belongs to, not a label someone has to remember to type.

Create the second entity

  1. 1

    Open Settings and choose Entities, under Practice.

  2. 2

    Click New entity.

  3. 3

    Enter a Name (Sydney Office) and an optional Code, a short identifier that shows up on reports.

  4. 4

    Click Create entity to save it.

That's the entire setup step. As soon as a second active entity exists, the entity picker on a project, the per-entity invoice sequence toggle, and the per-entity accounting connection list all appear on their own, everywhere they're relevant.

Assign a project to its entity

Once a second entity exists, every project gets an Entity field in its Brief, in the Cover section: which entity is responsible for this project. It's a plain picker, no typing, listing every active entity in the firm.

  1. 1

    Open the project's page, click Brief, then the Cover section.

  2. 2

    Open the Entity field and pick Sydney Office.

  3. 3

    Click Save. The project now belongs to Sydney rather than the firm's default.

A project always belongs to some entity, from the moment it's created, whether you set one or not. Build a project from scratch without picking an entity, and Monument reaches for your own home entity first, the one set on your Profile, before falling back to the organisation's default entity, the oldest still-active one, the same one that quietly held every project before you added entities at all. Build a project from a template instead, and the template's own entity takes priority over yours: it inherits whichever entity the template project itself belongs to, so a firm that keeps a Sydney-flavoured template automatically hands Sydney's new work to Sydney no matter who's creating it, only reaching for the creator's home entity, then the organisation default, if the template itself has no entity.

Archive an entity, don't delete it

There's no Delete for an entity, only Archive. Archiving takes an entity out of the running for new work, new projects can't be assigned to it and it drops out of the picker, while everything already stamped with it, past projects, past invoices, keeps its history intact. Restoring an archived entity brings it straight back into circulation.

  1. 1

    In Settings › Entities, find the entity you want to retire.

  2. 2

    Open the cog at the end of its row and choose Archive. An Archived badge appears beside its name.

  3. 3

    To bring it back later, open the same cog and choose Restore. The Archived badge goes.

Troubleshooting

  • The Entity field isn't showing up on a project. It only appears once a second active entity exists. With just the one default entity, there's nothing to pick between, so Monument doesn't show the field at all.
  • Can't archive an entity. If it's the only active one left, its cog leaves out Archive on purpose. Create or restore another entity first, then archive this one.
  • A project shows "Not set" for its entity even though entities exist. That project predates the entity it should have, or was created without an explicit pick and the resolved default hasn't been set on it. Open its Brief, then the Cover section, and assign one directly.

Where this fits next

An entity on its own is just a name a project points to. Give it real substance next: Office billing details covers its legal name, ABN and logo, and how invoices remember the entity they were raised under. Projects aren't the only thing that can belong to an entity, give your people a home entity too, so new projects default sensibly and reports can split by studio. Once that's set up, break reports and accounting down by entity shows how the same split reaches reporting and your accounting connection.

Search Monument help

Search help articles and open a result.