Skip to content
ZBIX website
ZBIX CRM 1.2.0

Manage Teams and legacy role policies

Teams group people for record visibility and reporting. A user can belong to several teams and can be a manager in a membership. Team membership and action permissions are evaluated separately.

Organize account coverage and manager visibility without granting unintended administrative actions.

  • Administrator identity.

  • Active users from the same organization.

  • An agreed ownership and team-scope policy.

  1. Open Administration > Teams & permissions. Review the existing teams before creating another group.

  2. Create a team with a descriptive name and save it.

  3. Choose the team, add its intended active members, and mark the relevant team managers.

  4. Save membership changes and refresh the team details. Resolve a version conflict by reviewing the latest membership rather than overwriting it.

  5. Review legacy role permissions and visibility if your organization uses them. Check Module Permissions for users with an explicit custom role because that assignment replaces legacy action/scope policy.

  6. Test access through a representative authorized user account during an approved access review.

Teams reflect the intended organization structure and effective visibility uses the current memberships.

Teams & permissions
SS-039 · Teams & permissions. Demonstration capture, 28 October 2026. Select the image to enlarge.
  • Existing record ownership stays with the owner when membership changes.

  • Multiple team memberships can produce overlapping reporting groups.

  • A team manager flag does not turn a user into an administrator.

  • Member cannot be added: confirm the user is active and belongs to this organization.

  • Team records are absent: the module visibility may be own rather than team.

  • Totals overlap: do not sum teams as disjoint business units.

Download manuals ↓

Open full-resolution image