Having one single administration project permission usually is not enough for project customization, too granular is not also good but create three categories for admin privileges as follow:

1. Things that change the project definition.
2. Things that change project access.
3. Things that are records within a project definition.

Where:

• • Definition **
    create automation rules
    integrate apps
    configure apps settings for projects
    edit project configuration
    add/remove project features
    place new boards on the project

• • Access **
    edit members for a particular project

• • Records **
    manage the components
    view and create reports
    create releases

For example, with this customization we can give developers control over versions, but not for adding people.