@ -15,9 +15,9 @@ description: How to manage Boundary scopes
These are in a hierarchy:
* There is only one single `global` scope. It is meant as the entry point for initial administration/setup and to manage org scopes.
* Under the `global` scope there can be many org scopes. These are used to hold IAM-related resources and project scopes.
* Under each org scope can be many project scopes. These are used to hold infrastructure-related resources.
- There is only one single `global` scope. It is meant as the entry point for initial administration/setup and to manage org scopes.
- Under the `global` scope there can be many org scopes. These are used to hold IAM-related resources and project scopes.
- Under each org scope can be many project scopes. These are used to hold infrastructure-related resources.
Some resources can only be associated with a specific level of scope. As an example, [Targets](/docs/concepts/domain-model/targets) can only be contained within a project scope. Other resources can be contained by multiple scopes. For example, users can be created within the `global` scope or an org-level scope. See the [domain model](/docs/concepts/domain-model) for detailed resource specific information.