Accessing Your Organization's Login

Each client on Pipeline has a specific subdomain to log in to the platform. Your administrator will provide you with the specific login URL. For example, if you organization has the subdomain example, you can login in at https://example.pipeline.us.

Note: We recently changed our domain name to pipeline.us. All of the domains in our ecosystem (ftocloud.com, fto.cloud, and trainwithpipeline.com) will automatically redirect to the correct page. Any saved sessions (i.e., if you checked "Remember Me" at login) that weren't not on the pipeline.us domain will need to signed back in. All links will redirect to the correct place.

Once you are on your organization's page, you can log in using the appropriate method. There are multiple login methods available for organizations. The various login methods are:

• Password/e-mail (default)
• Google Login
• Microsoft Login
• SAML 2.0
  • SP-Initiated
  • IdP-Initiated

Password & E-Mail Login

By default, all organizations will have a password/email combination for login. Simply enter your e-mail and password and click "Log In".

Google & Microsoft Login

Organizations that use Google for Business or a Microsoft Business product (e.g., Office 365) can request that the Google/Microsoft integration be activated on their account. With this, simply click on the button to sign in using Google. Then, choose the appropriate account.

If you do not yet have an authorized account and your organization has disabled JIT-provisioning, you will receive an error message. Please contact your organization administrator to have them verify that the email you are using to log in matches the one on your Google account.

Note: Due to security reasons, Pipeline cannot update your email address. Only an administrator from your organization can make this change.

SAML 2.0 Login

Pipeline allows organizations to enable the highest level of enterprise security while allowing integration with existing tools through the use of SAML 2.0 authentication.

SP-Initiated

The typical use case for SAML 2.0 is SP-initiated authentication. In this model, your organization will have a Single Sign-On link on the login page that will guide you through your organization's login. In most cases, both registration and login will be disabled so you will likely only see one link:

IdP-Initiated

While less common, Pipeline also supports IdP-initiated SSO. For this case, you will need to be authenticated within your organization's identity provider (e.g., Okta, JumpCloud, Azure AD, etc.). Then, simply click the link to follow the login to Pipeline: