AssetManager 0.5.5.73

Changed

Table filters, sorting, column widths, and row-number column widths are stored per signed-in user in the database.
Existing browser-stored table state is migrated non-destructively into the user account when no account value exists yet.
Browser storage remains the fallback when no user is signed in or the account-state endpoint is unavailable.
Server-filtered job tables use the same user-specific persistence without replacing their existing server-side filter behavior.
The profile page now explains that table views are saved automatically to the user account.

Existing table filtering, sorting, advanced filters, multi-value filters, and resize logic remain in place.
No manual database migration is required; the lightweight migration adds the new user UI-state column automatically.