Custom columns

Display institution-wide user data fields as columns in the Users table, and edit values per user or in bulk.

Custom columns are how institution-defined custom data fields appear in the Users table. Each column is tied to a field definition shared across every user. Values show as table cells and on each user’s Overview tab, so staff can search, filter, and edit supplementary directory data alongside core account information.

Why it matters

Every university maintains data that does not fit a generic user record — matriculation numbers, external system IDs, scholarship flags, advisor assignments. Without custom columns, that information lives in spreadsheets parallel to Fuxam, creating sync problems and audit gaps.

Custom columns keep supplementary data visible in the same system of record as user accounts. Registry staff can update a matriculation number once and see it in the table, on the profile, and during user creation. When combined with bulk actions, you can import or correct hundreds of values after an intake without opening each profile individually.

How it fits

Custom columns extend how User Management presents directory data, without changing core account structure:

Custom columns are separate from roles (which control access) and user groups (which organize people). They are also separate from academic data managed in Study programs and cohorts — custom columns hold institution-defined directory fields, not curriculum or enrollment structure.

Typical workflow: define fields and columns before a major intake → set values during Create a user or via import → maintain values on the Overview tab or through bulk edits as records change → request missing data when users must complete their own profiles.

Key concepts

Field types

Each custom column has a type that controls validation and editing behavior:

Add a custom column

Alternatively, if you have column-creation access, you can add a column placeholder directly in the table header and name it inline.

When you create an ID field with a format pattern, Fuxam can automatically generate IDs for existing users.

Edit column names

Select the column header text to rename a field (when you have update access). Press Enter or click away to save. Duplicate names are rejected.

Edit values per user

In the Users table

Click any cell in a custom column and enter or select a value. Changes save when you confirm or move away from the cell, depending on the field type.

For batch edits across many users, select rows and use ⋯ → Edit Custom Fields. See Bulk actions.

On the user profile

Open a user’s Overview tab. Custom fields appear in the profile sections alongside basic information. Edit and save using the unsaved-changes indicator.

See Edit a user for the full profile editing workflow.

Set values when creating a user

The Add User form includes any configured custom fields below the standard name, email, and role inputs. Fill them in during creation if you already know the values.

This is the preferred path during intake: capture student ID, department code, or other identifiers at the moment the account is created rather than returning to fill cells later.

Access for editing values

To change a user’s custom field value you typically need both of the following:

• Permission to update that user (or users institution-wide), and
• Permission to update the specific user-management column (or columns institution-wide).

Without both, the cell or field appears read-only.

Role configuration is covered in Roles and permissions.

Best practices

• Define columns before intake. Agree on names, types, and select options with registry staff before creating hundreds of accounts.
• Use ID fields for formatted identifiers. Matriculation numbers with a fixed prefix and sequence are less error-prone as auto-generated ID fields than free-text entry.
• Keep select lists short. Single select and Multiple select work best with stable, well-defined option sets — not free-form categories that change weekly.
• Use bulk edit for corrections. After a data import, filter the affected users and run Edit Custom Fields rather than correcting cells one by one.
• Separate directory data from academic data. Program enrollment and curriculum assignment belong in Study programs and cohorts; custom columns are for supplementary directory attributes.
• Restrict sensitive columns. Use column-level access so only registry roles can edit identifiers like national ID numbers.
• Request missing values when appropriate. For incomplete profiles after intake, use data collection requests instead of leaving blank table cells indefinitely.

Common pitfalls

FAQ

Related pages