3
[Feature Request] Add “collapsed by default” display option for custom fields in document detail view
Source: paperless-ngx/paperless-ngx#12805 · opened by @TKaluza
I would like to propose a collapsed_by_default display option on custom field definitions.
When enabled, the custom field would render collapsed by default in the document detail view. The field name/title would remain visible, with an expand affordance to inspect or edit the value. This should apply to any custom field type.
This is only a UI/UX preference, not access control. API behavior, search, filtering, workflows, exports, permissions, and stored values should remain unchanged.
Use case: long or machine-generated custom field values can be useful metadata, but they can dominate the document detail view.
When enabled, the custom field would render collapsed by default in the document detail view. The field name/title would remain visible, with an expand affordance to inspect or edit the value. This should apply to any custom field type.
This is only a UI/UX preference, not access control. API behavior, search, filtering, workflows, exports, permissions, and stored values should remain unchanged.
Use case: long or machine-generated custom field values can be useful metadata, but they can dominate the document detail view.
No pledges yet. Be the first to back this.
Comments
Similar requests
[Feature Request] Nested Custom Fields and Custom Fields of Type Class and List
12 votes · 0 comments
[Feature Request] Add Custom Fields Support to Correspondents, Document Types, and Other Entities
27 votes · 0 comments
[Feature Request] Using custom fields in workflow title templates
32 votes · 0 comments
[Feature Request] Define custom fields as required (mandatory)
35 votes · 0 comments
[Feature Request] Advanced search for custom fields with support for date filtering literals
7 votes · 0 comments
No comments yet.