---
title: Access & Login Methods
description: Automated User Verification (also known as Seamless Login) Vim automatically identifies and authenticates EHR users in the background—no separate login credentials or screens required. This feature en
---

[Skip to content](https://knowledgebase.getvim.com/home/access-login-methods#main-content)

[![Logotype-primary (1).png\]](https://knowledgebase.getvim.com/hs-fs/hubfs/Knowledge%20Base/Logotype-primary%20(1).png?height=50&name=Logotype-primary%20(1).png)](https://knowledgebase.getvim.com/home?hsLang=en)

Open main navigation

Close main navigation

- [Console](https://console.getvim.com/organization-admin/accounts?iss=https%3A%2F%2Fauth.getvim.com%2F)

[Console](https://console.getvim.com/organization-admin/accounts?iss=https%3A%2F%2Fauth.getvim.com%2F)

 Hello! How can we help you use Vim?

- There are no suggestions because the search field is empty.

1. [Practice Knowledge Base](https://knowledgebase.getvim.com/home?hsLang=en)
2. [User Resources](https://knowledgebase.getvim.com/home/user-resources?hsLang=en)
3. [Vim Terminology](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#vim-terminology)

# Access & Login Methods

---

**Automated User Verification** *(also known as Seamless Login)*  
Vim automatically identifies and authenticates EHR users in the background—no separate login credentials or screens required.  
This feature enables users to access Vim Connect instantly upon launching the EHR.

> *Note: Availability depends on EHR configuration and may not be supported in all systems.*

**Single Sign-On (SSO)**  
Users log in using existing clinic credentials (e.g., Microsoft, Okta) without needing a separate Vim username or password.

**Organization Key**  
A unique identifier assigned to a practice during technical implementation. It’s used once to link the clinic’s EHR to Vim during setup.

**Manual Login**  
Users log in by entering a Vim-issued password or a one-time password. Typically used by smaller or independent practices without SSO.

**Auto-Created User**  
A Vim user account automatically generated when someone with **Vim Connect installed** launches it from their EHR for the first time. This process—called **User Auto-Creation**—requires no manual setup by an admin and helps streamline onboarding for clinical users.

**Two-Factor Authentication (2FA)**  
A security measure for Console access requiring a secondary verification step via email or text message.

**Activation**  
The process of enabling Vim Connect or specific applications for a user or organization.

**Deployment**  
The installation of Vim Connect across clinic devices so users can access workflows within the EHR.

- [Welcome to Vim](https://knowledgebase.getvim.com/home/welcome-to-vim?hsLang=en#main-content)

    - [How Vim fits into clinical workflows](https://knowledgebase.getvim.com/home/welcome-to-vim?hsLang=en#how-vim-fits-into-clinical-workflows)
    - [Vim Canvas Marketplace overview](https://knowledgebase.getvim.com/home/welcome-to-vim?hsLang=en#vim-canvas-marketplace-overview)
- [Onboarding](https://knowledgebase.getvim.com/home/onboarding?hsLang=en#main-content)

    - [Getting Started](https://knowledgebase.getvim.com/home/onboarding?hsLang=en#getting-started)
    - [Technical Implementation](https://knowledgebase.getvim.com/home/onboarding?hsLang=en#technical-implementation)
- [Applications](https://knowledgebase.getvim.com/home/applications?hsLang=en#main-content)

    - [Care Insights](https://knowledgebase.getvim.com/home/applications?hsLang=en#care-insights)
    - [Clinical Data Exchange (CDE)](https://knowledgebase.getvim.com/home/applications?hsLang=en#clinical-data-exchange-cde)
    - [Enhanced Eligibility](https://knowledgebase.getvim.com/home/applications?hsLang=en#enhanced-eligibility)
    - [Prior Authorization](https://knowledgebase.getvim.com/home/applications?hsLang=en#prior-authorization)
    - [Order Assist](https://knowledgebase.getvim.com/home/applications?hsLang=en#order-assist)
    - [Vim Scribe](https://knowledgebase.getvim.com/home/applications?hsLang=en#vim-scribe)
- [User Resources](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#main-content)

    - [Vim Connect Users (For end users in the EHR)](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#vim-connect-users-for-end-users-in-the-ehr)
    - [Vim Console Admins & Owners (For practice admins managing Console access)](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#vim-console-admins-owners-for-practice-admins-managing-console-access)
    - [Vim Terminology](https://knowledgebase.getvim.com/home/user-resources?hsLang=en#vim-terminology)
- [How-to Guides](https://knowledgebase.getvim.com/home/how-to-guides?hsLang=en#main-content)

    - [Console Guides](https://knowledgebase.getvim.com/home/how-to-guides?hsLang=en#console-guides)
    - [Vim Connect Guides](https://knowledgebase.getvim.com/home/how-to-guides?hsLang=en#vim-connect-guides)
- [Help Center](https://knowledgebase.getvim.com/home/help-center?hsLang=en)
- [Get Involved](https://knowledgebase.getvim.com/home/get-involved?hsLang=en#main-content)

    - [Practice Experience Advisory Team (Invitation Only)](https://knowledgebase.getvim.com/home/get-involved?hsLang=en#practice-experience-advisory-team-invitation-only)
    - [Champion Program (Vim Console Admins & Owners)](https://knowledgebase.getvim.com/home/get-involved?hsLang=en#champion-program-vim-console-admins-owners)

[![Logotype-primary (1)](https://knowledgebase.getvim.com/hs-fs/hubfs/Knowledge%20Base/Logotype-primary%20(1).png?width=75&height=32&name=Logotype-primary%20(1).png "Logotype-primary (1)")](https://getvim.com/wp-content/uploads/2022/05/Transparent-logo.svg)

[getvim.com](https://getvim.com/)

Copyright © 2026, Vim