Quick Start

Goal

Complete the shortest path to a working remote browser scenario: create a user, machine, browser, site, group, and let the user open the site from the portal.

Prerequisites

• Sa2web has been deployed.
• The admin console is reachable at https://<APP_DOMAIN>/admin/login.
• At least one SaaS site URL is prepared.

Ten Steps to First Site Access

1. Log in to the admin console with the system user from installation.
2. Go to "Browser Management > Machine List" and add a machine.
3. Go to "Browser Management > Browser List" and create a browser instance bound to the machine.
4. Go to "User Management > User List" and create a normal user.
5. Go to "Site Management > Site Category" and create a category such as "Common Systems".
6. Go to "Site Management > Site List" and create a SaaS site under the category.
7. Open "Account Category Config" from the site list and create a default account category.
8. Go to "Group Management > Group List" and create a group such as "Default Access Group".
9. Authorize users, SaaS sites, permissions, and proxies for the group.
10. Log in as the normal user at https://<APP_DOMAIN>/app/login, open the site, and verify access.

Minimum Acceptance Checklist

Check	Expected Result
Admin login	Administrator can open the dashboard
Machine environment	Machine record exists, and the keeper service and runtime are available
Browser instance	Browser list has a schedulable instance
User portal login	Normal user can log in
Site visibility	Authorized SaaS site appears in the portal
Site access	Clicking the site opens the remote browser page

First-Day Recommendations

• Create at least two admin accounts to avoid maintenance lockout.
• Create groups by department or project instead of placing all users into one long-term group.
• Configure one test site first to validate browser, proxy, and scripts before adding production sites in bulk.
• Test external collaboration links with a small audience before wide distribution.