Desktop

If you have access to multiple axiUm databases on your workstation, you can select which database to connect to.

Example: You have access to both Production and Training databases.

To select the database:

1. From the axiUm run folder, double-click the axium.exe file to launch axiUm.

A pop-up displays, allowing you to select the database connection.

Note: The database connection listed in the axium.ini file is the selected connection by default.



2. Select the database you want to connect to and click Start to display a login window.

Notes:

• An error displays if you attempt to connect to a different database version. If this occurs, contact your axiUm administrator.
• If you have write access to the axium.ini file, your choice is saved and displays as the default database connection next time you run axiUm.
• The PowerAdmin button displays if the application is in your axiUm run folder. If available, you can launch PowerAdmin with the selected database instead of the information stored in PowerAdm.ini file.
3. Proceed to Step 2 of Log In to axiUm.

The axiUm LiveUpdater utility allows you to immediately access and install axiUm patches to an instance on your workstation as they become available.

If configured and a patch is available when you launch axiUm, the axiUm LiveUpdater process begins:

• If the instance on your workstation is set to On Prompt, a message displays. Click Yes to proceed with the update or click No to cancel out of the LiveUpdater process and open axiUm with the current axiUm patch.



• If the instance on your workstation is set to Automatic, the axiUm LiveUpdater window displays automatically and updates the axiUm version.



When the update is complete, axiUm opens and you can log in.

Note: For workstation instances that do not use axiUm LiveUpdater, the previous update methods such as manually copying files or using the auto-update folder can still be used.

You must use your credentials to authenticate yourself and open axiUm.

1. From the axiUm run folder, double-click the axium.exe file to launch axiUm.
2. In the login window, enter your credentials as specified by your institution and click OK. These may include:

• axiUm username and password

• Swipe card / SmartCard

• Active directory

The axiUm desktop opens.

Note: If your level or workstation has a default module configured, that module loads.

Important: This feature is only available if enabled for your institution and Auth Service is installed. For more information, contact axiUm Support.

Organization-based sign-in is an optional authentication method that allows you to log in to axiUm using your organization's Identity Provider (IdP) with SAML or OIDC and multi-factor authentication (MFA). If enabled, axiUm securely redirects to your organization's sign-in page in your default browser and provides a splash screen that runs in the background to guide you through the authentication process in real-time.

Tip: If sign-in takes longer than expected, the Auth Service is unavailable, or your account has not been set up, axiUm offers options to retry, troubleshoot, or try a different account.

You must authenticate yourself to open axiUm.

To log in via organization sign-in:

1. From the axiUm run folder, double-click the axium.exe file to launch axiUm.

After axiUm loads, a splash screen displays and indicates that it is connecting to your organization. When successfully connected, the splash screen indicates you must complete sign-in from a browser window and automatically opens your organization's sign-in page in your default browser.



2. Enter your email address and click Continue or click the available link.



Note: The welcome text displays axiUm Web when logging in from a web app and axiUm Desktop when signing in from a workstation.

3. Finish signing in to your organization.

   1. If not already done, enter your email address and click Next.

   2. Enter your password and click Continue.

   3. If prompted, enter the code from your authenticator app and click Sign in.

The browser indicates that authentication is complete, allowing you to return to axiUm and begin your work from the axiUm desktop.

Tip: If your level or workstation has a default module configured, that module loads.



Note: Users that are linked with multiple axiUm accounts will return to the splash screen and are prompted to select an account from their available options.

When finished in axiUm, or if another user needs to use axiUm, you will need to log out of axiUm or close the application.

Note: Depending on configuration, if left inactive for a set period of time, axiUm auto-closes or returns you to the log in screen.

There are a variety of ways you can end your axiUm session:

• Switch axiUm users: Another user needs to perform a task while you are still working in axiUm.

Example:  An administrator must perform a task in axiUm that you cannot.

• Log out of axiUm: You are done working in axiUm but want to keep axiUm running.

Example: Another user may need to use axiUm directly after you.

• Close axiUm: You are done working in axiUm and want to close axiUm.

Example: Your session is finished, and no other users require the program.

If you used organization-based sign-in to log in to axiUm with Single Sign-On (SSO) is enabled, you will not be signed out of IdP when you close axiUm. Your authentication tokens will securely persist in Windows secure storage as long as your IdP session is still valid and you can relaunch axiUm while still within the session with no need to re-enter credentials or complete MFA. If your session has expired, you will be prompted to sign in as usual.

If SSO is disabled, tokens are held in application memory only. Closing axiUm performs a full sign-out and clears all your authentication and browser cookies. The next time you open axiUm, you will need to complete the full sign-in and MFA process.

Note: SSO is controlled on a per-workstation basis through an SSOEnabled Station Option. For more information, refer to the Desktop Setup Guide.

• In the upper-right corner of the desktop, click the X to close axiUm.

Note: If configured, this option may also return you to the log in screen.