Getting Access to REDCap

The REDCap software is operated independently by individual institutions. Even if you have a REDCap account at another institution (e.g., Mayo, another university), you will need to access ASU’s REDCap using the link provided. Having access to multiple REDCap platforms is an option. However, it may be difficult to keep track of data and there is the potential for different versions of REDCap when using multiple platforms.

Gain access and/or request an account to each instance using the links below

Enterprise REDCap

Access to REDCap is for researchers, data collectors, project staff and affiliated students. Participants do not need access to REDCap. Bookmark this URL: https://redcap.rc.asu.edu/redcap/ Or click on the button below.

HIPAA REDCap

Access to REDCap is for researchers, data collectors, project staff and affiliated students. Participants do not need access to REDCap. Bookmark this URL: https://esr.asu.edu/ Or click on the button below.

User Account Policies

Users need to be entered into a REDCap system prior to accessing or creating any projects. The user requesting an account will receive an account creation email containing links to establish a password. After the user has access to the REDCap system, the user will also need to be added to any projects for which they are not the creator/owner.

REDCap@ASU organizes users into a hierarchical structure. This approach is beneficial as it improves system security by allowing research teams to extend access for users still involved in a project.

Types of REDCap User Accounts

Principal Investigators (PIs): PIs usually have an oversight role in REDCap, but this depends on the faculty’s research team structure. PIs have the responsibility to ensure their research team has appropriate access to the system and that personnel and students are appropriately removed from projects when their role has expired. PIs must be sponsors of non-ASU collaborators, research staff, and students or delegate this responsibility to a Project Coordinator (PC). If you are the PI, you or the PC will be the sponsor for your research team. You can manage your team account in your Sponsor Dashboard.

Project Coordinators (PCs): PCs oversee the design and implementation of REDCap projects and typically oversee student and faculty (ASU and non-ASU) collaborations. If you are the PC, you will be the sponsor for your research team if determined by the PI. You can manage your team account in your Sponsor Dashboard.

Project Staff: project staff conduct special activities, usually in conjunction with the PCs. Typical responsibilities include interacting with participants to obtain consent or study data or customizing REDCap project pages to improve the participant or researcher interface, or developing specialized code to allow REDCap to interact with other programs (API). Project staff can work alongside the PCs to oversee students as well. Your PI or PC will be able to manage your account and project access.

Research Assistants and/or Students: RAs and students are typically involved with consenting or collecting participant data as well as similar activities as project staff. Your PI or PC will be able to manage your account and project access.

Non-ASU personnel: non-ASU personnel includes any faculty, staff, or student that is not in the ASU system, such as a non-ASU consultant, faculty from another institution collaborating on the project, or students/staff from a different institution for a multi-site project. Your PI or PC will be able to manage your account and project access.

Account Expirations

Two weeks prior to expiration or suspension the user and sponsor will receive an email notification. The sponsor then has the ability to extend the account through the Sponsor Dashboard. This allows the faculty to have full control over who has access to their study data

Faculty/Sponsor accounts will need to be renewed annually by June 30th of each year.

Non-ASU or ASU student accounts will need to be renewed 3 times per year (December 15, April 15, August 15).

Auto-suspension of any user occurs after an inactive period of 365 days (182 days in the HIPAA instance).