Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Complete administrator documentation is available here.

Adding a project

It is easiest to create a project after the groups and schemes have been created.

Create Groups

Follow the vendor directions for creating a group and adding people to a group. If you need to create new accounts, follow these instructions.

Best practices:

  • User names should be the netid for CU folks and the full e-mail address for non-CU folks.
  • Make unique groups for your project. Don't use existing groups.
  • Your group names should be XXXXXX-YYYYYYYYYY where XXXXXX is the Project Key that you will use when creating the project and YYYYYYYYYY is "administrators", "developers", and "viewers".
Create Permission Scheme

Follow the vendor directions for adding a permission scheme.

Best practices:

  • Make a unique Permission Scheme for your project. Don't use the default one.
  • Your permission scheme should be named XXXXXX-permissions where XXXXXX is the Project Key that you will use when creating the project.
Create Notification Scheme

Follow the vendor directions for adding an email notification scheme.

Best practices:

  • Make a unique Notification Scheme for your project. Don't use the default one.
  • Your notification scheme should be named "ZZZZZZZZZZ Notification Scheme" where ZZZZZZZZZZ is the Project Name that you will use when creating the project.
Create Project

Follow the vendor directions for creating a new project, selecting the Permission Scheme and Notification Scheme created above.

  • No labels