Custom Fields

Custom fields let you extend AccessPoint's records with data points your office needs but the shipped fields don't cover. You define a field once here and attach it to an entity; from then on it appears on that entity's form, is captured on the record, and becomes available to filter and report on. Custom fields are part of AccessPoint's configuration-over-code approach — you reshape what a record captures without a developer or a redeployment.

(screenshot placeholder — capture: the Custom fields panel with the list of defined fields and the inline edit form open on one)

Where to Find It

Open Settings from the app toolbar and choose Custom fields in the Foundations group. The panel follows the standard list-plus-editor pattern: a list of defined fields with Add, an inline edit form, and a delete guard that blocks removing a field still in use.

What a Custom Field Adds

A custom field is tenant-defined and attached to an entity. It supplements the built-in fields on that entity's record with a value your office tracks — a reference number, an internal category, a program name, or any other data the shipped fields don't already capture.

Where Custom Fields Appear

• On the entity's form — the field shows on the record's detail/edit surface, where users enter and read its value.
• On the dashboard — custom fields are among the selections available in the Requests dashboard filter strip, so they can be built into saved dashboard views alongside status, priority, request type, and assigned officer.

Tips

• Add a custom field only when no shipped field fits — a lean set keeps forms and filters approachable.
• Where a field's label is user-facing, supply translations for each of your tenant's active languages so it reads correctly for every user.