> 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.

# Organize a large enterprise

> Keep enterprise data together and use Organizational Units to identify responsible offices.

Your Europe and America offices have their own domains, network ranges, and security contacts, but they also use shared services. Keep their data in one enterprise Environment so Tasks can work with the full dataset.

## Start with one Environment

Create a single Environment for the enterprise. A separate Environment for every office would limit each Task to one part of your organization's infrastructure.

Configure scans for both offices' domains and CIDR ranges in that Environment. Choose the Environment before you start: Objects discovered there cannot move to another Environment later.

## Associate each office with its discoveries

Create a Europe Organizational Unit (OU) and an America OU, each with the appropriate owner and location. Add both OUs to the enterprise Environment. For each OU, add the office's identifiers and configure the scans that will use them.

Each office's scans associate discovered Objects with that office's OU. All of those Objects belong to the enterprise Environment, so you can identify the responsible office within the shared dataset.

A shared service can have both OU associations. You can represent shared responsibility without duplicating the Object.

## Configure access and scanning controls

Suppose the Europe office allows scans only overnight, while the America office has systems that require a lower request rate. Configure schedules, no-scan windows, and egress rate limits for those requirements. No-scan windows and egress rate limits apply to identifiers across your Method instance, so you can use different restrictions for each office's identifiers within one Environment.

Give the relevant users access as part of that setup. The owner recorded on an OU identifies a contact; it does not grant permissions. Review the access settings and scanning controls when the offices' requirements change.

## Add an Environment when data needs separation

Add another Environment for data that must remain separate, such as experimental results or an independent company's dataset. You can reuse the existing OUs to identify responsible teams.

For example, add the Europe OU to a test Environment and configure its identifiers and scans there. Those scans associate discovered Objects with the Europe OU and keep them in the test Environment. The OU spans both Environments while their datasets stay separate.

> **Note**
>
> See [Data organization](/guides/platform-setup/data-organization) for the Environment and OU relationship, or [Create a new Environment](/guides/platform-setup/create-a-new-environment) for setup instructions.