Web dashboard

Add custom fields to a page template

Add a field of your own to every client profile — and understand that you are changing a shared definition.

Sound is off

A page template defines the extra fields that appear on a kind of profile. Clients, facilities and users have one template each; assets can have several, one per asset type.

You are editing a shared definition, not one profile. A field added here appears on every profile using that template — which is the point, and also the reason to be deliberate about it. Adding a field to the Client template adds it to every client in the organisation.

Sections group your fields on the page, so a template with more than a couple of fields stays readable.

A field has a name (the label people see) and a type, which decides what can be entered: short and long text, number, date, time, checkbox, radio buttons, dropdown, email, phone, address and currency. A field can be marked required, and it can be restricted to certain roles — useful where a detail should be recorded but not visible to everyone.

Changing the template needs page-template management permission; filling the field in on a profile needs ordinary edit access to that record. They are different jobs and usually different people.

Step 1
Open Page Templates
Admin Settings > Page Templates, on the Client entity. If your organisation has no client template yet, Create Client Template starts one.
Step 2
Open the template editor
Each entity has a template that decides what its pages hold. Clients, facilities and users get one each; assets can have several.
Step 3
Add a section
Sections group your fields on the profile. Put the field somewhere a reader would look for it rather than at the end of a list.
Step 4
Name the section
For what it holds, not for the project that prompted it.
Step 5
Add the field
Then the field itself, inside that section.
Step 6
Name it and choose a type
The name is the label people see. Field Type is required and starts as short text — change it deliberately, because it decides what anyone can put in the box. Short text, a number, a date, a currency amount and more are on the list, and you can mark a field required or restrict it to certain roles.
Step 7
Save the template
Create Template on a new template, Save Changes on an existing one. This is the moment it applies to every profile using the template, not just the one you are thinking of.
Step 8
Fill it in on a profile
Open any client: the section you made is on their profile with your field in it. A profile is read-only until you open a section to edit it — use the section's own edit control, type the value, and save. The value is stored on that client's record, not on the template.
Step 9
On every client, not just this one
Open a different client and the section and the field are there too, empty. That is the distinction the template draws: it defines the question, and each record carries its own answer. A field you add for one situation is a question asked of everybody.
Step 10
Check it kept the value
Go back to the first client and reopen their profile. The preference you typed is still there — a saved click is not the same as a saved record, and reopening is how you know.
Step 11
Required is a decision about existing records too
Marking a field required does not retrospectively fill it in. Existing profiles simply have it blank, and the next person to edit one of them meets a requirement they may know nothing about. Add required fields when there is a plan for populating them.
Step 12
Restricting a field to roles
A field can be limited to certain roles, which is the right tool when something needs recording but not showing to everyone. It controls what is displayed on the profile — it is not a substitute for the access rules on the record itself.