Custom fields for SRM records | Civio Engage Knowledge Base [Skip to content](#main) [ ![Civio Engage Knowledge Base](/civio-light.svg) ](https://engage.knowledge.civ.io) [Product documentation](/articles) [Release notes](/releases) [Roadmap](/roadmap) [ Support portal ](https://engage.knowledge.civ.io/portal/login) Toggle navigation [Product documentation](/articles) [Release notes](/releases) [Roadmap](/roadmap) [Support portal](https://engage.knowledge.civ.io/portal/login) 1. [Home](/) › 2. [Product documentation](/articles) › 3. [Stakeholder Management](/articles?category=16) › 4. Custom fields for SRM records Custom fields for SRM records ============================= Updated 1 day ago · 4 min read Search Search SRM ships with the fields most engagement teams need. Anything else your organisation tracks (a portfolio, a policy area, a jurisdiction, a consent flag, a membership number) you add yourself as a **custom field** on stakeholders, organisations or initiatives. A custom field is a first-class part of the record once you add it. It appears on the form, on the record's overview, as a column you can switch on, as a filter, in the spreadsheet export, and as a target for [survey mappings](/articles/capturing-stakeholders-from-a-survey). Where custom fields are defined ------------------------------- Each of the three entities has its own settings page: 1. From the left menu, open **Settings**, then **SRM**. 2. Choose **Stakeholders**, **Organisations** or **Initiatives**. 3. The **Custom fields** section is at the top of the page. ![The SRM section of Settings, showing links to the Stakeholders, Organisations and Initiatives settings pages](https://engage.knowledge.civ.io/storage/bjWZ1B1WjQx3eyayDWgQLJxuyFWqCwkBpHJf9Hea.png) Interactions, issues, tasks, notes and stakeholder groups do not take custom fields. Use the record's description or a tag on those. Adding a field -------------- Custom fields are built with the same form builder used for surveys, so the controls carry the same labels. 1. On the entity's settings page, click **Add input** and pick the field type from the list. 2. Fill in **Question**. The builder is shared with surveys, which is why the label field is called Question. Whatever you type here is what your team sees on the form, and it becomes the column header and the filter name. 3. For a **Drop-down**, **Radios** or **Checkboxes** field, add the options. You only type each option's text; the stored value is taken from it. 4. Add a **Description** if the field needs explaining. It shows under the field on the form. 5. Tick **Answer required** only if a record cannot exist without it. A required field blocks every save, including on records created before you added the field. 6. Click **Save**. ![The Custom fields form builder on the Stakeholders settings page with a select field being configured, showing the label and options inputs](https://engage.knowledge.civ.io/storage/kkc6kRhhPIOT6eMvfRTWsQwn9huDqzHspIRebBZA.png) ### Field types available Type Good for **Text short** Short free text, such as a reference number or a portfolio name **Text long** Longer plain-text notes **Number input** Counts, sizes, scores of your own **Date only**, **Time**, **Date and time** Review dates, term end dates, appointment dates **Drop-down** One value from a controlled list. Tick **Allow multiple selections** to let a record hold several. **Radios** One value from a short list, all options visible at once **Checkboxes** Several values from a list, such as policy areas or interests **URL**, **Email**, **Phone** Values you want validated as they are typed File and image uploads are not offered, and neither are the survey-only question types (likert, rating, rank, slider). Attach files to an [interaction](/articles/interactions) or a [note](/articles/notes) instead. The field type decides how the field filters. A **Drop-down**, **Radios** or **Checkboxes** field filters as a multiselect of its own options; a text field filters on a partial match of whatever was typed. Where the values appear ----------------------- Once a field is defined, it shows up in five places: - **The create and edit form**: grouped in a card of their own, between **Sentiment** and **Team** on the stakeholder form. - **The record's overview**: a **Custom fields** card in the sidebar, listing every field that holds a value. Empty fields are left out. - **The list view**: one column per field, off by default. Switch it on from the column selector. - **Filters**: one filter per field. - **The spreadsheet export**: every custom field gets a column, whether or not the record has a value. Custom field columns are also **sortable**. See [Filtering, columns and bulk updates in SRM](/articles/filtering-columns-and-bulk-updates-in-srm). ![A stakeholder record overview with the Custom fields sidebar card showing two custom field labels and their values](https://engage.knowledge.civ.io/storage/dXyJZHDP8QWqSXpv83bQUkT3znY8HH6GNeOlhCov.png) Planning your fields before you import -------------------------------------- If you are bringing existing stakeholder lists into SRM, define your custom fields **first**. The fields are what a spreadsheet import maps onto. See [Getting your stakeholder data into SRM](/articles/getting-your-stakeholder-data-into-srm). Changing or removing a field ---------------------------- Edit a field's question text, description or options at any time from the same settings page. Changing an option does not update records already saved against the old value. **Removing a field hides it, it does not clear it.** The field disappears from the form, columns, filters and exports, but values already saved are kept until each record is next saved. If you add the field back with the same name, those values reappear. To clear a value deliberately, empty it on the record itself. Permissions ----------- Editing SRM custom fields needs the SRM settings permission, which the **Stakeholder Manager** role holds (as do Administrator and Team Lead). **Stakeholder Viewer** cannot reach the settings pages, but does see custom field values on records they can read. See [SRM Roles](/articles/srm-roles). Related articles ---------------- - [Stakeholders](/articles/stakeholders) - [Organisations](/articles/organisations) - [Initiatives](/articles/initiatives) - [Filtering, columns and bulk updates in SRM](/articles/filtering-columns-and-bulk-updates-in-srm) Was this article helpful? ------------------------- Your feedback helps us prioritise what to rewrite. Yes No [ Back to Stakeholder Management ](/articles?category=16) On this page ### Still need help? Raise a request in the support portal and track it to resolution. [ Submit a support request ](https://engage.knowledge.civ.io/portal/login) Submit a support request through the [support portal](/portal) or email . © 2026 [Civio](https://civ.io) [Privacy Policy](/articles/privacy-policy) [Terms of Use](/articles/terms-of-use)