Before you begin
You'll need access to your practice's token file.
This change does not affect users who are already logged in—your cached token continues to work until you log out, clear the cache, or open the app on a new workstation.
How to log in with a token file
If you open the desktop app and see the login screen pictured below (no saved token is present), use one of the following three options:
On the desktop app login screen (not the browser), choose one of the following methods:
File selector: Click Select Token File to navigate to the location where your token file is saved, then select it.
Drag-and-drop: Drag the token file from your file explorer and drop it onto the login screen.
Manual entry: Copy the token text and paste it into the manual entry field on the login screen.
The app authenticates automatically after the token is loaded.
Note: After you log in successfully, the app saves your token locally. Future launches will sign you in automatically without needing to select the file again. |
Where to find your token file
Your token file can be stored on a local disk, a mapped network drive, or a folder on a workstation—the file selector supports all of these. Ask your IT team or practice Admin if you're unsure where your practice's token is stored.
What to do if the login fails
If you see the following error after selecting a token file:
"The credentials for practice <practice-id> are not valid. Canceling authentication."
Check the following:
Confirm you selected the correct token file (not a similarly named file).
Verify the token hasn't been updated or decommissioned—if it has, you'll need the updated token from your IT team or a practice Admin.
If the file appears damaged or unreadable, contact Instinct.
Important: Instinct can only send token links to a practice Admin. |
For technical teams or practice administrators
Token files can remain wherever you currently store them: local disk, mapped network drive, or managed file share. The app uses the standard file picker and handles mapped paths normally.
You no longer need to coordinate with Instinct to register a custom token path. Any previously registered paths will stop being used and will be removed from Instinct's systems once this update completes.
Make sure staff know where the token file is saved so they can select it on first launch on any given machine.
Frequently asked questions
Will existing users be logged out when this update ships?
No. Users who are already logged in will not be affected. The new login screen only appears after a logout, cache clearing, or first launch of the app on a new workstation.
Does this require manually updating the desktop app?
No. The change applies automatically when the app loads—no manual update is needed.
Do we need a new token?
No. Your existing practice token works with the new login flow. Only the method for locating the token has changed.
What happened to the Start Auto Login button?
It has been removed. The app no longer scans local file paths for tokens. Manual selection via file selector, drag-and-drop, or manual entry replaces that flow.
Can we still use drag-and-drop?
Yes. Drag-and-drop and manual entry are unchanged. The file selector is a new addition, not a replacement.
Still need help?
Contact support via live chat or email [email protected].