Set capabilities for specific folder

[RudiHendrix]

Within our environment we have 3 groups of users:
Functional Admins
Authors
Consumers

Consumers only have rights to run reports and some other minor features. (This is arranged out of the box)
Authors can create, edit and delete reports. They can also use Query Studio and Analysis Studio.
Functional Admins have more rights to (for example) auditing packages etc.

Now the thing is: I have 2 folders in Cognos Connection being:
Acceptance
Production

I would like the Authors to be able to create reports using report studio and store them in the Acceptance folder. Once tested and accepted by other users the report should be copied to the Production folder. However, I want the Functional Admins to be the only ones who have full access to the Production folder. Once copied the Authors and Consumers should have rights and capabilities to run the reports and view the outcome. The should not be able to open the report in report studio and make changes to it.

How can I arrange this?

In a first attempt I have set the permissions for the Authors on the properties of the folder to be able to Read, Execute and Travers. Further I have only set the capabilities for the Functional Admins.

[mpflug]

It sounds like you want people to have create but not delete access?  As far as I know you can't do this through the cognos interface.  "Write" implicitly includes both creation and deletion privileges.  If you're tied to this you could use the sdk to write a script to move reports that could be triggered by authors but actually run as an admin.

[RudiHendrix]

No, what I wanted was only for specific users to be able to create reports in that given folder. Other users are only allowed to see reports in the folder.

At first I thought I had it arranged by removing the "Write" rights for a usergroup for that specific folder, but I was struggeling with the fact that my test user was still able to save the report!
Then I found out that the test user was the owner of the report. Therefore he was still able to save the report, although it existed in a folder where he had no rights to write. After taking ownership of the specific report the issue was solved.