Go to content

Multi-company operation with separate contexts

Switch between companies and maintain staff, contacts and routines in the correct context of each operation.

Illustrative scenario

How the situation may appear in everyday life

One person manages two operations with different teams. When switching companies, it only consults the resources and records of that context before taking action.

Illustrative flow

A possible sequence to guide care.

  1. Choose the active company

    The navigation makes it clear in which context the work is happening.

  2. Consult data from that context

    Conversations and contacts remain associated with the corresponding company.

  3. Apply coherent access

    Each member acts according to the role and participation defined for the company.

Resources that support this flow

Resources give structure to the service; The rules and decisions remain the responsibility of your team.

company selector

Switch context without hiding which operation is active.

Teams by context

Organize participants and roles according to each company.

Separate data

Maintain contacts and conversations associated with the correct company.

Explicit permissions

Control what actions each role can perform in the active context.

What to line up before you start

A clear configuration starts with the actual process, responsibilities and the minimum amount of information required.

  • List the companies and units that really need separate contexts.
  • Review the participation and role of each member in each operation.
  • Adopt clear names to reduce accidental context switches.
Conversations under control

Turn conversations into organized work

Create an account to learn about Lumez and configure service according to your team's responsibilities.