🧱 Group Management

Group management has two core purposes:

• Put environments (browser instances) into different “buckets” by business dimensions.
• Control who can see and operate which environments through “group permissions”.

For daily usage, the exact group name is not important; the scope of group permissions is.

At a glance

Which bucket an environment belongs to is “group”; who can see which buckets is “group permission”.

🗂 Grouping environments

Grouping is essentially attaching a business label to each environment. Typical patterns:

• By business: ecommerce, social, scraping, testing, etc.
• By project: Shop A, Shop B, Campaign X, etc.
• By region: US, EU, APAC, etc.

In the left menu, go to “Group Management” to see:

• Group name: Click to jump to Environment Management and auto-filter environments in that group.
• Environment count: How many environments are in this group.
• Note: Additional explanation of this group’s purpose.

✏️ Steps to create a group

1. Click “New”
   • Opens the group creation dialog.
2. Fill in group name (required) and note (optional)
   • Recommended naming: “Business + Channel + Purpose”, for easy recognition later.
3. Save
   • A new group is created with environment count = 0.
4. Assign environments to the group
   • In environment details or batch operations, move/assign environments into this group.

🔐 Group Permissions: “All” vs “Specific”

Group permissions determine which environments a user can see and operate in Environment Management.

There are two common modes:

🌍 All-group permissions

• For: enterprise admins, tech owners, and global roles.
• Effects:
  • See all groups and environments in Environment Management.
  • All groups (including new ones) show up in the top group filter.
  • Can start/stop/edit environments in any group.

With all-group permissions, there are effectively no “walls”—all environments are visible and operable.

🎯 Specific-group permissions

• For: operators, outsourced accounts, members of sub-teams, etc.
• Effects:
  • Can see only authorized groups and their environments.
  • Group dropdown shows only groups they are authorized for.
  • Unassigned groups are completely invisible and cannot be accessed via URL.

Common scenarios:

• An operator responsible only for “Shop A” and “Shop B” gets permissions only for those groups.
• Outsourced partners see only the specific project group and nothing else.

If a user sees no environments

• Environment list appears empty.
• Group dropdown has almost no options.
• Very likely they have no group permissions and an admin must assign at least one group.

👥 Assigning group permissions to users

On the Group Management page, you can configure “which users get which groups”:

1. Choose groups
   • Select one or more groups from the list.
   • Click “User authorization” to open the authorization dialog.
2. Choose users
   • The left side shows users by role (for example operator, owner, etc.).
   • Select a role, then tick specific users on the right.
   • Selected users are summarized in a “Selected users” area below.
3. Confirm authorization
   • Confirm “Selected groups” and “Selected users” are correct.
   • Click “Confirm” to finish.
   • These users now have access to the selected groups (specific-group permissions).

All-group permissions are usually configured by enterprise-level admins on the system side. Regular users don’t set this themselves; they only need to understand:

• All-group permission ⇒ can see all groups.
• Partial-group permission ⇒ can see only assigned groups.

🧭 Usage and configuration suggestions

• Prefer specific-group permissions

  • Split groups by business or project and assign only relevant groups to each person.
  • Reduce misoperations and over-privileged access.

• Key groups should have at least 2 people with full access

  • Avoid lock-in when a single admin leaves or encounters account issues.

• Review authorizations regularly

  • Update group permissions when team members change.
  • Remove unused group permissions to keep least-privilege.

Once you understand “groups + group permissions”, you can build a secure and clear environment management model based on org structure and business dimensions.