My company, a very large organization, is in the early implementation phase of Alteryx right now. My company requires frequent password changes and we plan on making heavy use of Shared Connections since there are also many shared data sources. Unfortunately, this would mean that every time a credential has changed that affects a workflow, the credential holder would have to contact Server Administration (me), and I would have to update any Shared Connections or other assets that use those credentials. This problem is exacerbated by also having to manage user permissions and which users belong in each Subscription Right now, that is not much of a big deal, but as the number of users begins to scale, this could become a very daunting task.
My current solution is to create Subscriptions for each Department, Group, or Team and give one person from that Subscription Curator permissions. This enables each Department to work more autonomously and reduces the load for Server Admin. The issue is that there is no permission level between the publishing rights of an Artisan and the ubiquitous acces of a Curator. So, with my solution, any one of the Subsription Curators can start using connections they're not supposed to have access to or deleting/stopping scheduled flows, intentionally or otherwise.
I propose that we find a middle ground between Curator and Artisan, a (Studio) Moderator. This person can be assigned one or more subscriptions by a full Curator and will have Curator-like permission, but only to the assigned Subscriptions. This means that they will be able to add/modify Credentials, Connections, and/or Scheduled under the envelope of their Subscriptions, but they won't have access to any others. I believe that this solution will mitigate the possible overflow of tedium to the true Curators while allowing the powerful communal features of Alteryx be used to their full potential.