KB41597: "Project Configuration" option is grayed out for users who have all Administration privileges assigned through a Security Role in MicroStrategy 9.4.x - 10.x

SYMPTOM:
In Strategy 9.4.x - 10.x, a user who has all the Administration privileges granted through a security role is unable to modify the Project Configuration:
 

 
STEPS TO REPRODUCE:

1. Create a security role 'All privileges' granting all privileges under Administration.
2. Create a group 'Test' and grant the security role + inherited access for a project.
3. Create a user within this group. Do not give the user any privileges directly, so the user has only inherited privileges from the 'Test' group.
4. Log in through 3-tier project source. The new user sees Project Configuration for the project grayed out.

 
CAUSE:
This is behaving as designed. In addition to the Administration privileges, users also need to have Configuration permissions to the Server Definition object in order to modify the Project Configuration.
 
Although the user was granted all the Administration privileges through the security role, the "Bypass all object security access checks" privilege cannot be inherited through a security role. Therefore, if the user trying to modify Project Configuration does not have the required ACLs for the Server Definition object, then they cannot modify Project Configuration.
 
ACTION:
Grant the "Bypass all object security access checks" privilege at the user or group level, or modify the ACL for the Server Definition to grant users Configuration access with the following steps:

1. Log in to the 3 tier project source that has access to the projects.
2. Right click on the project source > Configure Strategy Intelligence Server > Server Definition > General.
3. Click Modify > Properties, and then go to Security.
4. Add the user or user groups that would need to modify the project configuration and give them Configuration permissions.