Help shape 4ALLPORTAL

Users want actions to remain visible and usable even when they only apply to part of a selection, with a clear indication of which objects will not be affected instead of the action disappearing entirely. Problem / Pain: When a selection includes objects that do not meet the cond

Users want the system to apply their preferred download profile automatically when adding files to the cart, instead of always defaulting to the original file profile regardless of their actual needs. Problem / Pain: When files are added to the cart, the original download profile

Admins want to see a clear reason and actionable guidance when the system enters maintenance mode automatically, so they can resolve the underlying issue quickly without having to investigate everything from scratch. Problem / Pain: When the system activates maintenance mode auto

Users want confirmation that their upload was successful and want to see the new files without having to manually refresh the view so the upload workflow feels seamless and reliable. Problem / Pain: After uploading files, the current view does not update to reflect the new conten

Admins want to define shared settings once at a base level and have them inherited by all object renderer sets, so that common configuration does not need to be duplicated and maintained separately in every set. Problem / Pain: Object renderer sets currently have no inheritance l

Users want to share a secure upload link with external contributors, so that files can be submitted directly into the system without the recipient needing a login or user account. Problem / Pain: When files need to be collected from external contributors — such as photographers,

Users want the change history to visually highlight the specific values that changed between two versions, so they can instantly see what was added, removed, or modified without comparing entries manually. Problem / Pain: The current change history shows what a field contained be

Users want to create references between objects by pasting a URL or using drag and drop, in addition to the existing reference finder — making the process faster and more intuitive for everyday workflows. Problem / Pain: Currently, references between objects can only be created u

Admins want to define a layout component once and reuse it in multiple places, so that changes only need to be made in one place and stay consistent across the entire system automatically. Problem / Pain: When a complex layout component needs to appear in multiple places across t

Admins want to see which objects were successfully transferred during a system sync and which were not — including the reasons for any failures — so they can verify and act on the results without manual investigation. Problem / Pain: After running a system synchronization, there