Would you consider adding a level of permissions between “owner” and “member” that could create projects, manage teams, add users (up to the license seat limit), but not manage the subscription, namely anything with a cost impact? The owners of our organization are not the ones running simulations day to day, but we’re somewhat reluctant to make the primary users of Pollination owners of the organization, since on the “Subscription” tab there’s a button that will charge us $~3000.
Since teams and private projects are unlimited, there’s no cost impacts, just possibly some organization/tidiness impact.
That’s a good point, and I understand the pain. I was just discussing this with @robm on a private post.
We have a similar user request here for a slightly different case.
I will prioritize this on our end to provide more granular user permissions to address the issue.
Meanwhile, the easiest way to address this issue is to create a project per team and give them owner access to that project. I know it is against the core design to keep the studies for different projects separate but it should minimize the management overhead until we have a better solution.
Thanks for the quick reply, Mostapha, and thank you for adding it to your list!
Your solution is a good one and I think we’ll go that route, along with making some “power users” an owner temporarily in case new projects need to be spun up without jumping through hoops.