NOTE: Enabling this setting will only display the button for modules that have been made 'Discoverable' in the system.

When enabled, REDCap provides the option to use the URL shortening service named REDCAP.LINK to shorten or customize public survey links, links for public project dashboards, and public report links. This service is hosted by Vanderbilt on AWS. If your server is behind a firewall and cannot make outbound HTTP requests to websites on the web, then you should disable this service.

When enabled, it will display the option to utilize the Randomization module for new or existing projects. When disabled, the option will remain completely hidden, and the Randomization module will stay hidden in each project and cannot be used.

Allows users to download forms from the REDCap Shared Library to import those forms into their project on the Online Designer page.

REDCap Messenger is a communication platform built directly into REDCap. It allows REDCap users to communicate easily and efficiently with each other in a secure manner. At its core, REDCap Messenger is a chat application that enables REDCap users to send one-on-one direct messages or to organize group conversations with other REDCap users.

The REDCap API is an interface that allows external applications to connect to REDCap remotely, and is used for programmatically retrieving or modifying data or settings within REDCap, such as performing automated data imports/exports from a specified REDCap project. For details on the capabilities of the REDCap API and how to use it, please see the REDCap API help page.

The REDCap Mobile App is an app that can be downloaded onto a tablet or mobile device to allow REDCap data to be collected locally on that device without the need for an internet connection (either wifi or cellular signal). If a user downloads the app, they must explicitly be given mobile app privileges in a given REDCap project in order to set up the project on the app. Once a project has been set up on the app, data can be collected in an offline fashion and then later synced back to the REDCap server.

e.g., /var/www/redcap/modules_staging/|/var/www/redcap/modules_internal/

e.g., C:\xampp\htdocs\redcap\modules2\

If disabled here, then users will not be able to utilize this feature in their projects. If enabled, then users may enable it for a project via the Additional Customizations popup on the Project Setup page.

If disabled here, the 'Import from Field Bank' button will be hidden in the Online Designer for all users.

If enabled, the Online Designer will allow users to supply a video URL for a Descriptive field on a form or survey, in which it will provide a button that, when clicked, will play the embedded video inside a popup dialog. This features allows any video URL to be used from any video hosting website (although it is most compatible with YouTube and Vimeo).

This features allows users to enable text-to-speech functionality in any given survey, in which text on the survey page can be read out loud audibly by the computer. This service utilizes a service hosted at Vanderbilt University that utilizes the IBM Watson Text-to-Speech API service, and thus will send all displayed survey text (e.g., survey instructions, field labels, choice labels) from the REDCap server to the Vanderbilt-hosted service. This means that the REDCap web server must be able to make outbound HTTP requests to https://redcap.vumc.org in order for this service to work.

This service utilizes the BioPortal API web service (see documentation at http://bioportal.bioontology.org). For this feature to work, the REDCap web server must be able to make outbound HTTP requests to https://data.bioontology.org/. If you do not yet have a BioPortal API token, you can obtain a token here. The service will not function without a valid API token.

The Data Entry Trigger is an advanced feature. It provides a way for REDCap to trigger a call to a remote web address (URL), in which it will send a HTTP POST request to the specified URL whenever *any* record or survey response has been created or modified on *any* data collection instrument or survey in this project (it is *not* triggered by data imports - including API imports and Mobile App imports - but only by normal data entry on surveys and data entry forms). Its main purpose is for notifying other remote systems outside REDCap at the very moment a record/response is created or modified, whose purpose may be to trigger some kind of action by the remote website, such as making a call to the REDCap API. View more details

If enabled (default), users will be able to download a backup of their entire project as a single XML file (CDISC ODM format), which could be used to create a clone of the project (including its data, optionally). This option will be shown on the Other Functionality tab of the 'Project Setup' page and also on the Other Export Options tab of the 'Data Exports, Reports, and Stats' page.

This setting prevents identifying data (PHI/PII) from being sent in outgoing emails for alerts, survey invitations, and survey confirmation emails. If enabled here at the system-level, users will see an option in the Additional Customizations dialog on the Project Setup page to allow them to enable the Protected Email Mode in their project. If this feature is then enabled in a project, either A) all alerts, survey invitations, and survey confirmation emails or B) those whose email body is attempting to pipe data from Identifier fields will be affected, in which it will not send the full email text to the recipient but will instead send a surrogate email containing a link that leads them to a secure REDCap page to view their original email. The recipient clicking the link allows them to navigate to a secure REDCap page where they may view the original email. If they are accessing an email in the Protected Email Mode for the first time (or in more than a month), it will send a security code to their inbox that will allow the recipient to view any protected emails for up to 30 days on that same device.

If enabled, users with User Rights privileges in a project will be able to opt-in to using the Email Logging page, which will allow them to search and access all outgoing emails for the project. This can be useful for troubleshooting potential issues related to emails. If this feature is disabled here, all outgoing emails will still be stored in the backend database, but they will not be accessible to users via the user interface.

If enabled, users with "Delete Records" privileges in a project will be able to delete multiple records at a time or specific instruments of data for a set of selected records.

You might wish to disable this feature if you are not using Table-based, LDAP, or LDAP+Table-based authentication since the e-signature feature will not work for certain external authentication methods (e.g., Shibboleth, OAuth2).

If disabled, the image icon will not appear in the rich text editor, and thus users will not be able to embed images in its text.

If disabled, the attachment icon will not appear in the rich text editor, and thus users will not be able to embed file attachments in its text.

NOTE: This feature requires that the ImageMagick PHP extension be enabled.

The REDCap DTS module allows data to be pushed into REDCap projects from external systems (e.g., electronic medical record system, electronic data warehouse) and provides an adjudication process whereby REDCap users approve all incoming data from DTS before it is officially saved in their REDCap project. DTS must be installed and configured beforehand in order for it to function when enabled on this page. Once enabled globally here, DTS can then be enabled for individual REDCap projects on the Edit Project Settings page. For installation and setup instructions, please contact the developers at Oregon Health & Science University that created DTS.

The CATs are generated dynamically using the API software developed by the Assessment Center. NOTE: The data sent from REDCap to the Assessment Center API service hosted by Vanderbilt University is de-identified and cannot be connected back to any individual respondent.

Note: In order to use the Twilio service, the REDCap web server must be able to make outbound HTTP/HTTPS requests to the following URL: https://api.twilio.com. Additionally, your REDCap server must be publicly available to the web (in the DMZ) so Twilio's web servers can make requests to it. Otherwise, Twilio cannot completely function. For more information on Twilio, see https://www.twilio.com.

If 'Only Administrators' is selected, then normal users will not even see the setting on the project's Project Setup page (only Administrators will be able to see it and enable it). If 'All users' is selected, then any user with Project Design/Setup privileges in that project can see the setting and can also enable it on their own to utilize Twilio services in their project.

If 'No' is selected, then Twilio SMS and voice call services will not be advertised to users on the Project Setup page, and all information about Twilio will never be displayed anywhere in a project. Setting it to 'No' is preferable if you wish to make Twilio services known to only a limited number of users without advertising it to all users.

Note: In order to use the Mosio SMS service, the REDCap web server must be able to make outbound HTTP/HTTPS requests to the following URL: https://api.mosio.com. Additionally, your REDCap server must be publicly available to the web (in the DMZ) so Mosio's web servers can make requests to it. Otherwise, Mosio cannot completely function. For more information on Mosio, see https://www.mosio.com.

If 'Only Administrators' is selected, then normal users will not even see the setting on the project's Project Setup page (only Administrators will be able to see it and enable it). If 'All users' is selected, then any user with Project Design/Setup privileges in that project can see the setting and can also enable it on their own to utilize Mosio SMS services in their project.

If 'No' is selected, then Mosio SMS services will not be advertised to users on the Project Setup page, and all information about Mosio will never be displayed anywhere in a project. Setting it to 'No' is preferable if you wish to make Mosio SMS services known to only a limited number of users without advertising it to all users.

Note: In order to use the SendGrid service, the REDCap web server must be able to make outbound HTTP/HTTPS requests to the following URL: https://api.sendgrid.com/v3. For more information on SendGrid, see https://sendgrid.com.

If 'Only Administrators' is selected, then normal users will not even see the setting on the project's Project Setup page (only Administrators will be able to see it and enable it). If 'All users' is selected, then any user with Project Design/Setup privileges in that project can see the setting and can also enable it on their own to utilize SendGrid services in their project.

If 'No' is selected, then SendGrid Template email services will not be advertised to users on the Project Setup page, and all information about SendGrid will never be displayed anywhere in a project. Setting it to 'No' is preferable if you wish to make SendGrid services known to only a limited number of users without advertising it to all users.

NOTE: This option enables the module for every REDCap project.

When this option is enabled, users creating a survey can set the option for survey respondents to view ALL survey results in aggregate graphical format and/or as descriptive statistics after the respondent has completed the survey. This option appears when a user clicks the Set Up Survey or Modify Survey Settings button on the Project Setup page.

(option will be located in the Online Designer)

HTML may be used in order to adjust the style of the text or to display links, images, etc.

If set to 'Yes', then users will be able to choose email-validated text fields in the multi-select when setting an alert's To, CC, or BCC. Administrators will always be able to do this in a project regardless of this setting.

If set to 'Yes', then users will be able to manually type *any* email address for an alert's To, CC, or BCC. Administrators will always be able to do this in a project regardless of this setting.

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

vanderbilt.edu
mc.vanderbilt.edu
mmc.edu

If set to 'Yes', then users will be able to choose phone-validated and integer-validated text fields in the multi-select when setting an alert's recipient phone numbers. Administrators will always be able to do this in a project regardless of this setting.

If set to 'Yes', then users will be able to manually type *any* phone number for an alert's recipient phone numbers. Administrators will always be able to do this in a project regardless of this setting.

Note: By enabling this, it will NOT be auto-enabled in any projects. It is disabled by default for all projects. Users with 'Project Setup & Design' rights will need to enable this feature in the Additional Customizations popup on a project's Project Setup page.

For WebDAV, the hostname must begin with http:// or https:// (e.g., https://ebldav.mc.vanderbilt.edu), but not for SFTP (e.g., sftp.vumc.org). SFTP always assumes port 22, while WebDAV is port 80 or 443.

Note: By enabling this, it will NOT be auto-enabled in any projects. It is disabled by default for all projects. Users with 'Project Setup & Design' rights will need to enable this feature in the Additional Customizations popup on a project's Project Setup page.

For WebDAV, the hostname must begin with http:// or https:// (e.g., https://ebldav.mc.vanderbilt.edu), but not for SFTP (e.g., sftp.vumc.org). SFTP always assumes port 22, while WebDAV is port 80 or 443.

For WebDAV, the hostname must begin with http:// or https:// (e.g., https://ebldav.mc.vanderbilt.edu), but not for SFTP (e.g., sftp.vumc.org). SFTP always assumes port 22, while WebDAV is port 80 or 443.