Custom User Fields
Custom user fields let you record extra information about developers beyond name, email, and role. You define the fields once. They can appear on registration, on Profile, and in the admin user editor — and optionally mirror onto the Apigee developer record.
Where to find it
The Users screen also has Users List, Roles Management, and Permissions. This page covers User Fields only. See Users for accounts, Role-Based Access for roles and permissions, and Teams for team membership.
Add a field
Click Add field. Until you create one, developers see only name, email, and role.
- Label — Required. Shown on forms. Until you edit Field name yourself, the name is generated from the label.
- Field name — Machine name. Must start with a letter and use only lowercase letters, numbers, and underscores. Fixed after creation.
- Type — See field types below.
- Help text — Optional. Shown under the field.
- Choices — Required for Dropdown. One option per line. Use
value|Labelto store a different value than the one shown.
| Type | Label in UI |
|---|---|
text | Single line text |
textarea | Paragraph text |
select | Dropdown |
number | Number |
checkbox | Checkbox |
date | Date |
Who can see it and who can change it
- Who can see it — Users and admins, or Admins only. Admin-only fields are hidden from registration and Profile, and Who can change it is locked to Admins only.
- Who can change it — The user, or Admins only. Users still see an admin-managed field on Profile when it is visible to them; they cannot edit it.
Required, registration, Apigee, and active
- Required — Must be filled in before the form can be submitted.
- Ask on the registration form — Off by default. Unavailable for admin-only fields.
- Sync to Apigee — Mirror the value as a custom attribute on the Apigee developer record. The Users table shows the attribute name. On a new field, turning this on defaults Who can change it to Admins only (you can override it).
- Active — Inactive fields are hidden everywhere but keep their stored values.
Reorder fields with the up and down controls. Edit or delete from the same table. Deleting a synced field also clears that attribute from developer records where it can.
Where fields appear
- Registration — Visible fields with Ask on the registration form turned on.
- Profile → Additional Details — Visible fields. The card is omitted when there are none. Users edit only the fields they are allowed to change.
- Configuration → Users → Edit User → Profile Fields — Admins fill in values (including admin-only fields). Requires Update Users.
The list column Shown on reads Registration + Profile, Profile, or Admin only.
Sync to Apigee
When at least one active field has Sync to Apigee on, Sync to Apigee appears on the User Fields toolbar. It writes current values onto connected Apigee developer records. The editor shows how many of the 18 custom-attribute slots are in use.
You need a connected Apigee organization. If none is connected, sync reports that there is nowhere to mirror the fields yet. See Apigee Integration.
Import
With at least one field defined, click Import. The panel is titled Import from Drupal.
- Upload a CSV with one email column and one column per field.
- Rows match existing users by email. Accounts are never created.
- Map each column to a field, or ignore it.
- Create missing fields — Adds a text field for a mapped column that has no field yet. New fields are admin-managed and not synced to Apigee.
- Preview first (nothing is written), then Apply import.
Preview and apply report rows updated, already correct, no such user, skipped, and duplicate email. After a successful apply that includes synced fields, run Sync to Apigee if the import recommends it.