Team, lines, groups, and assignment

ReportArea Company distributes reports through roles, service lines, and routes. Groups or sectors add the assignee's team context but do not replace the line.

Availability: ReportArea Company; configuration requires administration, while operation requires membership in a receiving line or an administrator role. Level: Intermediate to advanced.

What it is for

It sends each new report to the right role, lets one person assume responsibility, and moves work through allowed paths without losing history.

Before you start

• A role defines permissions and may represent a service stage.
• A chain orders lines linked to roles.
• A route defines where a report can enter or be transferred.
• A group or sector describes a person's operational team. A person may have a primary group.

An administrator configures these elements. A report can exist without a matching chain, but it will not have the expected queue route.

How a report enters

When a report is created, ReportArea first looks for an active chain specific to its type, then for a general or default chain. It chooses the entry line using a creation route from the creator's role, then a generic entry, and finally the first line as fallback.

The report is Open and unassigned. Its origin group records the creator's primary sector when available. The My line tab shows each role the active work its line can receive.

Take, assign, and release

1. An eligible member opens an unassigned Open report in the line and chooses Take report.
2. It becomes In progress, is assigned to that person, and adopts their primary group as current group.
3. An administrator can instead use Assign to a user, but only with active members eligible for the current line.
4. To return it to the queue, the assignee or an administrator chooses Release. It becomes Open without assignee or current group.

Transfer to another line

1. Report staff choose Transfer line.
2. Select an active route available from the current line.
3. Add an optional note of up to 500 characters.
4. Confirm the transfer.

The report is Open in the destination line without assignee or current group. Scheduled and recorded arrival, and the suspension date and reason, are also cleared. The transfer and note remain in history, and the destination line may be notified.

Rules and effects

• The membership role determines a person's lines.
• Taking requires an Open, unassigned report; assignment is offered only for Open or In progress work.
• Transfer uses only active routes explicitly enabled from the current line.
• The group follows the assignee: it is set on take or assignment and cleared on release or transfer.
• The origin group does not change; it preserves creation context.
• Someone who wrote a message or performed a transfer may retain access as a participant after the line changes.
• A requester without an operational line still sees their own reports but does not gain staff actions.

Required and optional

Coherent roles, lines, and routes are needed for queue operation. Groups are optional for the report lifecycle, although inventory and internal organization may rely on them. The transfer note is optional.

Example

An employee creates a request. A creation route sends it to Level 1 Support. A technician takes it and her sector becomes the current group. After finding a complex failure, she transfers it through an enabled route to Specialists; assignment and visit data are cleared and the new team receives it Open.

Limits

Professional does not show routing lines, groups, administrative assignment, release, or internal transfer. Its jobs always use the direct self-assigned workflow.