Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 20 additions & 4 deletions modules/ROOT/pages/business-groups.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -96,13 +96,11 @@ To interact with a business group, you must be granted a permission within that

As a member of a business group, you are automatically granted permissions to view and access the business group, but to access certain resources, you must have the appropriate permissions or roles assigned to you. For example, to access APIs and CloudHub deployments in the business group, you must be assigned permissions that apply to that business group.

For example, if you have the Organization Administrator permission in BusinessGroupA, you can grant users and teams access to APIs and CloudHub deployments in BusinessGroupA.

If you also have the Organization Administrator permission in BusinessGroupB, this does not mean that you can grant access to APIs and CloudHub deployments in BusinessGroupA to users in BusinessGroupB, and vice versa.
If you have the Organization Administrator permission in BusinessGroupA, you can grant users and teams access to APIs and CloudHub deployments in BusinessGroupA. If you also have the Organization Administrator permission in BusinessGroupB, this does not mean that you can grant access to APIs and CloudHub deployments in BusinessGroupA to users in BusinessGroupB, and vice versa.

Resources that belong to the root organization require permissions specified at the root organization level.

Users who are assigned the Organization Administrator permission at any level are automatically assigned that same permission in any child business group created within that level, so are automatically visible in the child. This does not apply retroactively to users who are assigned the Organization Administrator permission after a child is created.
Users who are assigned the Organization Administrator permission at any level are automatically assigned that same permission in any child business group created within that level, so they are automatically visible in the child business group. This does not apply retroactively to users who are assigned the Organization Administrator permission after a child business group is created.

== Control Access to Business Groups

Expand All @@ -118,6 +116,24 @@ The *Access Overview* section appears, displaying a list of all users with any p
* Permissions (sorted by product)
* Business group

=== Become a Business Group Administrator as a Root Organization Administrator

If you have the Organization Administrator permission over your root organization, you can assign yourself the Organization Administrator permission in a specific business group.

When you use this feature, note the following:

* This option does not appear if you already have the Organization Administrator in the business group.
* If you use this feature on a business group that has a child business group, the Organization Administrator permission does not automatically extend to the child business group. +
For example, if you add yourself as an admin to BusinessGroupA that has BusinessGroupB as a child, you only receive the Organization Administrator permission for BusinessGroupA.
+
* If you use this feature on a business group and then create a child business group under the original, you are automatically given the Organization Administrator permission for the newly created child business group.

include::partial$include-nav-business-groups.adoc[]

. Click the *...* or overflow menu next to a business group.
. Click *Add me as an admin...*
. Click *Confirm*.

== Delete a Business Group

Only an organization administrator that belongs to a business group can delete it. The top-level (root) business group can't be deleted, even by an organization administrator.
Expand Down