Welcome to
Help Desk

Product Updates
Training
Support
Ideas Contact Support

Project Templates

Follow

Project Templates make it easy to create new projects using a predefined folder structure and permission set.  

In addition to assigning permissions for pre-existing groups or users, project-specific groups can be created and assigned permissions on the folder structure at the time of project creation. The project-specific groups can then be populated with individual users giving them access to the respective project. 

You can set up different templates for different project types and choose who has access to use templates.

Project Templates are only available on the Project Control Add-On.

Creating a Project Template

Project Templates are stored in /Shared/Egnyte Templates/Project Templates.  Follow these steps to create a Project Template:

  1. Create a folder under /Shared/Egnyte Templates/Project Templates.  The name of your folder will be the template name.
  2. Add subfolders and files to the template
  3. (Optionally) Set any folder options (e.g. descriptions, link sharing controls, etc.) on the folders within the template
  4. (Optionally) Use Project Template Settings from the More menu to set a template description and configure the groups and permissions for the template.

    AEC_Project_Folder_Templates_1.png

The Project Template Settings dialog allows you to define Project Template Permissions via a JSON settings file.  A sample JSON file can be downloaded from the Project Template Settings dialog and gives examples of usage. 
AEC_Project_Folder_Templates_2.png

The following table describes the fields of the Permissions JSON object.

Field

Description

Required

Possible Values
folders Top-level key that contains the definition of folders and their permissions Yes Array of folder definition objects
folder.path The folder for which you want to set permissions Yes

Path, relative to the root of the project, e.g.:

  • /
  • /Design
  • /Accounting/Budget
folder.permissions Object with details about the permissions Yes See fields below. The structure is the same as is used in the Set Folder Permissions Public API
folder.permissions.groupPerms Object with details on groups and their permissions. No

An object where the keys represent group names and the values the permissions those groups should have.  Groups can be existing groups, e.g., “Finance” or dynamic groups, e.g., “{{projectId}} - Project Managers”, which will be created upon project setup.


Valid permissions include: None, Viewer, Editor, Full, Owner

folder.permissions.userPerms Object with details on users and their permissions. No

An object where the keys represent usernames and the values the permissions those groups should have.  


Valid permissions include: None, Viewer, Editor, Full, Owner
folder.permissions.inheritsPermissions Whether or not the folder should inherit permissions from its parent folder. No

true or false


Defaults to true

A sample permissions JSON is shown below:

{
   "folders": [
       {
           "path": "/",
           "permissions": {
               "groupPerms": {
                   "{{projectId}} - Project Managers": "Owner",
                   "Finance": "Viewer",
                   "{{projectId}} - Team": "Editor"
              }
           }
       },
       {
           "path": "/Budget",
           "permissions": {
               "groupPerms": {
                   "Finance": "Owner",
                   "{{projectId}} - Project Managers": "Full"
               },
               "userPerms": {
                   "bsmith": "Viewer"
               },
               "inheritsPermissions": false
           }
       },
       {
           "path": "/Budget/Forecasting",
           "permissions": {
               "userPerms": {
                   "jdoe": "Full"
               }
           }
       },
       {
           "path": "/External",
           "permissions": {
               "groupPerms": {
                   "{{projectId}} - External": "Editor"
               }
           }
       }
   ]
}

Supported JSON variables are: projectId, projectName

To control who can create new projects from your Project Template, set permissions on the template folder using the Share > Manage Folder Permissions dialog.  Any user with Viewer permissions on the template will be able to use it to create new projects within a destination folder to which they have Owner permissions.

Creating a Project from a Project Template

Use the following steps to create a new project from a project template:

  1. Navigate to a folder where you have Owner permissions
  2. From the New menu, choose Project from template

    AEC_Project_Folder_Templates_3.png

  3. Choose the template you would like to use and click Next

    AEC_Project_Folder_Templates_5.png

  4. Enter details about the project.  The Project name will be used as the folder name for your new project.  Depending on the template you choose, the Project ID may be required.  Click Next once you have entered the details about the project.

    AEC_Project_Folder_Templates_4.png

  5. Your new project is created. If your template created project-specific groups, you’ll see a list of those groups with an option to manage each group.  Clicking the Manage Group button will open the group details page in a separate browser tab.  Here you can add users to groups so that they get access to your new project.

    AEC_Project_Folder_Templates_6.png
Was this article helpful?
0 out of 1 found this helpful

For technical assistance, please contact us.