Profile fields

Turn Nextcloud accounts into a structured directory for real operational work.

Profile fields lets teams add organization-specific profile data that does not fit in the default Nextcloud profile, with clear governance over who can edit each field and who can see it.

• Model support regions, customer segments, escalation aliases, incident roles and other business-specific profile data.
• Combine self-service updates with admin-managed fields for sensitive operational context.
• Surface the same custom data in personal settings, admin catalog management and user administration workflows.

This makes the app useful for internal directories, support operations, partner programs and other corporate deployments that need richer account metadata without leaving Nextcloud.

Features

• Central field catalog for organization-specific profile data.
• Per-field governance for admin-managed and self-service updates.
• Per-value visibility controls for public, authenticated-user, and private exposure.
• User administration tools for reviewing and updating profile field values.
• Workflow integration based on custom profile metadata.
• Global search results built only from fields and values exposed to the current user.

API documentation

The public API contract for this app is published as openapi-full.json.

Data backup and import

Run the app commands from the Nextcloud stack root, not from the host PHP environment.

occ Command	Description
profile_fields:data:export	Export the current Profile Fields catalog and stored values.
profile_fields:data:import	Validate an import payload without writing anything.
profile_fields:data:import	Apply the non-destructive upsert import.
profile_fields:data:clear	Clear app definitions explicitly before reimporting into the same environment.

Notes:

• The import contract is versioned with schema_version and reconciles definitions by field_key and values by field_key + user_uid.
• The first delivery is non-destructive: missing items in the payload do not delete existing definitions or values.
• Validation is all-or-nothing. If the payload contains an incompatible definition or a missing destination user, no database write is performed.
• For a restore in the same environment, clear app data explicitly before reimporting.

Screenshots

Admin catalog

User management dialog

Personal settings

Workflow automation