> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.method.security/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.method.security/_mcp/server.

# Separate portfolio company data

> Separate independent company datasets and use Organizational Units to identify responsible teams.

Your security team supports several portfolio companies. Each company operates its own infrastructure, and its data needs to remain separate from the others. Give each company an Environment. If you also collect data for the parent organization, keep that in its own Environment.

## Create an Environment for each company

A central security team can administer all company Environments while keeping their datasets separate.

Each Task runs within one Environment. A Task for Company A works with Company A's dataset, even if the same security team also supports Company B. Objects cannot move between Environments, so choose the correct company Environment when you configure scans.

Within each company, keep related data in one Environment. Use Organizational Units (OUs) to identify the responsible offices and business units.

## Connect the responsible teams

Create an OU for each responsible team. Add it to the relevant company Environment, add its identifiers there, and configure its scans. The scans associate discovered Objects with that OU and keep them in the selected Environment.

A central network team may support both Company A and Company B. Its OU can span both Environments, with identifiers and scans configured for each. That shared responsibility does not combine the company datasets or let a Task cross their data boundaries.

An Object can also have multiple OU associations. For example, an Object in Company A's Environment can have associations with both the central network team and Company A's local team.

## Configure access and scanning controls

Configure Environment access for the central operators and the company users who need it. An OU association or owner does not grant access to a company's data.

Set scan schedules, execution locations, and identifier-based controls for each company's requirements. Even when the same team runs both companies' scans, their scanning restrictions may differ. Review each company's settings before starting scans.

## Use a shared Environment for integrated companies

Some businesses in a portfolio operate as an integrated organization and need a shared view of their infrastructure. If their data does not need to remain separate, use one Environment and OUs for the responsible teams, as in the [enterprise example](/guides/platform-setup/organize-a-large-enterprise).

Make that choice before collecting data. Changing OU assignments after an acquisition or reorganization does not move Objects or merge Environments.

> **Note**
>
> See [Data organization](/guides/platform-setup/data-organization) to compare Environments and OUs, or [Create a new Environment](/guides/platform-setup/create-a-new-environment) to configure a company Environment.