User Generated Content
When a user leaves the company, you might think you just delete their account and move on. The problem: that user may have been the owner of a layout the whole sales team uses, a profile the dispatchers depend on, or a filter the night shift opens every morning. Delete the account without thinking, and the shared content goes with it - silently breaking views for people who never touched the departing user's stuff.
User-generated content is what Dime.Scheduler calls those owned-but-shared artifacts: profiles, layouts, and filters that a user created and shared. This page is how you find them and transfer ownership somewhere safe before you remove the original owner.
Spotting the problem before deletion
The users grid in user administration has a column in the first position that warns you when a user owns shared content. If that icon is there, you have homework before the delete button is safe to press.
Click the warning to open a dialog that lists every shared profile, layout, and filter the user owns. Reassign them in place: double-click the Owner column and pick a new user. Three tabs separate the three artifact types - work through them one tab at a time.
Once the warning icon is gone, the user is safe to remove.
The standalone view
The user-generated content page is the bird's-eye version of the same workflow. Use it when you want to audit ownership across the tenant - for an audit, before a reorganisation, when a department changes hands - rather than handling one departure at a time.
The layout mirrors the user-administration views: a paged list of users on the left, three contextual tabs on the right (profiles, layouts, filters). The right pane stays disabled until you select a user, then filters to that user's artifacts. The Clear Filter button drops the filter and shows everything across all users, which is useful when you want to spot artifacts that should be owned by an admin but are sitting on a personal account.
The grids are editable. You can rename an artifact, change its owner, or change its sharing options directly here. What you cannot do is edit the content of the artifact itself - that still happens in the planning view where the user originally built it.
