Redmine

Oregon State University Central Web Services wrote:

It happens when the user in the appropriate role to create a project does not belong to a project.
For example, we set the manager permission to be able to create projects and subprojects.
User foo is created, and given the role as a manager, but not assigned to a group with projects or to any project individually.

A role is given to a user for a given project. So you can not give a role to a user that doesn't belong to any project.

foo logs in, does not see the "New project". If foo is subsequently added to a project with a role of manager, then foo is able to create projects.

It seems if a role is given the authority to create a project, it should be independent of if they belong to a project or not.

If you want users that doesn't belong to a project to be able to create project, you have to give the 'Create project' permission to the 'Non member' role.