Skip to content

Conversation

@boruszak
Copy link
Contributor

Description

This PR updates HCP platform documentation. Previously, an organization supported a single non-transferrable owner. To better support business continuity, organizations now allow up to 3 users with the owner role. These owners can be added or removed as desired, although one user must always be an owner for the organization.

Preview links

@boruszak boruszak added the documentation Improvements or additions to documentation label Oct 21, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Oct 21, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Mon Oct 27 23:38:12 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Mon Oct 27 23:32:11 UTC 2025

@github-actions
Copy link
Contributor

github-actions bot commented Oct 21, 2025

Broken Link Checker

No broken links found! 🎉

@boruszak boruszak marked this pull request as ready for review October 21, 2025 22:01
@boruszak boruszak requested review from a team as code owners October 21, 2025 22:01
Copy link

@xargs-P xargs-P left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you VERY much @boruszak . I can see you skills throughout the edits 😄
I added a few comments I wanted your feedback on.

Copy link

@xargs-P xargs-P left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good!! I think we are ready to merge once the code is ready to go 🙏

@boruszak boruszak removed the HCP label Oct 28, 2025
Copy link

@aimeeu aimeeu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I left some style nits :)


</Note>
organization. If you have logged in before, the portal opens the last project you were in.
Navigate to the Organization to change projects
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Navigate to the Organization to change projects
Navigate to the Organization to change projects.

missing period

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

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, HashiCorp Virtual Network (HVN) or a HCP Vault Secret App. 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.
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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

nit: indefinite article should be "an" for HCP (an HCP Vault...)

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

Users can be a member of multiple organizations if invited by the admin of other organizations. However, you can only create and own one organization for your HCP account.
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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

nit: spell out numbers zero through nine


## Find organization owners

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

style nit number ranges


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.

To find the organization's current owners:
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To find the organization's current owners:
To find the organization's current owners, perform the following steps:

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

# Role Names and Role IDs
## Role Names and Role IDs
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Role Names and Role IDs
## Role names and role IDs


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

## Access Management
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
## Access Management
## Access management

@@ -1,16 +1,15 @@
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 specific HCP application documentation for more information.
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.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

### Inheritance
Each resource in a HCP organization has an IAM policy associated with it that informs about 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.

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

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.

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

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation HCP Docs

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants