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
Sign-in security
Turn on two-factor authentication, review active sessions, and create the API keys your integrations use.
What you'll achieve
Protect the account with two-factor authentication and session visibility, and create an API key for an external integration.
You'll end up with: Two-factor authentication and session visibility ready to turn on, and an API key minted for an integration, shown once and revocable any time.
Before you start
Data living safely in Monument is only half the job; it also has to be protected. The Sign-in & devices section, under You in Settings, covers two-factor authentication and session visibility, both about proving it's actually you. The API section, under Access & security, is where you create the credentials external software uses to talk to Monument.
This is the last step of bringing your team in at Northlight Architects: require two-factor for everyone, turn it on for yourself first, keep an eye on active sessions, and mint a key for a reporting integration.
Two jobs, two sections
Prove it's actually you. Two-factor authentication and session management protect people, not software: a second factor and visibility over active sessions mean a leaked password alone isn't enough to get in. Both live in Sign-in & devices.
Let trusted software in. An API key is how something external, a custom dashboard, a script, talks to Monument's Public REST API on your behalf. It's a credential you create on purpose and can kill the instant it's unwanted. Keys live in their own API section.
Sign-in & devices is everyone's own section: each person protects their own sign-in. To make two-factor authentication a rule for the whole practice, use Domain & security under Access & security. The API section needs the API switch at Edit on the person's account access level. Decide who holds the keys before you start handing out access.
Require two-factor for everyone
In Settings, Domain & security has one switch: Everyone in Northlight Architects must use two-factor. It stays off until your own account uses two-factor, so you can't lock yourself out. Set up your own two-factor first, then come back and turn the rule on.
Two-factor authentication and sessions
At the top of Sign-in & devices sit two cards. Two-factor authentication adds a second step to signing in: turn it on and Monument walks you through scanning a QR code with an authenticator app and saving a set of backup codes, so a leaked password alone can't get into Northlight's books. Active sessions lists every browser and device currently signed in, with when it was created and last active, so you can sign out anything you don't recognise, or sign out every other session at once.
Create an API key
Switch to the API section. This is where credentials for integrations get created. Each key gets a name (and an optional expiry), and there's one moment that matters more than the rest: the full key is shown exactly once, immediately after creation. Copy it then, because Monument never displays it again.
- 1
In the API section, click New API key.
- 2
Give it a clear name, like Reporting Dashboard, and a description so future-you knows what it's for.
- 3
Turn on Set expiration date for a key that should stop working on a set day, such as a contractor's tool. Leave it off for the practice's own software. Then click Create API key.
- 4
Copy the full key from the success dialog and store it somewhere safe, since it won't show again.

- 5
Click Done. The keys table shows the start of each key, when it was last used and when it expires. Revoke is in each key's menu.
Integrations send the key in the X-API-Key header on every call to the Public REST API. The keys table lists each key's prefix, creation date, last-used date and expiry, so stale keys are easy to spot. Revoking one cuts off whatever's using it immediately, which is why naming keys per integration keeps that blast radius small.
Whoever holds the full key can act through your firm's API. Don't paste it into chat or commit it to a repository. If one leaks, revoke it and mint a new one; that's exactly what revoke exists for.
Troubleshooting
- The key really is shown once. There's no "reveal" screen afterward; only the prefix persists for display. Miss the copy, and revoking and recreating is the only fix.
- Revoke is instant and total. It doesn't pause a key, it kills it: any integration using it loses access the moment you click. Have the replacement ready first.
- API keys aren't in Sign-in & devices. Two-factor authentication and active sessions sit there; API keys have their own API section, which needs the API switch.
Where this fits next
Your team is in, each person with the right access, and every account is secure. To link invoices to your books, read Connect your accounting system.
Related articles
Search Monument help
Search help articles and open a result.