Currently, any user with a custom role cannot be designated as a collaboration coordinator. The only roles that are permitted to be collaboration coordinators are the default Facilitator and Administrator roles.
In our company, if we have entered into a collaboration with another organization, we want to allow our GIS analysts (those closest to the data and the project teams) to be able to own and manage collaboration group participants and content. The only option to do this currently, is to assign them a Facilitator or Administrator role.
If we were to assign our GIS analysts to the default Facilitator role, they would not have enough privileges to perform all tasking required as a GIS analyst (e.g. Facilitator cannot create notebooks). On the other hand, if we were to assign them the default Administrator role, they would have too many privileges that could impact the security of our organization (e.g. Administrators can manage the organizations security and infrastructure settings).
This means, a custom role is required to allow a GIS analyst work as a GIS analyst as well as manage access to project content as part of a collaboration.
Hi Deborah - this is good feedback and I will bring it to the team for further discussion. Your requirements make sense. From the ArcGIS side of things, I believe there are certain privileges a collaboration coordinator requires and the most efficient way to verify that a user in that role has the correct privileges is to require one of the known roles that has the correct privileges. I'll bring it up to the team to see if there is anything we can do to make this situation better.
@ScottBall, thank you!
Hi @ScottBall,
Just to add weight to this I have just come across the same issue. We have users with more privileges under their custom role than a Facilitator but they cannot manage collaborations. We are therefore having to change them to Administrators, which is not ideal from a security perspective as we now have more Admins than we would like. Do you know if this change may be included in the June update?
Thanks
Anthony
I support this request. The collaboration coordinator role is far too restrictive. Also the facilitator role has to have public publishing permissions which we try to restrict in our organisation.
It would be helpful if we could have a specific permission to allow members to be group managers of external partnered groups outside of the collaboration coordinator role. I have many members that need to be mangers in external groups but do not not need to be part of other collaborations we have, and should not be searchable whenever we partner with another org. They also do not need all the notification emails.
Similar to Anthony, we are attempting to trim the number of full Administrator roles in our org, but are being prevented from doing so as the Facilitator role is too restrictive. We would like to be able to create a custom role that allows a member to be a collaboration coordinator.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.