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
Invite your team
Bring colleagues into your workspace with the right access from day one: invite a new person by email, or send a login to someone already on your team.
What you'll achieve
Get your colleagues into Monument with a login and exactly the access they need.
You'll end up with: Invited team members who can sign in, each with the right account, project and team access.
Before you start
Adding someone to Monument is really two decisions bundled into one: does this person get a login, and what can they do once they have one. Handle both at the point you bring someone in and there's nothing to untangle later.
We'll bring Marcus Webb into Northlight Architects as a new hire, and see how to send a login to Priya Sharma, who's been on the team for a while already.
Access has three independent scopes
Monument doesn't rank people on one ladder. Instead, access sits at three separate scopes, and a person can hold a different access level in each at once:
- Account: what someone can do across the whole organisation. Built-in access levels: Director, Office administrator, Project owner, and Team member (the default).
- Project: what they can do on one specific project. Built-in project roles: Owner, Finance, Manager, Delivery lead, Member, Team member with project finances, and Viewer.
- Team: their standing within a team, a group of people. Built-in team roles: Lead, Resource manager, Viewer, and Member.
Because these compose, Marcus can be a plain Team member account-wide, the Owner of Riverside Apartments, and the Lead of the architecture team, all simultaneously. Wide access on one project never has to mean wide access everywhere.
Everyone new defaults to Team member at the account level: their own timesheet and expenses, and the projects they're allocated to, in hours. Widen access deliberately, project by project or team by team, rather than defaulting everyone to admin.
Add someone new, with a login in the same step
People are added under Team › Team members. New team member opens a blank profile: the same page and tabs every team member has, with the printed profile beside it filling in as you type. Creating the person and sending them a way to sign in happen together, when you click the button in the bar at the bottom.
- 1
Open Team and click New team member.
- 2
Leave Start from on Nothing: the practice's standard week and leave.
- 3
On Details, enter their name (Marcus Webb) and the email the invitation goes to.
- 4
Under Employment, pick or create their role, Senior Architect.
- 5
Open the Login tab and tick Send them a login invitation. The hint underneath confirms which address gets the email.

- 6
Click Create and invite. Monument creates the person, emails the invitation and opens their profile.
Their page's Login tab, under Profile, then shows the invitation sent to their email.
The login invitation isn't mandatory at creation. Leave the tick box off and the button reads Create team member: the person still exists as someone you can schedule and staff, and you can invite them from their page the moment they're ready to sign in.
Invite someone who's been waiting
Not everyone arrives with an invitation attached on day one. Priya Sharma has been part-time on the team for a while, added before anyone got around to sending her a login. That's fine, since the invite lives on her page whenever you want to send it.
- 1
In Team › Team members, open Priya Sharma's page. Under Needs you, it says she cannot sign in yet.
- 2
Click Invite at the top of her page.
- 3
Enter her email address and click Send invitation.

The link she receives is identical to the one sent when Marcus was created. Her page now reads Invitation not accepted yet, and the top button becomes Invite again, so a resend is one click away if it goes unanswered.
What actually happens when someone's invited
The invitation is an email carrying a secure link. Opening it signs your colleague up (or in), and drops them straight into your organisation: they return to the secure invitation page and accept it there, rather than building a workspace of their own.
Links do expire, so a resend now and then is normal rather than a sign something's broken. The person's record always shows the current status: sent, when, and how long is left.
Set what they can actually do
Access levels live under Team › Access levels, in one list with a section per scope: Access levels (account-wide), Project roles, and Team roles. Marcus's account access level, his role on Riverside Apartments, and his role in a team each come from their own section.
Only admins can open Access levels. If you can't reach it, that's your account access level, not a bug, so find someone who is an admin.
Managing an invite after it's sent
An outstanding invitation shows on the person's page:
- Pending: Needs you reads Invitation not accepted yet, with who it went to and when the link stops working. Invite again at the top sends it again; the Login tab under Profile can cancel it before it's ever accepted.
- Accepted: the person can sign in, and removing their login cuts it off entirely. The person stays on the team; they just lose the ability to sign in.
Troubleshooting
- No email, no invite. The login invitation needs somewhere to go, which is why an email address is the only field it actually requires.
- Revoke and Revoke Access aren't the same button. One cancels a pending invite; the other cuts off an active login. Different stage, different consequence.
- Team member by default isn't a bug. It covers their own timesheet and expenses and their allocated projects in hours, nothing financial or admin. If someone new "can't see anything", that's the default doing its job; grant what they actually need.
- Access can stack quietly. A Team member account-wide might still be Owner on one project. Check all three sections of Access levels before assuming what someone can or can't do.
Where this fits next
Your people are in. Ready to put them to work? Start your first project next, or go deeper on team setup with Working hours to organise teams and rates. For the defaults every new invite inherits, see Organisation setup.
Related articles
Search Monument help
Search help articles and open a result.