06-07-2019 02:09 PM - edited 08-03-2021 11:03 AM
How To: Manage a Collection
With the 2019.2 release of Server, Collections functionality has been expanded to overcome some of their previous limitations. This article covers Collections functionality and permissioning.
Prerequisites
Procedure
Permissions Example
You're the owner of a brand new Collection. The first person you add is the co-manager of the Collection, who is also the backup owner if you are unavailable. You give the backup owner admin privileges, which includes all asset and user permissions.
Next, you add your IT representative. This person has no interest in governing over the assets of the Collection, they just want to regularly clean up the Collection user set and ensure the right people have access. You give your IT rep user privileges, which allows them to add and remove users, update their permissions, and set their expiration dates.
Finally, you add the new guy, the new analyst to join your team. He is new to Server, and he is very excited. You want him to be able to add all the new analytics wonders he can create and update existing assets. However, until he gets familiar with the uses of all assets, you want to keep him from removing assets.
Common Issues
I can't find Shared Schedules in my collection.
Shared schedules were not included in the current collection improvements. We're looking into possible implementation options based on the feedback from studios.
A curator can do more than their permissions allows.
Curators are automatically admins of collections. However, they are only able to access the assets of collections they are added to.
I can't edit user permissions.
You can! The current design allows you to select the checkbox at the front of the table, and a permission button displays at the top of the table, allowing you to edit the user's permissions. You can also use this method to bulk change permissions if needed.
Hey Tanya, Sydney and Marty, thanks for posting this, it will be really useful to share with our customers.
I do have one questions regards the 'update' permission on assets?
What exactly does this allow? To me it sort of suggests that anyone can update an asset if it is shared via a collection; but from my testing that's not the case?
Thanks in advance!
Hi Ben, @BenMoss
That is correct, if the user has the update permission for assets they can modify and save back up to gallery a workflow.
If you open up designer and open the workflow from gallery. (Making sure that designer is 19.2 as well)
Modify the workflow and hitting save should open up the update dialogue with the location being the name of the collection.
If that isn't what you're seeing if you could post an error message or what you are seeing if be happy to take a look.
OH YOU GUYS ARE AWESOME (L); will be blogging this myself ASAP!
Hi All --
Still learning all the server stuff. If I don't give any specific permissions to this collection (based on the grid above) will someone I add to the collection be able to run the workflow?
Here is what I want to do. I want to put certain workflows behind the login and segregate them into collections. For instance:
There is one workflow that I want anyone to be able to run without having to log into server or create an account. Thank you in advance for your help.
Seth
@smoskowitz That is correct. If you add a workflow to a collection you can run that workflow if that collection is shared with you and you have the ability to run workflows.
As for your last case, if you mark a workflow as public. Go into The workflow page -> sharing -> place in my companies gallery
If you go to gallery and don't log in that workflow will show up on the home page. In order to run it you will have to go to the Admin -> jobs page and enable anonymous usage (You must be a curator to do this)
Thank you @MartyM, I think I am starting to get the hang out of how this works. The biggest piece that I missed is that a user needs to be a Member of the gallery for this to work correctly. I had everyone as a Viewer.
I learned something today!
Thanks,
Seth
Hi ! Question: Is is possible to add multiple workflows to a collection in a single operation (either by selecting multiple, wildcard etc) ? I can see how to add them one at a time, but we want to do some housekeeping with our collections which means moving many workflows around. And, since subscriptions are going away in favour of collections, want to get a head-start. Thx.
@8088 This is not yet possible, but we appreciate the great feedback, and we will definitely strongly consider addressing this need for an upcoming release.Thanks!
I'm still struggling to understand what the "Update" prevents if it is unchecked. I just updated one of my processes and saved a new version in a collection where I didn't have "update" permissions. My assumption would have been that it wouldn't have saved as a published version if I didn't' have update access.
@stvnhdmpa -- If a user has only the update box checked, then they can update (change) a workflow, but not add or delete workflows to the server.
Thanks,
Seth
@smoskowitz See my above example. This is my permissions in this collection. I do not have update access.
As you can see, I updated a workflow and it updated in the collection.
I even later removed my "add" permissions and it still allowed me to update the workflow and the updated results appear to me in the collection.
I'm not able to add new workflows to that collection. I am a curator, does that override these permissions?
@stvnhdmpa
There are a couple other ways you could be seeing this. One is you have native access to the application. IE you are the one that uploaded it.
As well as yes, being a Curator also overrides those permissions as you would be able do anything in the Admin side of server without the permissions anyway.
@stvnhdmpa If you're a curator (admin), all other permissions mean nothing. Can you create a new account with less permissions to test?
Thanks,
Seth