Skip to content

Multi-client operations

Portfolio visibility should not weaken account boundaries.

Netrix uses account, business, website, and location boundaries to keep client work organized. Staff can move across the portfolio, clients can be limited to assigned businesses, and every action resolves through the active membership rather than an unscoped record ID.

ControlSystemHumanClient
Collect evidence
Review meaning
Approve action
Verify output
The exact permission depends on account role, site ownership, connector capability, and the requested action.

What the workflow must answer

Keep the operating question attached to the evidence.

01

Business-centered organization

Tie websites and GBP locations to the business they describe so technical and local evidence share the correct client context.

02

Role-aware access

Owners, administrators, members, and clients receive different capabilities, with clients restricted to explicitly granted businesses.

03

One portfolio, separate records

Dashboard attention items reveal which client needs work while detailed data remains inside the selected account.

Inside the operating model

The screen should make the next decision easier to defend.

Each state keeps its source, owner, and boundary close enough to inspect before work advances.

01 / Product surface

Business-centered organization

Tie websites and GBP locations to the business they describe so technical and local evidence share the correct client context.

02 / Product surface

Role-aware access

Owners, administrators, members, and clients receive different capabilities, with clients restricted to explicitly granted businesses.

03 / Product surface

One portfolio, separate records

Dashboard attention items reveal which client needs work while detailed data remains inside the selected account.

An accountable trail

A useful state says exactly what happened.

  1. 01Observed

    The source evidence is recorded.

  2. 02Interpreted

    The condition is reviewed in context.

  3. 03Decided

    An authorized person chooses the next state.

  4. 04Applied

    A supported destination accepts the action.

  5. 05Verified

    The public result is read independently.

  6. 06Reported

    The claim matches the available evidence.

Product truth

Automation prepares work. Authority stays visible.

  1. 01
    No hidden autopilot

    Netrix does not publish AI drafts or apply SEO changes without an explicit authorized action.

  2. 02
    No optimistic verification

    An accepted write and a confirmed public value remain different states, and an unreadable page stays unknown.

  3. 03
    No invented scope

    Pages describe the product’s current boundary and name external providers or unfinished paths where they matter.

Continue the work

Browse all resources

See it in your workflow

Bring the evidence, decisions, and outcomes into one trail.

Request access