Introduction
Deploying Sanas across your team provides a fast, efficient, and centrally managed setup experience, allowing users to get started without configuring the application themselves. By rolling out the app centrally, administrators can pre-assign users to the appropriate groups, enforce the organization's authentication method, and seamlessly deploy updates—eliminating the need for users to manually install, configure, or update the application.
Who can use this?
Plan: All Sanas Plans (Admins)
Managed from: Sanas Portal + Endpoint Management Software
Below are the deployment processes depending on your organization’s operating system:
Stratodesk NoTouch OS
Stratodesk NoTouch OS is a Linux-based, read-only operating system. On NoTouch OS, Sanas is deployed using an application distribution link instead of a traditional installer package. This deployment method ensures that endpoints always receive the latest Sanas features and updates automatically, eliminating the need for administrators or end users to manually install or update the application.
Note: Sanas works with both server-hosted (VDI) and self-hosted NoTouch OS.
Before You Begin
NoTouch Center access
You'll need admin access to NoTouch Center, the centralized management console for app deployment.
OS version
Stratodesk provides prebuilt support for Sanas on:
Component
Minimum Version
NoTouch OS
3.7.154 and above
NoTouch Center
4.5.696 and above
Deployment Steps
Get the Sanas app distribution link. Contact Sanas Support to request your link. It is required before you can configure the deployment.
Configure the distribution link on NoTouch Center.
Access NoTouch Center and log in with your credentials.
Navigate to Group Settings in the left-side menu.
Click New Connection in the selected group.
Select Sanas under Connection Mode.
Enter the app distribution link under Connection target.
Enable Automatic start at system reboot.
Enable Icon on desktop.
Click Save, then click Announce to push the deployment to all connected endpoints.
Note: Two endpoint restarts are required for a successful deployment. The first restart will display the Announce message, and the second restart will introduce the Sanas package.
Configure app users for Stratodesk:
Authentication mode — Set to UAK (Unique Authentication Key). See Logging In to the Sanas App for a comparison of authentication modes.
Add app users — Users need a User ID and Group ID to authenticate. See Manage App Users.
For a full walkthrough with screenshots, see Deploy Sanas on Stratodesk NoTouch OS.
Windows & macOS
Important Note: For Windows & macOS computers, Install the app directly or deploy it silently via a script or endpoint management software (Intune, Jamf, SCCM, etc.) using an Installer ID to pre-configure each machine.
How It Works?
The Installer ID is a unique identifier tied to a Sanas group (or your overall account) that pre-configures the app during activation:
Group Identification
Sanas uses the Installer ID to identify which group a user belongs to, then pre-configures the app based on that group's settings (language, accent, authentication mode, etc.).
Auto-provisioning
On first activation, Sanas checks whether the user already exists in the group associated with the Installer ID. If they do, they're granted access. If not, Sanas automatically creates the user in that group.
Note: Installer IDs are relevant only for Sanas App users, and auto-provisioning requires the Automatic User Creation toggle to be enabled under Settings > Configuration > Application Authentication (with SSO or Auto-Activation configured).
Tip: Use your Account's Installer ID to provision all App users directly into the Default Group, then move them to their respective groups afterward. See Manage App Users.
Deployment Prerequisites
Download the latest Sanas installer from the Sanas Portal: Get Sanas page.
Locate your Installer ID.
Log in to the Sanas Portal.
Navigate to the Get Sanas page.
Select the group you want to deploy to.
Copy the Installer ID and save it securely.
During Installation
Set the Installer ID as part of the initial app install. This can also be run through your endpoint management software to deploy to centrally managed machines in bulk.
Windows
Method 1: App Installer
Enter the optional Installer ID in its field when prompted during installation.
Method 2: Command
Replace <file_path> and <optional installer_ID> with your actual values — only for those commands that use installer IDs.
.msi with installer ID (CMD or PowerShell)
msiexec /i "<file_path>" installerid="<installer_ID>" /q.msi without installer ID (CMD or PowerShell)
msiexec /i "<file_path>" /q.exe with installer ID (CMD)
"<file_path>" /installerid="<installer_ID>" /q.exe without installer ID (CMD)
"<file_path>" /q.exe with installer ID (PowerShell)
& "<file_path>" /installerid="<installer_ID>" /q.exe without installer ID (PowerShell)
& "<file_path>" /q
macOS
Method 1: App Installer
Enter the optional Installer ID in its field when prompted during installation.
Method 2: Terminal
Run the command below, replacing <file_path>:
sudo installer -pkg "<file_path>" -target /Key Points:
The Installer ID is stored locally on the machine and is used the first time the app is activated.
The command can be run manually on each machine or deployed at scale through your endpoint management software.
Post Installation
Update the Installer ID on machines where Sanas is already installed. This allows you to move a device to a different group or correct an existing deployment configuration.
Windows
Replace <installer_ID> with your actual values. (CMD or PowerShell)
reg add "HKLM\SOFTWARE\Sanas.ai\Sanas" /v InstallerId /t REG_SZ /d "<installer_ID>"macOS
Replace <installer_ID> with your actual values.
sudo defaults write /Library/Preferences/ai.sanas.SanasApp.plist InstallerId "<installer_ID>"Note: This change takes effect the next time the user activates or reactivates the Sanas App. If you need to move App users from User Activation Key (UAK) login authentication method to Auto-Activation or (Single-sign On) SSO after installation, you can use the process described above to update the installer ID without reinstalling the application.
Google Chrome Extension
The Sanas Chrome Extension is the dedicated solution for organizations running Chrome OS devices, where the Sanas Desktop Application cannot be installed. It brings Sanas Speech AI directly into the Chrome browser, enabling Chrome OS users to access Sanas.
All Speech AI processing is offloaded to a remote inference backend, and the user gets access to consistent performance.
Note: The Chrome Extension works only with conferencing and softphone applications that run inside a browser (for example, Zoom Web or Google Meet). Users on dedicated desktop applications must continue to use the Sanas Desktop Application instead.
To get started, contact Sanas Support to obtain your organization's Endpoint URL. This URL is the access point that users' machines connect to for audio synthesis while using Sanas.
Depending on your organization's requirements, Sanas Support will provision an Endpoint URL that points to one of the following:
Option | Description |
Sanas Cloud | Sanas-hosted infrastructure, available in Singapore and the United States regions. Ideal for organizations that prefer a fully managed, low-overhead deployment. |
Self-Hosted | Sanas Speech AI models are hosted on your organization's own infrastructure. Ideal for organizations with strict data residency or network isolation requirements. |
Once you have your Endpoint URL, your administrator can complete remote inference configuration in the Sanas Portal.
Note: Ensure that all users can reach the configured Endpoint URL from their network via HTTPS on Port 443.
Install the Sanas Chrome Extension
Install the extension on the user's machine from the Chrome Web Store.
On the user's machine, open Google Chrome.
Navigate to the Sanas Chrome Extension page on the Chrome Web Store.
Note: The current Sanas Chrome Extension version is: 1.8.0.
Click Add to Chrome.

On the confirmation dialog, click Add Extension.
The Sanas icon appears in the Chrome toolbar once the installation is complete.
Note: If your organization manages Chrome browser settings centrally (for example, via Google Admin Console or a device management policy), you can push the extension to user machines without requiring manual installation. Contact Sanas Support for guidance on managed deployment.
Verify Authentication Mode
The Sanas Chrome Extension currently supports the following login options below. Verify that the group you are configuring uses either methods before proceeding.
User Activation Key (UAK)
Log in to the Sanas Portal using your credentials.
Navigate to Settings > Configuration, then select Application Authentication under Platform Authentication.
Ensure UAK is selected. If not, update it before continuing.
.png?sv=2026-02-06&spr=https&st=2026-08-20T23%3A55%3A20Z&se=2026-08-21T00%3A12%3A20Z&sr=c&sp=r&sig=5vZon5DltlH33RACdq%2BOFJlOKcK8QJvNJC9wkht%2FP2c%3D)
Single Sign-On (SSO)
Log in to the Sanas Portal using your credentials.
Navigate to Settings > Configuration, then select Application Authentication under Platform Authentication.
Ensure SSO is selected, then Domain based under redirection type. If not, update it before continuing.
.png?sv=2026-02-06&spr=https&st=2026-08-20T23%3A55%3A20Z&se=2026-08-21T00%3A12%3A20Z&sr=c&sp=r&sig=5vZon5DltlH33RACdq%2BOFJlOKcK8QJvNJC9wkht%2FP2c%3D)
Note: Verify with your Sanas point of contact (POC) or contact Sanas Support to confirm that this feature has been enabled for your organization. Otherwise, it will not be accessible from your account.
Configure Remote Inference on the Sanas Portal
Remote inference must be configured on the Group before users can authenticate with the extension.
On Portal’s Group Tree, select the Group you want to configure remote inferencing for.
Note: For account-wide configuration, select your Sanas Account instead of an individual Group.
Navigate to Settings > Configuration, then select Remote Inferencing under Group / Account Settings.
Enter the Endpoint URL provided by Sanas in the respective field, then click Save. Users will be routed to this access point while using Sanas.
Note: Contact Sanas Support to obtain your Endpoint URL. Ensure that all users can reach the configured Endpoint URL from their network via HTTPS on Port 443.
.png?sv=2026-02-06&spr=https&st=2026-08-20T23%3A55%3A20Z&se=2026-08-21T00%3A12%3A20Z&sr=c&sp=r&sig=5vZon5DltlH33RACdq%2BOFJlOKcK8QJvNJC9wkht%2FP2c%3D)
Once the endpoint is saved, configure the inferencing settings:
On the Configuration tab, select Accent Translation under Products.
Select Remote Inference under Inference Mode.
(Optional) Select your preferred Speech AI model from the drop-down menu. Sanas automatically selects the recommended model.
(Optional) Enable the Lock Configuration toggle to enforce this inferencing configuration across subgroups and prevent subgroup administrators from modifying it.
.png?sv=2026-02-06&spr=https&st=2026-08-20T23%3A55%3A20Z&se=2026-08-21T00%3A12%3A20Z&sr=c&sp=r&sig=5vZon5DltlH33RACdq%2BOFJlOKcK8QJvNJC9wkht%2FP2c%3D)
Click Save to apply the changes.
Add Users to the Portal
Add users to the Portal and assign them to the Group configured in Step 3. Refer to Add User for detailed instructions.
If your organization uses the User Activation Key (UAK) authentication mode, share the following credentials with each user :
Account ID — located at the top of the Group Tree. This is common across all users in your account.
User ID — unique to each user.
Test Your Setup
Add a temporary user to the configured Group and install the Sanas Chrome Extension on your Chrome browser to verify the installation and portal configuration setup.
Please refer to the link below on how to test the Chrome Extension:
Support
Need help? Get in touch with our Support Team for assistance.