Skip to content

Mantle 2.0 Guide: Group Management

Overview

Groups define the operational boundary for assets, nodes, users, and workflows inside Mantle 2.0. A clean group structure lets enterprises delegate control without losing visibility or overexposing shared resources.

Use this guide when you need to:

  • Create a new group for a program, team, or deployment tier
  • Add users to a group with the correct role
  • Enable group-scoped assets
  • Upload or remove assets inside a specific group

1. Group Design Basics

Before building out the UI objects, decide how groups should map to your environment:

  • Use groups to represent real operational boundaries such as business units, customers, labs, staging environments, or mission kits
  • Keep names short and descriptive so ownership is obvious in dashboards and audit trails
  • Prefer a stable hierarchy over frequent reorganization
  • Reserve elevated group roles for administrators who truly manage local assets and memberships

As a rule, groups should make permission boundaries clearer, not more complicated.

2. Create a Group

  1. Open Groups from the left navigation, then click Add Group. Groups tab and add button
  2. Enter a descriptive name such as East-Region-Staging, then save. Enter group name modal

Tip: Align group names with business units, programs, or deployment tiers so administrators can immediately understand scope.

3. Add Users to a Group

  1. Select the target group from the list. Group detail page selection
  2. Open the Users tab to review current membership. Users tab inside group management
  3. Enter edit mode for the membership controls. Edit user membership controls
  4. Set the operation to Add, select the user, assign the appropriate role, and save. Adding a user and selecting operation Assigning the Standard role before saving

Typical group-scoped roles include:

  • Group Admin: Manages membership, settings, and group-scoped resources
  • Standard: Contributes operational data and runs workflows within assigned boundaries
  • View Only: Read access for observers, audits, or training

4. Enable and Upload Group Assets

Group assets allow a team to maintain files that should not live in the global library.

  1. Open the target group and confirm you have the necessary administrative permissions. Group users and permissions
  2. Open the Settings tab and enable Allow Group Assets. Enable allow group assets setting
  3. Move to the Assets tab and click the green Add button. Group assets add button
  4. Open the Upload Group Assets tab. Upload group assets tab
  5. Upload the file, confirm it appears in the modal, assign the correct type, and click Upload All. Upload files area for group assets Select files from local system Upload assets tab in modal Select asset type for group upload Upload all button
  6. Use Monitor Assets if you need to watch the install state. Success and monitor assets button

Use group assets when a file is specific to one tenant, one customer, or one deployment stream. Keep broadly reusable artifacts in the global asset library instead.

5. Remove Group Assets

  1. Open Groups and select the target group. Groups tab in left nav Select group
  2. Open the group's Assets tab. Group assets tab
  3. Open the asset Action menu and choose Delete. Action menu and delete option
  4. Confirm the delete action. Delete confirmation modal

Next Steps

Once groups are defined:

  1. Use User Management to align account roles with group scope.
  2. Use Asset Management to maintain reusable global assets and tagging strategy.
  3. Return to Getting Started if you still need to establish the baseline group and user model on a fresh appliance.