It has happened too often that we create a single role in order to deploy a package for testing to Thinkwise, that we have missed to check the All rights option.
Setting this field default to True will help alleviate this error.
Further on when setting specific rights, this toggle can be removed automatically.
Compare this to the toggles for subject performance of default, context, layout and badge. In which case the stored procedures are initially not called, but only after a template has been linked to a program object.
How about taking it a step more friendly and supplying a newly created project with a pre-made 'All rights’ role? It saves a bit of time.
Hi Roy,
We have discussed this idea internally but we ultimately decided to decline this idea as we do not want to give the impression that an All rights role is the right thing to have. Only for administrators an All rights role could exists but it should be created and used consciously. All other roles should be as small as possible. Our idea of Role based access control focusses on having smaller roles for more specific distribution of rights. So this idea conflicts with our vision.
Completely agree with this vision.
Alas, during the first version when no specific roles has yet been decided on by the product owner, we still require an all rights role in order to deploy to a test-environment, or even test the Web / Universal GUIs.
Such an initial role would be most welcome in those situations. And would appreciate it very much when this initial role (maybe not even visible under roles) would be deactivated upon creating a specific role.