Application administrators of the Projects application can configure the admin side, ready for Projects to be created by users with permissions on the front end.
This guide will detail all the options available. It's recommended to set these up before Projects start to be created on the front end.
Admin side tabs
Head to Applications> Admin > Projects
- The 'Permissions' tab

Assign users/roles/groups permissions to perform desired actions:
- Create New Project: User(s) can add new projects
- Full Permission: User(s) can create, edit, delete, and view all projects (even if they have not been included in each project's permissions specifically)
- Add/Edit companies: User(s) to add and edit companies within your project.
Generally, administrators or responsible users who should have an overview of all projects will be given all permissions.
Users you wish to only be able to create and see their own projects (or projects they have been added to by others) give the 'Create new project' permission only.
As long as they add themselves to the project in a role with permissions to view, they will be able to make further edits.
- The 'Default project Roles & Rights' tab
Here, an administrator can set the Roles & Rights that will autopopulate for any Project created on the front end:

This prevents this manual work from being repeated in each Project if the general permissions needing to be set are the same.
Consider the Roles your Company needs across Projects and tweak these or rename them.
Consider what permissions each Role should have universally and set these.

Click 'submit' to apply any changes.
When Projects are created on the front end, the default Roles & Rights will pre-populate to speed up this process, but they can still be edited further by the Project creator if needed.
- The Files tab
Select the folder in the Documents application where Project files should be stored.
By default, the system creates a 'Projects' folder for use, but you can create your own and change the location on the admin side if preferred.

- Action for non-images: Choose what happens when users click on content in the project, whether it opens a preview or downloads immediately
- Always detailed upload: Check this box to ensure all file uploads will be given the extended list of fields to accompany them
- Open docs in new window: Check this box to ensure all clicks on files open in a new window (meaning users do not have to go back to view the project when browsing files)
- View Style: How files will appear across Projects, with file icons or as a list
- The 'Communication' tab
For the list of actions, choose which format of notification should be sent to users (who are included in Projects on the front end)
The choice is between what users have set in their notification preferences, or to override this and send the content as a daily digest-style email:
