Groups, sectors, and the Company map

Groups represent sectors or teams across service lines. They help limit warehouse access, attribute activity, and explain possible routing between areas.

Availability: Company organizations only; all active members can view the map and administrators configure groups. Level: Intermediate to advanced.

Purpose

Use groups to describe where a person works and which sector warehouses they can access. Use Map to understand composition, activity, and possible operational routes, not to represent a reporting hierarchy.

Requirements

An organization in Company mode.
To create or edit groups and sector types: owner or administrator.
For useful connections to appear: members associated with groups, roles included in service lines, and active routes that allow creation or transfer.

Configure groups

Under Settings, Groups, create or choose a sector type.
Set the group's name, description, and status.
An active group appears on the map even when it has no members.
A person can belong to multiple groups and one acts as primary. That primary group identifies the origin sector when they create a report and the current sector when they take or receive it.

Read the map

Each card shows sector, members, roles, and service levels.
People without a group appear under No group and do not create connections.
Can route to and Receives from are calculated from active routes between roles and members' primary groups.
An A → B arrow expresses a possible report flow. It does not mean B manages A.
Selecting a group shows active reports originated there, active reports currently held by it, reports resolved during the last 30 days, and connections.
Selecting a person shows groups, role, active assigned or created reports, and reports resolved during the last 30 days.
On mobile, the same relationships are presented as a readable vertical list.

Rules and effects

A report's origin sector is fixed when it is created.
Current sector follows the assigned person; it is cleared on release or transfer until someone else takes it.
Groups are cross-functional and can contain people from different roles or levels.
The “external” and “technical” indicators, internal group role, and routing capability are currently descriptive; they do not grant permissions by themselves.
A sector warehouse is available only to members of that group and inventory managers.

Required and optional information

Required for a group: name, type, and status. Optional: description, members, primary group, and participation in routes. An empty group is valid, but the map shows it as incomplete configuration.

Practical example

Support and Workshop contain technicians with different roles. A route allows the Support role to transfer to the Workshop role. The map shows Support → Workshop; selecting Workshop displays its members, current work, and recent activity.

Current limits

There is no public interface to add or remove group members, select a primary group, or edit internal responsibilities. An organization configured through the interface may therefore show empty groups and people under No group.
The map does not create routes; it only interprets existing chain and membership configuration.
It does not show hierarchical dependency between sectors.