From 220456d092f77db93e5eb2efc7e5bbb144ac58ec Mon Sep 17 00:00:00 2001 From: stephan242 <99481666+stephan242@users.noreply.github.com> Date: Tue, 25 Oct 2022 16:14:50 +0100 Subject: [PATCH] Remove duplicate sentence (#2560) --- website/content/docs/concepts/domain-model/index.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/website/content/docs/concepts/domain-model/index.mdx b/website/content/docs/concepts/domain-model/index.mdx index 08a10f27fa..12c8ae84a4 100644 --- a/website/content/docs/concepts/domain-model/index.mdx +++ b/website/content/docs/concepts/domain-model/index.mdx @@ -45,8 +45,7 @@ The next level of access management is a [Grant](/docs/concepts/security/permiss For example, a grant can specify the List Action against a specific resource. Grants can specify resource types or resource IDs and may also be implemented as a rule. -The highest-level in Boundary utilizes the concepts of [Roles](/docs/concepts/domain-model/roles). Roles are a collection of zero or more grants. Roles are assigned to principals (users and groups) and govern what actions they are authorized to perform. Roles belong to a single scope and their lifecycle is dependent on the existence of that scope. Should the scope be deleted, the role would be deleted too. Roles are assigned to principals (users and groups) and govern what actions they are authorized to perform. -The diagram below illustrates the relationship between the different IAM components within Boundary. +The highest-level in Boundary utilizes the concepts of [Roles](/docs/concepts/domain-model/roles). Roles are a collection of zero or more grants. Roles are assigned to principals (users and groups) and govern what actions they are authorized to perform. Roles belong to a single scope and their lifecycle is dependent on the existence of that scope. Should the scope be deleted, the role would be deleted too. The diagram below illustrates the relationship between the different IAM components within Boundary. ![](/img/component-relationship.png)