Selective lock on Contributor

[GEPlebe]

Does anyone know of a way to lock out only certain people from contributor?  Currently the practice is to 'lock' contributor via the GTP options during a planning setup.  This however is a universal lock - users can via contributor but not make any changes.

Any advise appreciated. 

Anthony

[StuartS]

Can you not control and get the behaviour you want through adding and removing people from groups set in the rights file?

For exmaple if you want someone to access but not edit then VIEW?

Not aware of any method to actually have elist items locked for only certain people.

I am using 8.1 so unless this has changed in any later releases?

Regards

Stuart

[sascha]

Try adding a new group like 'Planning disabled' and assign planning package security in Connection to 'deny'. AFAIK the most restrictive security should apply which makes the package unavailable to this group. Add/remove users as you like.

As I haven't done that before it would be nice to get a small feedback it this does work or not.

[adityashah27]

The "Rights" set in CAC would override any changes in permission for contributor package on portal.
I would suggest to give VIEW rights to those users in CAC unless there is any creative ways to do this.

[GEPlebe]

Thanks for the feedback. 

We've got all groups set up in access manager with appropriate security settings.  But during setup for each planning session we like to lock everyone out so that they can't make changes and then make reconciliation difficult.

The issue is not day-to-day access, but rather being able to freeze most people out during a select period, and then letting them back in once setup is complete...

[StuartS]

Is the take application offline / on line in CAC on the toolbar not suitable for your needs?

[sascha]

The "Rights" set in CAC would override any changes in permission for contributor package on portal.

a) Only if you do a GTP. In case you just want to lock users step by step in a running planning process I assume that there aren't any GTPs.
b) If there are you can prevent overwriting package security with the Rights in CAC development setting below 'Go To Production Options' by disabling 'Overwrite the package access rights at the next GTP'.

[adityashah27]

Sacha,

I know its not related to this thread, but do you think it is recommendatory to disable override? when there is a new rights added in CAC, it wont take effect on portal.

Aditya

[sascha]

I know its not related to this thread, but do you think it is recommendatory to disable override? when there is a new rights added in CAC, it wont take effect on portal.

Aditya, I totally agree with you and would only facilitate this option to temporarily change the package security. If there are frequent changes in the rights you would need to maintain security in two places which I don't like.

BTW I never used this functionality in practice but still think that it might be a nice way of temporarily lock users from the package without having lots of GTPs.

[GEPlebe]

Is the take application offline / on line in CAC on the toolbar not suitable for your needs?

I wasn't aware there was such an option in the CAC.  After a look I cannot see such an option either (only 'Remove Application') - is this available in 7.3 or only in later versions?

[adityashah27]

its only available 8.2 onwards.

[StuartS]

You can do this in 8.1