Link a counterpart and view shared work

Linking confirms that a Related company corresponds to a real ReportArea organization. It requires a proposal from the recipient and an independent confirmation by the source.

Availability: Company only; linking requires Manage service network. Shared work requires its specific viewing permission. Level: Advanced.

Purpose

Use linking to securely onboard an existing or new counterpart, convert open assignments, and enable a minimal work view for authorized customer accounts.

Link an existing Company

1. The source sends an invitation to the recipient's exact email.
2. Within seven days, the recipient opens the link, signs in with that verified email, and selects a Company they manage as owner, administrator, or network manager.
3. They re-enter their password and propose that Company. A second seven-day period starts.
4. The source reviews the exact Company, re-enters a password, and confirms or rejects it.
5. Confirmation creates or reuses a direct connection and permanently links the account to the record.

The recipient can decline before or after proposing; the source can revoke during either phase. Only one pending link can exist per record.

The email invitation uses the customer language stored on the record; if none is set, it uses the source organization's language. In both cases it is sent with ReportArea formatting and a text alternative.

When the counterpart is new

The recipient creates an account with the invited email, verifies it, and proposes a Company profile where they have administrative access. If none is eligible, they can create a Company profile from that journey and ReportArea returns to the claim without losing it. A Professional profile is not eligible, but it does not need to be converted when the person prefers to keep it separate.

Shared work as a customer

An active record with Client or Both role, linked account, and active connection lets roles with View shared work see provider, reference, subject, latest published status and ETA, published updates, and published attachments. Internal messages, notes, assignee, inventory, commercial data, private contact, and unpublished diagnosis remain hidden.

Shared documentation is a different kind of access. It is granted for one specific document, the recipient Company must accept it and assign it to its roles, and its level can never exceed View, Comment, or Edit as defined by the author. Linking alone exposes no libraries or plans.

Rules, required and optional choices

Required: exact verified email, active Company, network authority, and password at both confirmations. Optional: accepting the link and granting shared-work viewing. Linking creates no service agreement.

Confirmation moves active assignments to Pending conversion and revokes their portals. Each is converted or rejected separately.

Practical example

A company invites an unregistered provider. The provider creates an account and Company, returns to the link, and proposes it. The source confirms. Later, if the record also has Client role and updates are published, an authorized customer role sees only that projection.

Current limits

• Losing the session or changing browsers may require reopening the original link.
• The linked account cannot be replaced or unlinked through the interface.
• Ending the connection removes Shared work and can leave the record without a public reconnection path.
• Linking never moves data, accepts assignments, or creates agreements automatically.