Origin Group Toggle in Create
Currently, if we want projects to be separated by origin groups, the authors have to update their CMS profiles and toggle them between origin groups (Toggle to a different group and work there but have to leave Create and return to CMS to toggle back to original origin group to work on other projects). It would be nice if CMS grants/removes origin group privileges to an author. So, when they access Create, they could toggle between the origin groups (pulldown menu) when a project is created.
-
Hello David,
We are currently reviewing this request. Thank you for your patience.
0 -
Permanently deleted userHi David,
Thanks for the feature request! We would like to understand why you want projects to be separated by origin groups when it is possible for a group to have multiple recipient groups defined for it such that authors can optionally publish scenarios to any of the recipient groups. Further, if the author also has an admin license, then the should be able to publish to any group and not just the recipient groups.
0 -
Thanks for the response. The key part of the request is that it is my current understanding that the author's origin group needs to match the origin group of the project of interest during creation. So, if an author has 2 projects with different origin groups, the author will need to go to CMS and change their origin group relative to the project and switch back when attention is needed on the other project.
We actually have projects that require higher level of access restrictions (non-disclosure agreements) for both project and published scenarios. The existence of these projects is even covered. In those cases, we would have an origin group that is something else than the default group. However, we have several authors that we would consider them to be super-authors that have contributions to all projects.
It would seem more efficient since the admin can define/modify which groups an author can work with already and have the author make the origin group switch either in CMS (currently prohibited though I thought it was allowed in the past) or in Create when they sign in or somewhere else. So, I would be fine if it stays in CMS.
0 -
Hey David, thanks for the feedback. What I like here is that you helped verify a strong need for continued improvement on the CMS, and it aligns with other feedback we have received. I can tell you that there is already thought underway as to an improved way to support this requirement, and perhaps we can share a little more of the plan when we meet next with our team. I'm intentionally being vague so as to not set any false expectations, but lets chat about it when we meet so you can understand what we are thinking and make sure it aligns to your requirements.
0 -
Hi Team-
Sorry, I haven't checked the chats in the community for a while, didn't see this conversation about me! I'm the author with the problem, let me share my version of the problem statement.
When I press Publish in Create, I am presented with a list of groups that I can publish to. Those groups are ones that our admin added me to. That's great. That's working how we like.
The problem is that as an author, when publishing, I'm unable to uncheck my origin group. No matter which group I select to publish to, I'm also forced to publish to my origin group.
Suppose I'm working on projects for both GroupA and GroupB and don't want folks to be able to see content from the other groups. If my Origin group is GroupA, it's no problem to publish to GroupA, it's selected by default and I can't uncheck it. But suppose my Origin group was GroupB. In that case, when I want to publish to GroupA, I'm forced to also publish to GroupB, because I can't uncheck GroupB. When I reach that point, I have to call my admin and ask them to change my origin group to GroupA.
If I'm actively trying to support projects in both groups, it becomes cumbersome to contact David every time I need to publish to a different group. It would be great if I could uncheck my origin group when publishing, or be able to adjust my origin group myself.
Thanks for all your help, David, David, and James!
Andy
0 -
We could make GroupA, GroupB, and GroupAndy. Put only myself in GroupAndy. Make GroupAndy my Origin Group.
0 -
Permanently deleted user
Hi Andrew, that’s exactly what I was going to suggest until we move to a more conventional file/folder system that gives you even more flexibility. :-)
1 -
Hi James,
Unfortunately, the idea to have me publish to a separate Origin group didn't work as we had hoped. I was only able to publish to GroupAndy. I was not presented with a list of other groups to publish to.
In talking with David W, he said there is another layer of CMS called "recipient groups" that needs to be considered. And if we were to set up the recipient groups so that I can see and publish how we want, it would expose the content to other groups.
Desired arrangement:
- GroupA content is only accessible to people who are in GroupA (and admins)
- GroupB content is only accessible to people who are in GroupB (and admins)
- Authors can be in multiple groups
- Projects can be shared with multiple authors (if they are in the group that has access)
- Authors can select to publish to any of the groups they are in, freely
Are you aware of any group and recipient group setup structure we could use to make that happen in the current software? Or do we need to wait for a CMS improvement?
Thanks for your help,
Andy
0 -
We have since added GroupA and GroupB to GroupAndy's "CAN PUBLISH TO" field, and that made it so I could publish to GroupA or GroupB, freely.
However, I'm unable to share the projects in GroupAndy with any other authors for co-authoring.
0 -
Permanently deleted user
Indeed, for an author to be able to publish scenarios to groups other than their origin group, the origin group must be configured with recipient groups. However, to share projects in GroupAndy with other authors, they just need to be a member of GroupAndy. Their origin group does not need to be set to the same as yours: GroupAndy.
Sorry that this is confusing which is why we want to change this to a more conventional file/folder system that not only gives you more flexibility, but is also more easily understood!
1 -
Thanks for all your help and tips! That's helpful that the author I share with doesn't need to have the same Origin group as me, they just need to be a member of my Origin group.
This gets us set up well enough to work on our near-term projects!
I'll keep helping David W think about CMS strategies we might need longer-term, to help inform the next CMS improvement.
Thanks again, and have a good weekend!
0 -
Permanently deleted user
That is great to hear. Please do not hesitate to reach out if there are any issues that prevent you from optimizing your workflows on our platform!
0
Please sign in to leave a comment.
Comments
12 comments