Skip to main content
Use Settings > Customization > Fields to define extra information for portal records. Choose Devices, Compliance, Goals, Budgets, Planner, Users, or Companies before adding a field.
A new Devices custom field starts as an unsaved row with separate save and cancel controls.

A new Devices custom field starts as an unsaved row with separate save and cancel controls.

​
Before you start

This is an MSP staff settings workflow. Your role needs access to Custom Fields settings; creating, editing, reordering, and deleting also require the corresponding action permissions. Company users ask their IT provider to change field definitions. Definitions belong to the shared portal catalog for their record type. Creating a definition does not fill in existing records, create a PSA custom field, or grant permission to read or edit a record. Configure PSA project fields separately in Project Settings.

​
Create a field

1

Choose the record tab

Select the entity you want to extend. For example, choose Devices, then Add Devices Field. The Add button uses the selected tab’s name.
2

Enter the field definition

Enter a descriptive Label, choose its Type, and configure scope. Add opens an unsaved row; it does not create the field yet.
3

Save the row

Select the green checkmark and wait for the success message. The red X cancels this unsaved row. Each field saves separately; there is no final page-wide Save for these definitions.
4

Add choices after saving a choice field

For Dropdown, Multi-Select, or Radio Buttons, first save the field as optional. Expand its saved row, select Add Option, enter the choice, then use that option’s checkmark. Repeat for each choice. After options are saved, edit the field to enable Required if needed.
Choose the field type carefully when creating it. Do not rely on changing the Type selector on an existing field to convert its saved definition or values. For a different type, create a replacement field and review the records before retiring the old one.
The new-row form does not offer Hide from company users. If the field is internal, create it, edit the saved definition to hide it, and verify visibility before filling in sensitive values.

​
Scope and Company visibility

For Compliance, also choose the fill location when creating the field:
  • Filled on the check (pre-filled): configure the value on the check definition; it is shown read-only on runs.
  • Filled on compliance page: enter the value for the individual run.
The Compliance fill location is fixed after creation. Plan a replacement and preserve needed values before deleting an old definition.

​
Edit, reorder, or delete

Open a saved field by its label or pencil. Change the label, required setting, scope, or Company visibility, then select the row checkmark. Use X to cancel that draft. Save or cancel before leaving the page. Drag a field row by its handle to reorder it. Reordering saves immediately. The current options editor does not offer option dragging. Expanded Field Options save independently: a checkmark saves an option edit, and an option’s trash control removes it immediately without a separate confirmation. Closing the editor or canceling a field draft does not undo saved option changes.
Deleting a field removes its stored values across records. The Delete Custom Field dialog requires the field name before confirmation. Cancel keeps the definition. Deleting a definition is different from clearing a value on one record.

​
Check the result and recover from errors

Open a representative record of the intended type and check the Custom Fields section. Save its value using that record’s own save controls. Verify the intended Company role separately when changing visibility; an MSP preview does not prove client access. If a save or reorder reports an error, reopen the page and check stored fields and options before retrying. Reordering updates multiple rows, so an error is not proof that every row stayed unchanged. A new field with a conflicting name may need a distinct label.
No. It opens a draft row. Use the green checkmark and wait for success to create the definition.
Save the optional field first, expand it, and save at least one option. Then edit the definition to enable Required. If the warning remains after adding an option, reopen the page to reload the saved option count.
No. Field edits and option edits save separately. X cancels only the current unsaved edit.
The current Field Options editor has add, edit, and delete controls but no drag control. The main field rows can be dragged and save their order immediately.
No. This is MSP settings. Company users need their IT provider to configure definitions and access.
No. User scope chooses which user records receive the field. Hide from company users controls whether Company users can see it.
No. Deleting the definition removes the field and its stored values across records. Clear an individual record’s value instead when that is your intent.
No. These are portal field definitions. Supported PSA project fields have their own configuration in Project Settings.