Use cases by role

These journeys combine the main features according to each person's responsibility. You can start with reports alone and adopt advanced modules when the work requires them.

Availability: basic journeys apply to Professional and Company; organizational and B2B journeys are Company-only. Level: Basic to advanced.

Purpose

Use this guide to identify a starting point, understand who acts next, and avoid configuring modules you do not yet need.

Common requirements

• Account with verified email and one active membership.
• Active organization, current catalogs, and appropriate permissions.
• Internet connection to read or save changes.

Requester: create and follow a report

1. Open Reports, select type and urgency, and enter subject and details.
2. Add attachments, customer, asset, or component only when they add context.
3. Submit and follow status, assignee, and conversation from the detail.
4. Respond if it becomes Waiting and review the solution.
5. Sign if requested, close when satisfied, or reopen a Resolved/Closed report with a reason if the issue returns.

In Professional the report is self-assigned and starts In progress. In Company it enters Open in the configured flow.

Technician: perform field work

1. Take or receive the report and review My work.
2. Schedule arrival, mark arrival, and communicate with the requester.
3. If work cannot continue, use Waiting or Suspended with the correct reason.
4. Request the part and resume after Inventory delivers it.
5. Record consumption, installation, or replacement where relevant.
6. Write the resolution summary and capture or request a signature under policy.

Inventory and asset manager

1. Inventory classifies items, receives stock, and configures minimums and warehouses.
2. Handle requests by approving or delivering directly from Pending; only delivery deducts stock.
3. Select every serialized unit; quantity items may identify a subset.
4. Assets creates types and published templates, then workstations or units and assignments.
5. For replacement, verify compatibility and confirm returns before stock is restored.

Inventory and asset permissions are independent.

Commercial operator and sales administrator

1. Create the customer and contacts, then an order from the report.
2. Receive equipment into custody with accessories, condition, and photos.
3. Create quote revisions and record the customer's decision.
4. An administrator creates non-fiscal documents and records payments and allocations by currency.
5. Mark the order Ready and deliver under the debt policy.
6. If coverage was set, handle a claim through a new report and order.

Company administrator

1. Invite people with an explicit role.
2. Create roles with the minimum needed permission.
3. Configure groups, catalogs, and the primary chain; use the map to review flow.
4. Remember that there is currently no page for group membership and alternative chains are not fully configurable.

External provider without an account

1. Receive an assignment link through a secure channel.
2. View only shared information and publish progress or responses with attachments.
3. Do not change report status: the source organization retains control.
4. If you later create a Company, propose it from the linking invitation; every open assignment must be converted or rejected.

Network manager and B2B provider

1. Connect registered Companies or link a Related company.
2. The provider publishes offerings; the client proposes a directional agreement and the provider accepts.
3. The client hands off a report with only authorized categories.
4. The provider accepts, works in its local report, publishes progress, and proposes a resolution.
5. The client accepts or returns the resolution. Subcontracting continues only when authorized and never reveals the full chain.

Rules and effects

• A role journey describes responsibilities but never grants permission; role, record access, and current state prevail.
• Report, inventory, asset, order, and collaboration keep related histories without replacing one another.
• Public and Company-to-Company actions share a deliberate projection, never all internal content.
• Finishing one step never completes all others automatically: part delivery is not installation, quote approval is not payment, and accepting external work does not close the source report.

Required and optional choices

Required: verified identity, organization, report with type, urgency, and subject, and permission for every action. Optional: customers, assets, inventory, orders, signatures, public tracking, and B2B. Adopt only what matches the real process.

End-to-end example

A Company receives a notebook. The requester creates the report; an operator associates the customer and opens an order with custody. The technician diagnoses a specialized board and requests a part. Inventory delivers the exact unit. Because an external laboratory is needed, a manager hands the job to a connected Company. The laboratory proposes a resolution, the source accepts it, installs the part, records signature, delivers the order, and starts the warranty.

Current limits

• A journey never grants permission by itself; role and current state always prevail.
• Professional has no members, groups, map, chains, or B2B collaboration.
• External portal, public tracking, and Shared work are limited projections, not access to the internal report.
• The installed app cannot work offline.