Navigating Organizations

Learn how to navigate between different organizations in Layer5 Cloud and understand the order of precedence for organization settings.

This guide explains how to switch between organizations in Layer5 Cloud and describes the order of precedence that determines your active organization context.

When you work in Layer5 Cloud, your current organization context determines:

  • Which resources you can view (designs, environments, connections, workspaces)
  • Where new resources are created when you add them
  • What permissions and access levels apply to your actions

Layer5 Cloud uses the following order of precedence to determine your active organization context:

When you access Layer5 Cloud through a specific domain configured for an organization, that domain setting takes the highest priority in establishing your organization context.

Your user session stores the organization you have actively selected. When you switch organizations using the organization switcher in the UI, this selection is stored in your session and used for subsequent requests.

Organization context can be specified via URL query parameters. This is useful for direct links to resources within a specific organization.

When making API calls, the organization context can be explicitly specified as an API parameter, giving programmatic control over which organization’s resources are accessed.

To navigate between organizations in Layer5 Cloud:

  1. Locate the organization switcher in the interface (typically found in the navigation area).
  2. Click to open the list of organizations you have access to.
  3. Select the organization you want to switch to.
  4. The UI will refresh to display resources from the newly selected organization.

When you switch organizations, the following resources update to reflect the selected organization:

  • Designs: Only designs belonging to the selected organization are visible.
  • Workspaces: Only workspaces within the selected organization are accessible.
  • Environments: Environment configurations specific to the organization are shown.
  • Connections: Both managed and unmanaged connections scoped to the organization appear.
  • Team Memberships: Your team memberships and associated permissions within the organization apply.

All new resources you create are automatically associated with your currently selected organization:

  • New designs are created within the selected organization’s context.
  • New workspaces are established under the selected organization.
  • New connections and credentials are scoped to the selected organization.

Your roles and permissions are organization-scoped. This means:

  • The same user may have different roles in different organizations.
  • Administrative capabilities in one organization do not automatically grant administrative access in another.
  • Team memberships and their associated permissions are specific to each organization.

For more details about roles and permissions, see the Roles documentation.