nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Asset Level Permissions??

jstephan

Hi,

MEDIABIN 4.6.2

Is it possible to setup individual ASSET LEVEL PERMISSIONS in MEDIABIN instead of FOLDER LEVEL? That, all users will have access to a folder, but they can not access all assets in that folder, only have access to particular assets based on their roles/permissions? Is there anyway to implement this scenario?
Thanks in advance.
John

Find more posts tagged with

Comments

lyman

Not as such. However the traditional way to handle this scenario in MediaBin is to set up a folder per role and then make reference copies of the files you wish that role to see into the folder.

Cheers,

Lyman Hurd

jstephan

Thanks for the response.

I am not totally understand what do you mean by reference copies? Can you please explain about how to do that?

Not as such. However the traditional way to handle this scenario in MediaBin is to set up a folder per role and then make reference copies of the files you wish that role to see into the folder.

Cheers,

Lyman Hurd

iwTech

Thanks for the response.

I am not totally understand what do you mean by reference copies? Can you please explain about how to do that?

Quick Reference Guide — MediaBin Web Client (Page 1 )

References. For source assets, this tab lists the name and location of any reference copies.

For reference copies, this tab displays the name and location of the source asset.

A “reference copy” is a pointer to the original file

MediaBin® Web Client

User’s Guide

Work with Reference Copies (Page 64)

-Vin

CalvinFold

Reference Copy can be thought of as an Alias or Shortcut depending on if you're a Mac or Windows user.

We've often wanted asset-level permissions and have this scenario:

We store graphics and their linked files, available only to designers, in it's own folder with a "_p" added to the folder name. At the same level as this folder is a PDF which is accessible to everyone. So the enclosing folder everyone can get into, but the "_p" projects that created the PDFs are hidden away.

Rather than rely 100% on having to make sure the project permissions are always applied on this scale (thousands of projects and hundreds of thousands of assets) we have a background script custom-written to look for the "_p" folders and making sure they have the right permissions set.

A bit wonky, but serviceable.

We've avoided Reference Copies because with this many assets they become unwieldy, especially since we're in the (bad) habit of re-organizing our assets every couple of years. Also, reference copies cause the same files to show up more than once during searches, which is confusing to users. So we use reference copies very sparingly and only for extraorinary circumstances.