Setting it to 'no' will allow only Administrators to create new projects and will provide a 'Request New Project' feature to users, where they can send a request to an admin that a project be created for them.

Setting it to 'no' will allow only Administrators to move projects to production and will provide a 'Request To Move to Production' option to users, where they can request to an admin that a project be moved to production.

If a user creates a new instrument while a project is in production, you may choose whether all users in the project will have 'No Access' rights to the new instrument(s) by default or if they will instead have 'View & Edit/Full Data Set' rights to the new instrument(s) by default. NOTE: This applies to ALL projects, and the user access right selected above gets set automatically after the draft mode changes are approved.

This setting can be used to notify admins whenever new users enter the system. Table-based users are not included because their accounts are created by an administrator.

The "welcome" email will consist of the following stock text:

If the option is set to allow only selected users to generate API tokens, then any given user can be given this privilege on the Browse Users page when modifying their user account settings.

If enabled, users that have not logged into REDCap or used the API in the past X number of days (specified above) will automatically have their account suspended and (if set to Yes above) will be notified via email of their suspension. If the user has a sponsor (i.e., secondary contact) listed on their account, the sponsor will be CC'd on the email so that they are aware. Please note that if a user has been UNsuspended by an administrator within the period of inactivity, then the user will NOT get auto-suspended.

NOTE: If using 'LDAP & Table-based' authentication, there will appear an additional choice above to enable auto-suspension only for Table-based users.

Regarding user expiration times, if a sponsor requests to extend a user's expiration time for their account, it will add the amount of days above to their existing expiration time. And if the sponsor is setting the expiration time (as opposed to extending it), then it will calculate the expiration time using the value above added to today's date.

Explanation of options for enabling the UAD:
Disabled - UAD page is hidden and not accessible to users.
Enabled: Notification on page - Displays text on the My Projects page to remind users to visit the UAD page periodically.
Enabled: Notification and warning on page - Displays text on the My Projects page to remind users to visit the UAD page periodically, and if the user has not visited the UAD during the current calendar month, it will display the notification in red to alert them to visit the UAD soon.
Enabled: Notification and warning on page + Monthly email reminder - Displays text on the My Projects page to remind users to visit the UAD page periodically, and if the user has not visited the UAD during the current calendar month, it will display the notification in red to alert them to visit the UAD soon. This option will also send an email reminder on the first weekday of every month to remind users to visit the UAD.

If enabled, users can be granted privileges (via the User Rights page) to edit survey responses that have been either partially or fully completed by a survey respondent.

NOTE: For all options above, a REDCap administrator is still required to review changes made in Draft Mode if any critical issues exist AND the project contains one or more records.

Explanation of options above:
The options above go from most strict to least strict (top to bottom) with regard to when they allow automatical approval. If option 1 is selected, REDCap admins will always have to review and approve all production changes made by users. Option 2 will permit auto-approval ONLY if new fields are being added to the project (or if fields are simply reordered), while Option 3 will permit auto-approval if the project has no records OR if only new fields are being added (i.e. no existing fields were modified). Option 4 will NOT permit automatic approval if any critical issues exist (e.g., fields deleted, multiple choice options deleted, field type changed), while Option 5 will NOT permit automatic approval if BOTH the project has records AND critical issues exist. NOTE: If a project has no records, then the auto-approval process will behave just the same if using either option 3 or 5; however, options 3 and 5 behave very differently if a project does contain one or more records.

NOTE: Even if set to 'Yes', Administrators will still be the only ones who can delete events while in production. Additionally, if set to 'Yes', normal users will be able to designate instruments to events on the 'Designate Instruments For My Events' page that have not yet been designated, but they will not be able to un-designate any instruments that are already designated.

Separate each domain on a different line. See example below.

vanderbilt.edu
mc.vanderbilt.edu
mmc.edu

This feature may be used in environments that restrict users in certain ways (e.g., 21 CRF Part 11 environment). Normal users will still be able to edit their email address or (when using Table-based authentication) reset their password, and Administrators will still be able to edit their first/last name regardless.

This feature may be used in environments that restrict users in certain ways (e.g., 21 CRF Part 11 environment). Normal users will still be able to (when using Table-based authentication) reset their password, and Administrators will still be able to edit their primary email address regardless.

NOTE: Tabled-based users will have their individual value set manually by an administrator when their account is created, so this primarily applies to external authentication methods (e.g., LDAP, Shibboleth).

Before a user or admin (depending on the selection above) makes a report public, they must do and agree to ALL of the following:

1. Must view the report being made public beforehand.
2. Must acknowledge that they understand that making the report public means that all data in the report will be fully accessible to anyone with the public link to the report.
3. Must acknowledge that they are responsible if any private, sensitive, or identifying data in the report is exposed to persons who should not have access to such data.

If set to allow public dashboards after approval by an admin, the admin will receive the request from the user via the To-Do List page (or via email, if setting is enabled), and after the admin approves/disapproves the request, the user will receive an email regarding the response to their request.

For privacy reasons, you may adjust the minimum amount of data points required when viewing a public project dashboard, public report, or survey page that contains Smart Charts, Smart Tables, or Smart Functions. Thus if any given Smart Chart, Smart Table, or Smart Function on a public project dashboard, public report, or survey page does not meet the minimum requirements, it will not output the chart, table, or value, respectively, but will instead output the text '[INSUFFICIENT AMOUNT OF DATA FOR DISPLAY]'. Note: This privacy setting does not apply to dashboards or reports being viewed from inside a REDCap project but only when viewing them via their public link.