Skip to main content

Switching organizations

A single user can belong to several organizations within the same Mawidabp instance (for example, working in a parent company with subsidiaries, or supporting multiple clients). This page explains how to enable that cross-access and how to switch between organizations without signing out.

When this makes sense​

Real examples:

  • An external consultant who audits several companies in a holding.
  • An administrator who maintains several organizations on the same instance.
  • A corporate manager with visibility across all subsidiaries.
  • An auditor who moves between business lines with separate data.

Alternative: if the need is to see everything consolidated, it is better to use a corporate organization (see Organization and units) instead of having each user switch manually.

Enable access to another organization​

A user already created in one organization can be linked to others from their own profile.

Step by step​

  1. Administration → Security → Users.
  2. Find the user to edit and click the pencil icon.
  3. Inside the editor, click Add new profile.
  4. Fill in:
    • Organization: the organization to grant access to.
    • Role: the profile they will have inside that organization.
    • No login required: tick this when the user is not registered in the SAML account of the destination organization. They will then authenticate with their main organization's credentials and the access propagates without requiring duplicate registration.
  5. Update user.

Switch active organization​

Once access is configured, the user switches organizations from the same session:

  1. Go to the user icon in the upper-right corner of the screen.
  2. Click to expand the available organizations.
  3. Select the destination organization.

Mawidabp reloads the context with the chosen organization's data. Everything on screen (menus, listings, permissions) refreshes to reflect the user's profile in that organization.

Data isolation​

What is not shared between organizations:

  • Findings, reviews, plans, and periods are specific to each organization.
  • Business units, tags, templates, and best practices live in one organization and are not visible from the others.
  • Comments, notifications, and attachments belong to the active organization context.

What does follow the user:

  • Their identity (name, email).
  • Language and personal interface preferences.
  • Sign-in history (lives at the instance level, not the organization level).

Multi-organization with SSO​

When the instance is integrated with an identity provider (Entra ID, Google Workspace, generic SAML), the flow changes slightly:

  • If the user exists in the destination organization's identity provider: simply sign in with that provider.
  • If the user only exists in their main organization: by ticking No login required when configuring the additional profile, Mawidabp propagates the main authentication to the rest of the enabled organizations. No duplicate registration in the destination's SSO is needed.

Corporate organization vs. manual switch​

A corporate organization (marked at creation) has cross-cutting access to all organizations in the instance without the need to switch. Appropriate when:

  • A permanent aggregated view is needed (consolidated dashboards, corporate reports).
  • An operational team works constantly with data from all subsidiaries.

Manual organization switching is preferable when:

  • Each organization has its own teams.
  • The isolated view is the norm and switching is the exception.

Support​

If you have doubts during configuration, write to soporte@mawidabp.com.