Hello Daniel,

by default only an admin has the permission to create a project. If you create an OpenProject instance you automatically are an admin.
You can give other users the permission to create projects by creating a “Global role” with the permission “Create projects” and then assign that role to the users who should be able to create projects.
The respective users can then select the “Projects” dropdown and choose “+ New project” to create projects.

To create and assign a global role, please go to the administration “User name” (upper right corner) > “Administration” and select “Roles and permissions”. Then select “+ New role”, mark the checkbox “Global role”, check “Create project” and create the role.
You can then select “Users” from the side menu, select a user to assign the permission (click on the user name), navigate to the tab “Global Roles” and assign the global role to the user.

Best,
Robin

Dear Robin,

I’m having similar issue. (see work-around below)

I added additional users to the site, granted to them the “Create project” permission in the “global role” but it does not help, because the users creating projects are being added to them as a “Member”, so they cannot do much with their own projects.
Moreover, the user is getting “403 forbidden” message after creating a project which is the consequences of the mentioned above.

In order to change that the admin user have to assign them “Project administrator” role manually after user creates the project. It makes no sense because in that case the user can initially ask the admin user to create a project for him.

Apparently to solve this issue there is a setting in “AdministrationSystem settings>Projects(tab)”: “Role given to a non-admin user who creates a project”. There one can chose a role which is given to a user after he creates the project.
But this settings does not have any effect.

Luckily there is a work-around:
Apparently the user is always given the first role from the list for the projects he creates.
So all you have to do is to “swap” the roles: make the default “Project member” to a “Project administrator” and vice versa.
After that users become “Project administrators” of the projects they create with corresponding rights and there is no “403 forbidden” error anymore at creating a project.

@Developers: please consider to make the setting “AdministrationSystem settings>Projects(tab)”: “Role given to a non-admin user who creates a project” work (to make the system behave as expected) or please consider removing is (to make the system simpler). In the latter case the role “Project administrator” has to be moved to the first position in the list in default configuration.

If I’m missing something looking at this issue - please let me know:)

Regards,
Andrey