IT Monkey:   Join the Cireson Community today for your chance to win $50!
We appreciate you taking the time to vote and add your suggestions to make our products awesome! Your request will be submitted to the community for review and inclusion into the backlog.

We recommend reviewing what is submitted before posting, in case your idea has already been submitted by another community member. If it has been submitted, vote for that existing feature request (by clicking the up arrow) to increase its opportunity of being added to Cireson solutions.

For more information around feature requests in the Cireson Community click here.

Control Limiting Collection for deployments to a Create a collection on demand

Currently this creates a collection that is limited to all systems.

would love to see the ability to control the limiting collection by user role.

i.e. User 1 who can only deploy to W10 workstations could be limited to a custom collection called. All W10 Workstations

User 2 who can only deploy to WS2012 could be limited to a collection called All WS2012 Servers 

having to many collections to limited to all systems can cause issues with collection update times  

1 votes

Submitted · Last Updated

Comments

  • wally_meadwally_mead Cireson PACE, Product Owner Advanced IT Monkey ✭✭✭
    Thanks Jason. As Flemming mentioned in one of your other posts, full collection management is coming in a future release. So today, unless you implement Configuration Manager RBAC within the CMP, you don't get to control which collections a user sees and can create. But in the future :-)

    Keep the suggestions coming, we love the feedback.
Sign In or Register to comment.