Ok found a workaround, the "permissions" setting in the Tools menu. Seems to control which groups can do what, no matter what the "user permissions" page says.

There is no cross checking, ie.
1. Tools page gives read permission to unauthenticated.
2. User permissions indicate no read access for the group unauthenticated.

• status: open --> accepted
• assigned_to: Rui Ferreira

Hi Michael

That is correct. The User permissions setting defines groups and base permissions for the project.

The permissions options for each tool (if they have it), overrides the behaviour for each tool - i.e. it can add permissions that do not exist in the User permissions tab. In some cases (e.g. tickets) it defines permissions that cannot be defined in the general tab.

So in a nutshell: the User permissions is general project wide permissions, each tool can override it in its permissions.

Given the confusion, it is probably best if we update the FAQ to reflect this.

Hi

I've added a new entry to the FAQ, and page at the docs wiki on [Projects and Permissions]. Hopefully this helps clarifying things.

• status: accepted --> closed