Quickstart Guide

Updated on Mar 14, 2026
Published on Mar 6, 2026
3 minute(s) read

Introduction

This guide prepares you for a successful Sanas account setup. Before diving into configuration, review the permissions you'll need, gather the required information, and make key decisions upfront.

This guide covers:

.png?sv=2026-02-06&spr=https&st=2026-07-18T04%3A45%3A57Z&se=2026-07-18T04%3A58%3A57Z&sr=c&sp=r&sig=W3llWvq1uRygrfcFbkawZEM1x4NrZR1ok7aUCdGvP5U%3D)

Access requirements - Permissions and expertise needed to complete the setup.
Data preparation - Information to gather before you begin.
Key decisions - Strategic choices to make before you begin.
Account setup - Begin with your Sanas account setup.

.png?sv=2026-02-06&spr=https&st=2026-07-18T04%3A45%3A57Z&se=2026-07-18T04%3A58%3A57Z&sr=c&sp=r&sig=W3llWvq1uRygrfcFbkawZEM1x4NrZR1ok7aUCdGvP5U%3D)

Ensure you have the following permissions before starting:


Requirement	Why do you need it
Network admin access	To whitelist Sanas URLs on your organization's firewall, ensuring uninterrupted access to Sanas resources.
Application installation rights	To install the Sanas desktop application. Your specific needs depend on your deployment method (see below).

Installation rights by deployment method:

Local installation: Local administrator access on individual computers.
Remote deployment: IT admin access to your endpoint management software (e.g., Microsoft Intune).

.png?sv=2026-02-06&spr=https&st=2026-07-18T04%3A45%3A57Z&se=2026-07-18T04%3A58%3A57Z&sr=c&sp=r&sig=W3llWvq1uRygrfcFbkawZEM1x4NrZR1ok7aUCdGvP5U%3D) Gather the following information before starting your account setup:


Information	Description
Application user list	List of users who will use the Sanas desktop application.
Portal administrator list	List of administrators who will manage users and settings through the Sanas Portal.

.png?sv=2026-02-06&spr=https&st=2026-07-18T04%3A45%3A57Z&se=2026-07-18T04%3A58%3A57Z&sr=c&sp=r&sig=W3llWvq1uRygrfcFbkawZEM1x4NrZR1ok7aUCdGvP5U%3D)

Before configuring your account, decide on the following. You can proceed with default settings, but we recommend reviewing these options to create the best experience for your team.

What Group structure should I create for my organization?

Groups let you organize users and apply settings at scale. Plan your hierarchy based on how you want to manage users and view reporting.

Sample group structure:


Level	Organized by	Example
1st level	Projects or business units	Project A, Project B
2nd level	Geographic regions	India, Philippines
3rd level	Cities or offices	Mumbai, Bangalore

Why it matters:

Simplifies user management at scale
Enables granular reporting and analytics by group
Allows different settings (authentication, products) per group

Goal: Design a group structure that reflects how your organization operates and how you want to track usage.

See Create a new group for implementation steps.

What Portal roles should I assign to my administrators?

Portal roles control what administrators can see and do. Sanas provides default roles, and you can create custom roles for more granular control.

Default roles:


Role	Access level
Account Admin	Highest privileges—full access to all Portal features, including account details and subscription management
Group Admin	Same as Account Admin, except cannot access account details or subscription management

Custom roles: Define specific permissions tailored to your organization's needs. For example, create a role that can manage users but not change authentication settings.

Goal: Identify which roles you need and whether custom roles are required before inviting administrators.

See Create a custom role for details.

Which authentication mode should I use for my team?

Authentication mode determines how users sign in to the Sanas desktop application. Choose based on your security requirements and user workflow.


Method	How it works	Recommended for
Email-Passcode	User receives a one-time verification code via email	Organizations where users have reliable work email access
UAK	User enters the Account ID and the User ID provided by the admin.	Environments without user email access; admin controls credential distribution
SSO	The user authenticates through your identity provider (eg, Okta, Azure AD, etc.).	Organizations already using SSO—provide seamless, centralized authentication. SSO requires additional setup to work. See Auto-activation to learn more.
Auto-activation	Automatic sign-in using the organization’s domain.	Organizations require quick user onboarding with minimum admin overhead. Auto-activation requires additional setup to work. See Configure SSO to learn more.

Configuration flexibility:

Set a single authentication mode for your entire account, or
Configure different modes for different groups (e.g., SSO for headquarters, UAK for contact centers)

Goal: Decide which authentication mode to use and whether different groups need different methods.

See Authentication Modes for configuration guidance.

How should I deploy the Sanas application to users?

Decide how you'll install the Sanas application on user devices.


Method	Description	Recommended for
Individual deployment	Share the installer with users for manual installation.	Small teams, pilot groups, or quick evaluations.
Enterprise deployment	Use endpoint management tools (Microsoft Intune, SCCM, etc.) for centralized deployment.	Large organizations with existing device management infrastructure.
Thin client deployment	Deploy on virtualized desktop platforms (Stratodesk, IGEL, eLux).	Organizations using virtual desktop infrastructure.

Goal: Select a deployment method that fits your IT infrastructure and team size.

.png?sv=2026-02-06&spr=https&st=2026-07-18T04%3A45%3A57Z&se=2026-07-18T04%3A58%3A57Z&sr=c&sp=r&sig=W3llWvq1uRygrfcFbkawZEM1x4NrZR1ok7aUCdGvP5U%3D) You're ready to begin. Proceed with the account setup flow below:

Configure your Sanas account

Default settings:

Authentication: UAK
Products: Based on your request

Proceed with account Setup →