Multisite shared libraries Pro
Show one site's document library on any other site of the network — one central library, rendered anywhere, with the central site's access rules enforcing.
A school trust, a council, an agency network: one central document library, dozens of sites that need to show it. On a WordPress multisite network, FileDeck Pro renders any site’s library on any other site with one attribute:
[filedeck_library site="2"]
Every other shortcode attribute works as normal — category, layout, colours — and the block/Elementor equivalents can use the shortcode form.
How enforcement works (the part that matters)
The rendered library belongs to the central site: download links, search, pagination and signed URLs all point at it, so its own access rules, gates and activity log do the enforcing. A visitor who couldn’t see a document on the central site can’t see it through a shared render either — there is no second, weaker copy of the rules.
Two requirements, both ordinary: FileDeck active on the site being shared (network activation covers it), and the network’s normal shared auth salts (every standard multisite has this).
What it is not
Not a sync — there is exactly one library, rendered in more places. That’s the point: no copies to drift, no "which version is right".
Still stuck? Email support@getfiledeck.com.