My columns, our table: designing saved data views
A saved table view needs clear boundaries for columns, filters, sorting and ownership. Design for returning to work and changes to available fields too.
Article language: English

In this article
“For inspection” is a useful name for a view as long as everyone knows what has been saved under it. Is it just the column layout? A filter for equipment awaiting inspection? Or the eleven devices someone selected yesterday? Those promises lead to different results. Designing a table view starts by choosing the right one, before adding a name field.
Imagine a recording-equipment rental company with a single equipment database. Róża handles returns and needs the kit number, due date and drop-off location. The person inspecting the equipment looks for the last inspection date and a description of the fault. A shared layout showing everything forces both people to move columns around every day. The table resembles a desk where everyone has left their own folder.
Saved views can reduce that work. But they need a clear boundary between presentation, the choice of results and changes to the data itself. Moving a column does not change an item's return date. A row disappearing from a view does not mean the equipment has been deleted from the database. Those distinctions need to be visible during ordinary work, not only in an administrator's manual.
First decide what should still be there tomorrow
At our rental company, the “Returns” view could include particular columns and their order, a filter for open rentals and sorting by the nearest due date. It saves a way of finding work. When a new matching record arrives, it should appear according to the agreed rule. We are not keeping yesterday's snapshot of eleven rows.
Shopify describes order views that save filters, columns, their order and sorting. It also explains that the contents of a view change as records meet or stop meeting the filter conditions. This is one product's contract, not a definition that every dashboard must adopt.
Your own design might save less. A personal column layout without filters can be useful too, if that is what it is called. Switching from “My columns” to the default layout should not then silently change the records found. “Save column layout” describes the feature more precisely than the broader “Save view”.
Treat selected rows separately. Selecting the whole result or the current page (in Polish) defines the scope of an intended action. It need not be restored tomorrow just because column widths were saved. Specify explicitly what happens to the selection when the view changes. The hidden return of an old selection could surprise someone during the next operation.
A page number is not a complete memory of a place either. After a sort change, page three may contain different devices. The MUI Data Grid state documentation warns that restoring pagination without filters or sorting will not restore the same rows. The design should define the complete set of settings to restore.
A filter can still apply to a hidden column. If Róża hides the due date, “Returns today” should not show every rental as a result. The condition still needs to be visible somewhere outside the column itself. Otherwise, a person sees a short list but cannot explain why some devices disappeared. Editing the presentation and editing the filter should have separate effects.
Describe the saved state in one short sentence available when it is created: “We'll remember the columns, filter and result order; your current selection of devices stays separate.” The sentence must match the implementation. It is not a list of everything the table can do, but an explanation of this particular action.
Personalisation does not require giving up the whole screen
Róża wants to hide technical-condition information, but the kit number still lets her identify the device. We can make a few fields permanently visible and leave the rest flexible. A limited choice like this can be more useful than a panel where every column can be removed and the user must then find a way to recover the list.
MUI Data Grid can prevent a specified column from being hidden through the interface. That is a component behaviour. It does not grant access to the data, or establish that every column should be mandatory in our use case.
Show the current order and state of each item in the column panel. For a fixed field, give the reason if it is not obvious. “Kit number - needed to identify the device” explains more than a disabled, greyed-out control. Other columns can be added and removed without confusing that action with deleting data.
Take care with names that are close in meaning. “Last return” and “Scheduled return” should not both become “Return” when their labels are shortened. Long names in an interface (in Polish) discusses ways to keep the full text recognisable and readable. Saving space in the settings panel must not prevent someone from choosing the right field.
Reordering with an alternative to dragging (in Polish) discusses ways to move items without precise mouse movements. Apply an appropriate alternative to moving columns. Accessible move buttons or another agreed method are possible. During acceptance testing, a person should be able to tell which column moved and where it ended up. Animation alone is not enough when using a keyboard.
Do not equate a compact view with tiny type. If personalisation includes row density, it should adjust the layout within agreed limits while keeping it readable. At high text magnification, a user still needs to distinguish the device name from the fault description. The view exists to support the task, not to break a record for cells per screen.
Decide when changes take effect as the panel closes. We could provide an explicit “Apply” button or save the layout continuously. In either case, the user should know whether closing the window keeps the change. Adding “Cancel” to a panel that has already applied everything and offers no way to undo it would make a false promise.

Whose view are you changing?
Róża's personal layout should not change the screen for the whole rental company. A shared “For inspection” view, by contrast, may have an owner and editing rules. These models need to be clearly distinguished at save time. A username hidden in a profile menu does not tell people who will be affected when columns are rearranged.
Salesforce distinguishes private views from those shared with others. It also notes that a public view does not give a recipient access to records or fields they cannot already access. Sharing a configuration and the right to read data remain separate rules.
When a shared template has been changed locally, show whether the current layout differs from the saved one. Róża might add a column temporarily for a single conversation and go back without publishing the change. A clear unsaved-settings indicator next to the view name helps distinguish that state from a new shared version. Discarding a local change should restore the saved settings, not select a different filter simply because it is the default.
In our panel, a shared view could offer “Save as mine”, while only an authorised role could edit the original. This is a design proposal that must be agreed with the application owner. The user needs to understand whether they are adjusting their own workspace or publishing a new way of working for the team.
This is a task for Aeneia Design: designing screens, interactions and documentation that distinguish personal configuration from a shared template. A real table and two different user tasks are enough to start the conversation. Rules for storing settings and access must be matched to the capabilities of the agreed application backend.
Record the storage scope too. Does a preference belong to the account, a particular company or only this browser? Róża, working at another workstation, should know whether she will see her layout. If settings are local, the message should explain that without promising synchronisation. If they are saved to an account, the design needs a failed-save message instead of silently reverting to the old layout.
The fields have changed. What happens to old settings?
The rental company adds a column for the next reservation. A user has saved a personal layout without that field. Do not automatically assume every new column should appear in the middle of their list. It could be identified as new in settings or added to the starting template. The choice depends on whether the field is an extra or information necessary for the task.
If the new information changes how people work, a small dot by the menu is not enough. Róża should not issue a kit for a week without knowing it is reserved for tomorrow. The team could decide on a mandatory warning at the relevant step. But forcing a wide column onto the screen cannot be expected to repair the whole equipment-issue process.
Removing a field is different. An old view may filter by “status”, which is now split into availability and technical condition. Do not replace it with the closest-sounding name without an agreed rule. One option is “This view needs updating”, with the part that needs correction identified. An empty list must not masquerade as a valid result of the old configuration.
Not every field rename breaks compatibility in the same way. If “Location” becomes “Drop-off location” but keeps the same meaning, the user can retain its order and width. If the definition of its values has changed, the old filter needs a different assessment. Distinguish a label correction from a change in concept in the documentation, so an editorial edit does not wipe out someone's personal organisation of work.
Restoration also needs a named scope. “Default columns” can leave the filter in place. “Default view” can replace the whole set of settings. “Delete saved view” removes the configuration, not the equipment. Test those labels in real sequences: a lone “Reset” button explains none of the differences.
In data export design (in Polish), separately establish whether the file contains the columns currently visible or another agreed scope. Hiding a field on screen should not accidentally become an export rule. The person downloading the report needs to recognise its contents before passing it on.
Return to the work, not just to the same rectangles
Start testing the saved view with Róża's task: find today's return, check the kit number and identify the drop-off location. She then changes the layout, saves it and returns in a new session according to the chosen storage model. Assess whether she can do the task and whether the settings are correct, not merely whether the column menu opens.
In the test, change a single value so a device no longer matches the view. Once a return is accepted, the kit should leave the open-rentals list if that is what the rule specifies. The user needs to recognise that the task is complete, rather than assume the disappearing row means data has been lost. This is different from expecting a personal column layout to persist.
Add a new matching record and check whether the view follows the rule. Then remove access to one field from a prepared test role. The design must explain the unavailability in a way that matches the actual system. It cannot treat a personal configuration as permission to regain a field after access rights change.
Separately, open a device's details and return. Returning to a place in a long list (in Polish) involves more than restoring column widths. The user wants to recognise the record they came from and the way they were browsing. If data has changed in the meantime, the current state needs to be shown clearly.
The finished “Returns” view has a specific promise: it saves the layout and rules, shows currently matching devices, does not restore an old selection and does not change other people's settings. If the person using it can explain that after completing the task, the view's name starts to mean something concrete. Personalisation can then save daily work rather than add another panel to configure.







