Skip to content

Commit c5673e5

Browse files
committed
Suggestions from Aimee's review
1 parent 4f48743 commit c5673e5

File tree

5 files changed

+13
-13
lines changed

5 files changed

+13
-13
lines changed

content/hcp-docs/content/docs/hcp/admin/orgs.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ This page describes how to create and manage an organization in HashiCorp Cloud
1313
An _organization_ is a top-level entity in HCP for organizing resources. It contains one or more
1414
[HCP projects](/hcp/docs/hcp/admin/projects), which separate access to resources such as [HashiCorp Virtual Networks (HVN)](/hcp/docs/hcp/network) according to [user permissions](/hcp/docs/iam/users#user-permissions). An organization can have up to 100 projects.
1515

16-
Users can be a member of multiple organizations, and organizations can have a maximum of 3 users with the `owner` role. You can add and delete organization owners over time, but organizations require at least 1 owner at all times.
16+
Users can be a member of multiple organizations, and organizations can have a maximum of three users with the `owner` role. You can add and delete organization owners over time, but organizations require at least one owner at all times.
1717

1818
You cannot create an organization if you are already the owner of an existing organization.
1919

@@ -38,9 +38,9 @@ To locate the organization ID:
3838

3939
## Find organization owners
4040

41-
An organization can have 1-3 users with the `owner` role. Owners can change, but there must always be at least 1 owner per organization.
41+
An organization can have one to three users with the `owner` role. Owners can change, but there must always be at least one owner per organization.
4242

43-
To find the organization's current owners:
43+
To find the organization's current owners, perform the following steps:
4444

4545
1. At the top, click the dropdown to open the organization and project selector. Select **View all organizations**.
4646
1. Click the name of the organization.

content/hcp-docs/content/docs/hcp/admin/projects/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ the roles you can assign.
4141

4242
1. Log into [HCP Portal](https://portal.cloud.hashicorp.com/) and choose your
4343
organization. If you have logged in before, the portal opens the last project you were in.
44-
Navigate to the Organization to change projects
44+
Navigate to the Organization to change projects.
4545

4646
1. Select **Projects** in the sidebar.
4747

@@ -72,6 +72,6 @@ the roles you can assign.
7272

7373
![HCP Organization Structure](/img/docs/hcp-core/diagram-hcp_organization_project-resources.png)
7474

75-
A resource is any item that the access management system controls access to. Examples of resources are a HCP Vault Dedicated cluster, HCP Packer Bucket, or a HashiCorp Virtual Network (HVN). The **Active Resources** page lists all resources created in the project. To delete a project, all resources must be deleted. If an resource exists, HCP will block users from deleting the project. This page helps you to identify what resources are still in the project.
75+
A resource is any item that the access management system controls access to. Examples of resources are an HCP Vault Dedicated cluster, an HCP Packer Bucket, or a HashiCorp Virtual Network (HVN). The **Active Resources** page lists all resources created in the project. To delete a project, all resources must be deleted. If a resource exists, HCP blocks users from deleting the project. This page helps you to identify what resources are still in the project.
7676

7777
![Active Resources](/img/docs/hcp-core/active-resources-page.png)

content/hcp-docs/content/docs/hcp/iam/access-management.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ You can change the user's role assignment and the service associated with that r
3232

3333
## Organization level roles and permissions
3434

35-
The following table describes the roles and permissions available at the organizational level:
35+
The following table describes the roles and permissions available at the organizational level.
3636

3737
| HCP Organization Permissions | Owner | Admin | Contributor | Viewer | Browser | No role |
3838
| --------------------------------- | :-----: | :------: | :---------: | :------: | :------: | :------: |
@@ -146,13 +146,13 @@ A user can be a part of an organization with no roles assigned directly to them
146146

147147
## View current role assignments
148148

149-
To view a list of current role assignments in an organization:
149+
To view a list of current role assignments in an organization, perform the following steps:
150150

151151
1. At the top, click the dropdown to open the organization and project selector. Select **View all organizations**.
152152
1. Click the name of the organization.
153153
1. From the **Organization dashboard**, click **Access Control (IAM)**.
154154

155-
The **Role assignments** page lists the currently assigned roles, and provides an interface to search and filter the current assignments.
155+
The **Role assignments** page lists the currently assigned roles and provides an interface to search and filter the current assignments.
156156

157157
## Project level roles and permissions
158158

@@ -257,7 +257,7 @@ To learn more about each permission, refer to [HCP Terraform project permissions
257257

258258
@include '/hcp-administration/assign-project-role.mdx'
259259

260-
## Role Names and Role IDs
260+
## Role names and role IDs
261261

262262
To interact with the HCP Access Management system using the [HCP Terraform provider](https://registry.terraform.io/providers/hashicorp/hcp/latest) or public APIs, you must properly format the role IDs you reference. The following able lists role names and the formatting of their Role IDs.
263263

content/hcp-docs/content/docs/hcp/iam/users.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,6 @@ users.
3030

3131
@include '/hcp-administration/permission-intro.mdx'
3232

33-
## Access Management
33+
## Access management
3434

3535
For more information about permissions, the different types of roles and how they can be used within HCP, checkout the [Access Management](/hcp/docs/hcp/iam/access-management) page.

content/hcp-docs/content/partials/hcp-administration/permission-intro.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
HCP uses a role-based access controls (RBAC) system to enable members of your organizations and projects to perform actions in HCP and interact with resources. Some HCP applications allow you to assign roles for specific resources, such as an HCP Packer bucket. Refer to the individual HCP service's documentation for more information.
1+
HCP uses a role-based access control (RBAC) system to enable members of your organizations and projects to perform actions in HCP and interact with resources. Some HCP applications allow you to assign roles for specific resources, such as an HCP Packer bucket. Refer to the individual HCP service's documentation for more information.
22

33
### Types of Roles
44

@@ -9,7 +9,7 @@ You can configure HCP roles for an organization at two levels:
99

1010
### Inheritance
1111

12-
Each resource in a HCP organization has an IAM policy associated with it that sets the level of access allowed on that resource. This IAM policy is a data structure that provides a mapping of roles to principals assigned to that resource.
12+
Each resource in an HCP organization has an IAM policy associated with it that sets the level of access allowed on that resource. This IAM policy is a data structure that provides a mapping of roles to principals assigned to that resource.
1313

1414
![Role Permission Inheritance](/img/docs/hcp-core/diagram-hcp_IAM-inheritance.png)
1515

@@ -23,4 +23,4 @@ Permissions are inherited through the resource hierarchy. And they are effective
2323

2424
For example, a user assigned the `viewer` role in an organization also has `viewer` role permissions for projects within the organization. Similarly, a user assigned the `contributor` role in a project also has `contributor` role permissions for resources within the project.
2525

26-
If a user has an `viewer` role in an organization and `admin` role on a project in the same organization, the user receives a concatenation of `viewer` _and_ `admin` role permissions within that specific project.
26+
If a user has a `viewer` role in an organization and an `admin` role on a project in the same organization, the user receives a concatenation of `viewer` _and_ `admin` role permissions within that specific project.

0 commit comments

Comments
 (0)