Operational context: work by company without switching profiles

Operational context focuses navigation, filters, and new records on a person or company you serve, without turning that subject into a work profile or mixing organizations.

Availability: Professional and Company profiles; visible choices depend on each member's permissions, plan, and existing access. Level: Basic.

Work profile and operational context

The Work profile remains the true security boundary. It defines the organization, membership, permissions, and subscription. Switching it opens another isolated environment.

Operational context lives inside the selected profile. It only organizes work that the profile may already access; it never grants permission, creates a membership, or turns a symbolic company into a fictional organization.

Every new session starts in General. When you change context, ReportArea remembers it for that profile during the session. Another profile keeps its own selection.

Available scopes

General keeps the profile's aggregated areas and is the default scope.
Own focuses on the organization or independent practice itself.
Symbolic companies only groups counterparts that do not yet have a linked ReportArea Company.
A specific person or company focuses on modules that apply to its role: customer, provider, or both.

The Change context dialog searches by name, legal name, identifier, or email. Results are grouped to distinguish symbolic and linked companies, other businesses, people, and historical or closing records. Badges and secondary details disambiguate duplicate names.

Select a context

Confirm the Work profile in the Work scope card, at the start of side navigation.
Choose Change context and search for a scope or customer.
Select an option. Choosing a specific customer opens its contextual Home.
Confirm the name, icon, and accent before creating or changing information.

If a form has unsaved changes, ReportArea asks for confirmation. Canceling preserves the draft, position, and previous context.

For a specific customer, the card shows its identity, type or status, and accent. Applicable destinations begin immediately underneath. General for profile name follows, collapsed unless the current destination is general. Every destination appears only once. Inventory, templates, map, users, roles, settings, and subscription remain general and explicitly say so.

General and company filters

You do not have to use a complete context. In General, local filters offer All, Own, Symbolic only, and grouped customers. Changing a local filter affects only the current list or form: it does not change the menu, remembered selection, or global color.

The explicit Work in this context action deliberately makes that customer the operational context. This supports both aggregated management and cross-module focus without confusing the two choices.

Within a specific context, compatible creation flows inherit the customer and show its source. Customize chooses another customer only for that new record; Reset restores context without clearing other entered information.

Temporary view and shared links

Opening a detail may derive the correct context from the actual record. When it differs from the remembered context, the card identifies a Temporary view: the page uses the correct customer while the session preference remains unchanged. The content notice keeps the actions to adopt it or return.

Choose Use this context to adopt it or Return to… to go back to the remembered choice. An invalid link or one from another profile neither reveals names nor silently redirects to another company.

Accents and visual identity

Each specific customer can use blue, cyan, teal, indigo, violet, or fuchsia. Automatic consistently assigns the same tone to that record. A member who can manage commercial operations may change it from the canonical customer record; the Related company record previews the tone and links to that editor instead of duplicating controls.

The accent appears on contextual surfaces, icons, borders, and subtle backgrounds. It never replaces the name, icon, or badge, and it does not override error, status, focus, button, or active-navigation colors. Color therefore helps orientation without becoming the only identifier.

Symbolic companies and documentation

A symbolic company can have reports, assets, orders, and an internal documentation library when its capabilities allow them. It may be selected as an exact context or grouped under Symbolic companies only.

Documenting a symbolic company does not share content with it because no recipient organization exists. Sharing still requires a linked Company, a connection, and real permissions.

Controlled closing

A company or one of its roles may enter closing while commitments remain. Its context stays available and identifies whether each capability is open, closing, historical, or unavailable.

Closing prevents new records, reopening, activation, association, and transfers into the closed capability. It still permits completing or canceling existing commitments, removing or moving assets out, delivering or canceling orders, resolving existing commercial documents, finishing claims or assignments, and consulting, exporting, archiving, or revoking documentation as applicable.

Reactivating the capability allows new work, but it does not automatically restore archived records, completed transfers, or revoked shares.

Practical example

A company manages dozens of customers in General and filters Symbolic companies only to review pending work. Before a visit, it selects “North Clinic” as context: navigation prioritizes its reports, assets, and documentation, and new records inherit that customer. Afterward it returns to General. Nothing changes the Work profile or grants information the member could not already access.

Limits and privacy

Context never expands permissions or access across profiles.
Local filters never change the remembered context.
A symbolic company cannot receive shared content or remote access until it is linked through authorized flows.
General modules are not filtered by context even while the accent remains visible in the Work scope card.