From e51ae7bc8609ea546bd0f150faa0c1df3c40210d Mon Sep 17 00:00:00 2001 From: Kyle MacDonald Date: Tue, 6 Oct 2020 18:09:29 -0400 Subject: [PATCH] website: correct link to domain-model docs (#542) --- website/content/docs/common-workflows/manage-scopes.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/docs/common-workflows/manage-scopes.mdx b/website/content/docs/common-workflows/manage-scopes.mdx index a9f3fa715e..f8803669f0 100644 --- a/website/content/docs/common-workflows/manage-scopes.mdx +++ b/website/content/docs/common-workflows/manage-scopes.mdx @@ -13,7 +13,7 @@ Scopes are a foundational part of Boundary. They allow users to segregate resour 2. Organization 3. Project -Some resources can only be associated with a specific level of scope. Targets for example can only be project scope. Other resources can be of multiple scopes. For example, users can be both global and organization level scoped. See the [domain model](/docs/domain-model) for detailed resource specific information. +Some resources can only be associated with a specific level of scope. Targets for example can only be project scope. Other resources can be of multiple scopes. For example, users can be both global and organization level scoped. See the [domain model](/docs/concepts/domain-model) for detailed resource specific information. In this example, we're going to create two scopes, a project and an organization.