Skip to main content
Inspiring
November 6, 2023
Open for Voting

Restricting access to invite only in enterprise team libraries

  • November 6, 2023
  • 0 replies
  • 55 views
Currently, any library created as an enterprise team library is viewable by the entire company. I have the option to make them viewable or editable, but I don’t have the option to make them invite only. Only the personal libraries are invite only.

This sometimes creates an issue for us. There are times we want to have libraries that we share with individual teams, but we don’t necessarily want to share them company-wide. Currently, the only way to do that is to make a personal library. That has some negatives to it, because any personal library we make is tied to that personal account. So if that person leaves the company and we close their CC account, that library goes away.

We have a workaround, which was suggested by someone from the library team at Adobe when I was at Max2019. I created a separate account that is not tied to a personal license, but to a general email for my team that I have access to. I can create libraries with that account and share them with myself giving edit rights, and then I can populate and invite other people from my own account. But that’s kind of a kludge workaround now that enterprise libraries are here and persistent. It also requires me to log in/out of accounts in the browser to make it work and the storage limit on that account is much smaller than our enterprise account.

What I’d like to be able to do is to create Enterprise Team Libraries that are invite only, not available by default to everyone. That would allow me to create team libraries for our team that may not be assets everyone in the company should be using. And right now that’s not possible. This is the kind of thing that gets done regularly in a DAM system, where you have varying permission levels that can be assigned and asset.

One of the other benefits of this would be limiting how many libraries are in the “browse shared libraries” page. With the number of licenses we have, this will begin to turn into a bit of a mess as more people create enterprise libraries. While my group is pretty centralized and we have our own set of curated libraries, a lot of our company is very decentralized and there’s no real way to control that if it continues to expand.