Last reviewed on {formatted}
; }; Polarion shows a work item's attachments as a table of file names. That is efficient for documents, but unhelpful when the attachments are screenshots, photographs, diagrams or recordings — you cannot tell one from another without opening each in turn. Mediakit adds a gallery view of those same attachments. Images appear as thumbnails you can recognise at a glance and open full size when selected; other recognised file types appear with an icon identifying what they are. ## It Adds a View, Not a Store Mediakit keeps no files of its own. Everything it displays is an ordinary Polarion work item attachment, and everything you do through it — uploading, replacing, deleting — acts on those same attachments. Three consequences follow, and they are the reason the plugin behaves predictably: * **Permissions are Polarion's.** If you may not modify a work item's attachments, you may not change anything through the gallery either. Mediakit adds no permission model of its own. * **History is Polarion's.** Every upload and replacement creates a revision of the attachment, visible in the work item's own attachment history. * **Nothing is stranded if Mediakit is removed.** Uninstalling the plugin removes the gallery, not the files. They remain attachments on their work items exactly as before. ## Two Places It Appears | Surface | What it is | Typical use | | ---------------------- | ------------------------------------------------------------- | ------------------------------------------------------------------ | | Gallery section | A section on the work item form itself | Day-to-day work on the item — the usual choice | | Mediakit Upload widget | A widget placed on a rich page, pointed at a chosen work item | Dashboards and overview pages that should surface one item's media | Both render the same gallery and act on the same attachments. Configure either, or both. ## What It Does Not Do Mediakit is a presentation and upload layer, so it deliberately leaves the surrounding model alone. It does not introduce its own file store, its own permissions, its own approval flow, or its own versioning — in each case Polarion's existing behaviour applies unchanged. ## Related