Skip to content

Project Template

Introduction

Project Templates allow Site Admins to configure which custom roles are available for Projects within a Group. Creating a Project Template allows you to:

  • Simplify the roles available for Project Admins to assign to users
  • Automatically add users to all Projects under a Group
  • Standardize roles across Projects
  • Ensure that all new Projects created in a Group have the correct roles by default

This article explains how to configure a Project Template.

Instruction Steps

To configure a Project Template:

  1. Sign into Flywheel as a Site Admin.

  2. Go to Groups, and select a Group.

  3. Click the Project Template tab.

    ProjectsTemplate-export.png

  4. Click Add.

  5. Select a user and assign a role for that user.

    adduser

    Note: To assign a custom role to a user, the role must first be offered to the group. Learn more about creating or editing a custom role.

  6. Choose to either add the user to all projects in a group, or allow the Group or Project Admins to assign the user to specific projects.

Roles and Permissions Considerations

Flywheel gives you granular control over who has access to data in different areas of the Flywheel hierarchy. Below is an overview of the 3 different roles that apply to each user.

Flywheel users can see, edit, or delete data based on their roles and permissions.

  • Permission: Enables or disables the ability to perform a specific action in Flywheel. For example, adding notes to a Project is a specific permission.
  • Role: A group of permissions that are assigned to a user. For some roles you can edit the permissions.

Roles can be assigned at the Site, Group, and Project levels. All users have a role assigned at each of these levels:

  • Site role: These roles are broad and assigned when you create a new user. In general, these roles match what the user is doing in Flywheel at a high level. The available site roles are Site Admin, Developer, and User. Pair these basic site roles with the more granular roles assigned at the Group and Project levels.
  • Group role: Group roles give users broad permissions for what they can do within a Group. The available group roles are Admin, read-write, and read.

    Assigning a Group role does not automatically add users to Projects in that Group.

  • Project role: By default, Projects have Admin, read-write, and read-only permissions. However, Site Admins can create customized project roles for each project. Custom project roles give you the flexibility to only give users access to the data they need. Learn more about creating or editing a custom role.

If you only want a user to see certain projects under a Group, you can assign the user a role in the Project without giving the user a Group role. To give the user access to a Project, but not the Group associated with the Project, add them from the Permissions screen of the Project.