Requirements

Introduction

Requirements are created and managed by the organization, and can be assigned to different access levels on a permission group. In order for a user to access data at a particular level, they must have been approved for all requirements up to that level.

All requirements can include instructions as well as a customizable form for collecting relevant information from users.

Types of requirements

There are three general types of requirements. You'll have to choose which type you want when you create it. This can't be changed later.

User requirement

A user requirement is fulfilled by a user once for the entire organization. User requirements can be set to either auto-approve or require administrator approval, and can be set to expire at a certain date.

Study requirement

A study requirement is the same as a user requirement, with the exception that it is fulfilled on behalf of a study, not a user.

Authentication requirement

A user requirement in which you can set up an automatic check for information on users profiles. Currently this can be used to verify a user's institution affiliation.

Creating and editing

Requirements are created and managed within the "Requirements" tab of the administrator panel. All requirements must have a name that is unique within the organization.

Requirements can also have optional instructions and/or a form associated with them. The form provides an interface to collect both structured and unstructured user input, as well as signatures and uploaded files.

Requirement settings

You can configure any requirement with details about how it is approved and what that approval means

This requirement needs to be approved by an administrator

When turned on, all submissions will be marked as "pending" until an administrator from you organization responds to it. When turned off all submissions are automatically approved.

Approvals of this requirement expire after a period of time

When turned on you can choose to set a default expiration based on a form field or the date of the requirement's approval. You can override this default when approving the requirement. When turned off you will not be able to assign an expiration to requirements and once approved they will always be approved unless you individually revoke them.

Approvals of this requirement apply only to specified datasets

When turned on extra section will be generated on this requirement listing all datasets it is assigned to. Datasets will need to be individually selected for this requirement to be applicable to them once approved. When turned off, it will by default apply to every dataset in your organization.

Approving requirements

When a requirement is submitted, if it requires approval it will trigger an alert on the corresponding member or study. You can resolve this alert by either approving or rejecting the requirement.