Skip to main content

Step 1: Install the Connect Application

Last updated: May 15, 2026Latest Frontend Version: 2.17.3

Prerequisites​

The Connect Application runs either in an external browser (for debugging) or in the embedded browser (standalone application). You can obtain the Connect Application installer only from your host institution or the Tera Insights team.

tip

We recommend that new users choose the Connect Application over the browser version because new features, such as support for external SFTP and a local filesystem bridge to the Vault, are added to it.

caution

The Connect Application does not run on mobile devices or tablets.

Minimum Requirements
  • Processor (CPU): 8 cores.
  • Memory (RAM): 32 GB.
  • Operating System (OS): macOS or Windows; Red Hat Enterprise Linux 7 or 8, or equivalents such as CentOS or Springdale.
  • App Storage: 44.1 MB.
  • Machine Storage: based on intended use.
  • Graphics: based on intended use.
  • Network: Fiber-optic internet connection.
  • Supported browsers: Google Chrome or Mozilla Firefox.

Install the Connect Application on macOS​

  1. Open the Connect Application.dmg Installer provided by your institution or the Tera Insights team.
  2. In the prompt, click Continue.
  3. Review the required local machine storage and click Install.
  4. Enter your password when prompted.
  5. In the pop-up, click OK to allow access.
  6. Once the installation is complete, click Close.

Launch the Connect Application on macOS​

  1. Navigate to your apps and open the Connect application.
  2. Launch your deployment to connect to your institution’s secure enclave.
  3. In the new prompt, log in to the system.
Confirmations, Errors & Solutions
Email Account Activation Confirmation

Your account has been activated by an admin successfully.

Login Failed User

Login failed: No user exists with email the-email-you-entered.

Ask your Admin

Ask your admin to create a new account with the same email. In rare scenarios: if you use multiple institution deployments, you might have used a private key file from a different deployment. Check that the private key file corresponds to the associated deployment.

Login Failed Password

Login failed: The password for the private key is incorrect or is the wrong key file.

Re-Enter the Correct Password or Private Key File

You must re-enter your password and check that you have added the correct private key file locally.

Login Failed Timeline

Login failed: Too long since last login.

Ask Your Admin to Re-activate Your Account

If you have not logged in for a long time or your account has expired, your admin must re-activate your account.

Bad MFA

Bad MFA certificate: certificate is for different user.

Re-Login with Correct User ID

You entered a different credential in the MFA prompt. You must log in again with the same user ID.

Remaining Login Attempts

decreasing-number-from-8-to-0 login attempts remaining until account is locked. The next time you can log in is month-day-year, hour-minute-second AM/PM (date and time of next possible re-login).

Re-enter Your Password Later

You entered an incorrect password multiple times. You have 14 total attempts and are notified of 8 of them. You must wait until the indicated date and time to log in again. Your admin cannot help you in this situation.

Declined Terms & Conditions Upon Login

You clicked Decline in the T&Cs prompt.

Re-login and Accept Terms & Conditions

Go back to the login page and log in again as usual. Once logged in, click Accept in the T&Cs prompt.

Install the Connect Application on Windows​

  1. Open the Connect Application.exe Installer provided by your institution or the Tera Insights team.
  2. In the prompt, click Next.
  3. Click I Agree.
  4. Review the required local machine storage for the application, then click Next.
  5. Select a Start menu folder and click Install.
  6. Once the installation is complete, click Finish.

Launch the Connect Application on Windows​

  1. Navigate to your Start menu, then find and open Connect application.
  2. Launch your deployment to connect to your institution’s secure enclave.
  3. In the new prompt, log in to the system.
Confirmations, Errors & Solutions
Email Account Activation Confirmation

Your account has been activated by an admin successfully.

Login Failed User

Login failed: No user exists with email the-email-you-entered.

Ask your Admin

Ask your admin to create a new account with the same email. In rare scenarios: if you use multiple institution deployments, you might have used a private key file from a different deployment. Check that the private key file corresponds to the associated deployment.

Login Failed Password

Login failed: The password for the private key is incorrect or is the wrong key file.

Re-Enter the Correct Password or Private Key File

You must re-enter your password and check that you have added the correct private key file locally.

Login Failed Timeline

Login failed: Too long since last login.

Ask Your Admin to Re-activate Your Account

If you have not logged in for a long time or your account has expired, your admin must re-activate your account.

Bad MFA

Bad MFA certificate: certificate is for different user.

Re-Login with Correct User ID

You entered a different credential in the MFA prompt. You must log in again with the same user ID.

Remaining Login Attempts

decreasing-number-from-8-to-0 login attempts remaining until account is locked. The next time you can log in is month-day-year, hour-minute-second AM/PM (date and time of next possible re-login).

Re-enter Your Password Later

You entered an incorrect password multiple times. You have 14 total attempts and are notified of 8 of them. You must wait until the indicated date and time to log in again. Your admin cannot help you in this situation.

Declined Terms & Conditions Upon Login

You clicked Decline in the T&Cs prompt.

Re-login and Accept Terms & Conditions

Go back to the login page and log in again as usual. Once logged in, click Accept in the T&Cs prompt.

Install the Connect Application on Linux Fedora Version 40+​

  1. Open Fedora terminal.
  2. Run dnf install _url_to_rpm_.

Install the Connect Application on Linux Ubuntu Version 24+​

  1. Open Ubuntu terminal.
  2. Run wget _url_to_deb_.
  3. Then run dpkg -i local_downloaded_file.
note

The Connect Application does not run on versions of Linux other than those listed above.

Manually Add a New Front-End Version​

  1. Open the Connect Application from your desktop.
  2. In the window, click the Manage versions button in the top right (macOS)/left (Windows) corner.
  3. In the pop-up, click the Add version button in the top right.
  4. Click Upload szip. file to manually upload the new version.
  5. In the window, select the new version file, then click Open.
info

You may also paste the new version file link into the Paste a version URL field.

Manage Front-End Versions​

  1. Open the Connect Application from your desktop.
  2. In the window, click the Manage versions button in the top right (macOS)/left (Windows) corner.
  3. In the pop-up, select the appropriate front-end version.
  4. Click outside the pop-up to exit.
note

We recommend users always run the latest version, which is selected by default. Front-end versions are updated globally by default.

Delete Front-End Versions​

  1. Open the Connect Application from your desktop.
  2. In the window, click the Manage versions button in the top right (macOS)/left (Windows) corner.
  3. In the pop-up, click the Delete button next to the front-end version you want to delete.
  4. Click outside the pop-up to exit.

Add a New Deployment​

  1. Open the Connect Application from your desktop.
  2. In the window, click the Add deployment button in the top right (macOS)/left (Windows) corner.
  3. In the pop-up, click Upload dep. file to upload the deployment.
  4. In the window, select the deployment file, then click Open.
info

You may also paste the deployment file link in the Paste a deployment URL field.

Delete an Existing Deployment​

  1. Open the Connect Application from your desktop.
  2. In the window, click the Delete a deployment button in the top right (macOS)/left (Windows) corner.
  3. In the prompt, click Yes.
note

After deleting a deployment, you must re-add it to regain access.

info

You may delete a deployment when there are at least two existing deployments.

Deployment File Requirements for Connect Application Updates​

The same .dep file is required for any new version of the Connect Application because all versions use the same database.

If the .dep file is already loaded, the Connect Application recognizes it automatically.