Skip to content

Categories and SaaS Sites

Goal

Create site categories, SaaS sites, and site browser accounts so users can access business sites by category.

Prerequisites

  • At least one browser instance exists.
  • Your account has permissions for site categories, site list, and site browser accounts.

Steps

  1. Go to "Site Management > Site Category" and create a category.
  2. Go to "Site Management > Site List" and click "Add Site".
  3. Enter site name, URL, category, logo, introduction, status, and related information.
  4. In the site list, open "Account Category Config" to define supported account categories.
  5. Go to "Site Management > Site Browser Account" and create browser accounts for the site.
  6. In the user portal, open the SaaS site and click visit or login.

Field Reference

FieldDescriptionRecommendation
Site NameBusiness system name shown in the user portalUse a name business users recognize
URLTarget site entry addressUse a complete https:// address
CategorySite grouping in the user portalGroup by business line, department, or system type
LogoSite icon in the user portalUse a clear icon with a clean background
Account CategoryDifferent login modes for the same siteExamples: admin, support, read-only
Site Browser AccountAccount used by the remote browser login flowCombine with permissions, groups, and workspaces

Login Flow Recommendation

  1. Create a test site and test account first.
  2. Verify that the target site opens in a browser instance.
  3. Configure account category and login scripts.
  4. Authorize a test group.
  5. Verify login from the user portal.
  6. Open access to production groups after confirmation.

Verification

  • The user portal displays SaaS sites by category.
  • Clicking a site opens the remote browser visit page.
  • Sites with configured accounts can perform login by account category.
  • Unauthorized users cannot see the site.

FAQ

  • If users cannot see a site, check site status and group site authorization.
  • Enable encrypted URL in site configuration if the source URL should not be exposed.
  • Site browser accounts should be controlled by permissions and groups.

Sa2web 1.0.0