Browse articles
- Control access to business finances
- Control access to rates
- Control who can create projects
- Control project administration
- Control staff and team management
- Control expenses and claims
- Control report definition editing
- Control access to contacts
- Give full project control with Owner
- Manage project work without changing money
- Let project members edit tasks safely
- Share a project safely with Viewer
- Let a team lead coordinate shared work
- Share teammate profiles without management access
- Keep team members focused on their own work
- How Monument models finance
- Revenue from resourcing
- Fixed fees
- Formula based pricing and construction cost
- Modifiers: contingencies and discounts
- Recurring and periodic fees
- Progressive billing
- Budgeting costs
- Recording expenses
- Revenue from expenses
- Pricing templates
- Operational expenses
- Recording revenue entries
Custom fields
Record information Monument doesn't track by default: add your own fields to projects, tasks, contacts and resources, like a council reference or a contract type.
What you'll achieve
Add a custom field so Monument captures a piece of information it doesn't ship with, attached to the right kind of record.
You'll end up with: A custom field that appears on every project, task, contact or resource of its kind, with a stable key that identifies the field in reporting and API data.
Before you start
Monument tracks the things every firm needs: dates, fees, statuses, people. It can't know the one detail that matters to your practice, though, whether that's a council reference on every project, a contract type, or a square-footage. Custom fields close that gap. You add a field once, decide what kind of record it lives on, and from then on Monument records it like any built-in field.
We'll add the field Northlight Architects wants on every job: a Council Reference on projects, so the planning authority's number sits alongside the fee and the dates.
Where custom fields live
Custom fields live on the Settings tab that matches what they attach to: project and task fields are on the Projects tab, resource fields are on the Team members tab, and contact fields are on the Contacts tab. A field belongs to one kind of record: a Project, a Task, a Contact or a Resource. On the Projects tab, Custom Fields shows a Projects entity tab and a Tasks entity tab side by side, since both record types live there; choosing between them, such as Projects, is what decides where the field shows up, because a council reference makes sense on a project but not on a person. Switch to the right entity tab first, then add the field, and it appears on every record of that kind.
Like the rest of Settings, these controls are restricted to admins. A field you add here applies across the whole firm, so everyone sees it on the record type you chose.
Add a field
- 1
In Settings, open the Projects tab, then under Custom Fields select the Projects entity tab.
- 2
Click Add Field and name it, for example Council Reference.
- 3
Choosing a Field Type decides what kind of value the field stores. Options include Text, Number, Currency, Date, Yes/No, URL, Single Select and Multi Select; a council reference is a Text field.
- 4
Click Create Field, and it's live on every project immediately.
For a Single Select or Multi Select field, you type the options one per line, and those become the choices people pick from later.
Monument generates the key as you type: Council Reference becomes council_reference. Review or edit the Key field before you click Create Field, since the key cannot be changed afterward.
Troubleshooting
- Fields apply immediately. Unlike code generation, a custom field is live the moment you create it. There's no page save bar to click for custom fields.
- The key comes from the name, once. Type Council Reference and Monument fills in council_reference automatically as you go. Review or edit the Key field before clicking Create Field, since the key cannot be changed afterward.
- Pick the right record type up front. A project or task field lives on the Projects tab, a resource field on the Team members tab, and a contact field on the Contacts tab. If a field you expected isn't where you look, check the entity tab too, in case it was added under Tasks instead of Projects.
Where this fits next
Fields capture the what. Next, shape the where a task is up to with your own task statuses, or set the codes and numbering that name your projects and invoices. The Customise Monument overview ties all four together and shows them on screen.