Browse articles
- Getting started
- Project finances
- Billing by the hour
- Practice finances
- Grouping fees
- Budgeting project costs
- Claim an expense
- Recording revenue entries
- Recording project expenses
- Purchase orders
- Approving expenses
- Going further
- Construction cost fees
- Recurring fees
- Billing expenses
- Contingencies and discounts
- Billing progress claims
- Project templates
- Overheads
- Getting started
- Billing milestones
- Sending an invoice
- Billing logged time
- Month-end invoicing
- Fee proposal templates
- Writing a fee proposal
- Getting a proposal signed
- Link invoices that are already in Xero
- Going further
- Payments and overdue invoices
- Connect your accounting system
- Fee groups on invoices
- Tax codes and accounts
Give your people a home entity
Set a home entity on each person so new projects default sensibly, and reports can split your people, time and allocations by studio.
What you'll achieve
Set a home entity on a resource so it can drive which entity their new projects default to, and so reports can filter and group your people by studio.
You'll end up with: People with a home entity set where it matters, new projects that default to the right studio automatically, and reports that can be split by where your staff actually work from.
Before you start
A person's entity and a project's entity are two different questions
Adding an office covers the entity a project belongs to: which studio owns this job. That's not the same question as which entity a person works from, and until now Monument only let you answer the first one. A home entity answers the second: where Priya Sharma actually sits, regardless of which studio's projects she happens to be staffed on this month.
Northlight Architects runs Melbourne and Sydney studios. Priya Sharma, the Senior Architect from set your team's availability, works out of the Sydney studio. Nothing about her home entity changes her capacity or her rates; it answers a narrower question: which entity does she belong to, the same way a project's entity answers which studio a job belongs to.
Set a home entity
Like every entity-aware field in Monument, this one stays out of sight for a single-entity firm. It only shows up on a person's Profile once a second active entity exists.
- 1
Go to Team › Team members and open Priya Sharma's page. Click Profile, then the Details section. Its fields are ready to edit.
- 2
Open the Home entity field and pick Sydney Office.
- 3
Save. Priya's profile now shows Sydney Office instead of Not set.
A resource with no home entity isn't broken; it's just undeclared. Nothing stops them working on any project in any entity; it only means Monument has nothing of theirs to default from when they create a project, and nothing to group them under in a report split by studio.
What a home entity actually drives
New projects default to it
Build a project from scratch without picking an entity yourself, and Monument first reaches for your own home entity, not the organisation's default. Priya creating a project from scratch now lands it in Sydney Office automatically, without her touching the Entity field at all. Only a resource with no home entity set, or one whose home entity has since been archived, falls through to the organisation's oldest still-active entity, the same fallback that's always existed.
Building from a template still puts the template first: a Sydney-flavoured template hands its entity to the new project ahead of the creator's own home entity. A home entity only steps in when the template itself carries no entity.
Explicit pick on the create screen, then (for template-based projects only) the template's own entity, then the creator's home entity, then the organisation's default. Each step is skipped only when the one before it has nothing to offer.
Reports can split people, time and allocations by studio
Once a person has a home entity, the Team members list gets a Home entity column and filter you can add and group by, exactly like the columns already covering job title and employment type.
- 1
Go to Team › Team members and add the Home entity column from the plus menu.
- 2
Filter Home entity to Sydney Office to see only Sydney's people, or group by Home entity to band Melbourne and Sydney side by side.
The Time and Resource Allocation reports go further: they already had an Entity column showing which studio the project belongs to, and now carry a second, separate Home entity column for which studio the person belongs to. The two usually agree, but they don't have to. Priya, based in Sydney, can still log time or carry an allocation against a Melbourne project, and a row like that shows Melbourne under Entity and Sydney under Home entity at once. Reading the wrong one of the two is the easiest way to misread a studio split on those reports.
On Time and Resource Allocation reports specifically, Entity describes the project and Home entity describes the person doing the work. Group by the wrong one and a report that looks like "Sydney's work" might actually be "work Sydney-based people did," which can include Melbourne projects they were staffed on.
Groups don't have an entity
A group, like the Architect team from group people into teams, has no entity field of its own and never will while its members can span studios. A group is a shared bucket of capacity; the studio split lives on the individual members, not the container.
To see how a group breaks down by studio, don't look on the group itself; filter or group the Team members list or the Resource Allocation report down to that group's members instead, using Home entity to see who's Melbourne and who's Sydney within it.
Troubleshooting
- The Home entity field isn't showing on a person's Profile. Same rule as everywhere else for entities: it only appears once a second active entity exists. With just one entity, there's nothing to choose between.
- A new project didn't default to my home entity. Either you don't have one set, it's since been archived, or you built the project from a template that carries its own entity; templates take priority over your home entity.
- I can't find an entity split on the groups report. There isn't one. Groups carry no entity of their own; filter the Team members list or the Resource Allocation report to that group's members and group by Home entity instead.
- A Time or Resource Allocation row shows two different entities. That's not a bug: Entity is the project's studio and Home entity is the person's. They diverge whenever someone works on a project outside their own studio.
Where this fits next
A home entity is a small setting with a real payoff: sensible project defaults and a studio-aware view of your people. If you haven't set up entities at all yet, start with run multiple entities in one workspace. Once projects and people are both tied to a studio, give each entity its own billing identity covers what prints on the documents those projects raise, and break reports and accounting down by entity covers the rest of the reporting split.
Related articles
Search Monument help
Search help articles and open a result.