From 3ade270f30f027b40d9e58d59b8e707f2f90b072 Mon Sep 17 00:00:00 2001 From: Joey Mucci Date: Wed, 22 Apr 2026 15:47:22 +0000 Subject: [PATCH 1/5] reorder paragraphs --- docs/reference/terms/access-groups.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/terms/access-groups.md b/docs/reference/terms/access-groups.md index e875ad2b..b9e0ff10 100644 --- a/docs/reference/terms/access-groups.md +++ b/docs/reference/terms/access-groups.md @@ -9,8 +9,8 @@ myst: In Landscape, **access groups** are logical groupings used by administrators to assign specific administrative rights to computers on a per-group basis. Each computer can only be in one access group. In addition to computers, access groups can contain package profiles, scripts and custom graphs. -A new Landscape installation comes with a single access group, called global, which gives any administrators who are associated with roles that include that access group control over every computer managed by Landscape. Most organizations will want to subdivide administration responsibilities by creating logical groupings of computers. - -Typical access groups might be constructed around organizational units or departments, locations or hardware architecture. You can manage access groups from the **Access groups** tab in your organization's home page. See how to [create access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#create-access-groups), [add computers to access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#add-computers-to-access-groups), and [associate roles with access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#associate-roles-with-access-groups). +A new Landscape installation comes with a single access group, called global, which gives any administrators who are associated with roles that include that access group control over every computer managed by Landscape. Most organizations will want to subdivide administration responsibilities by creating logical groupings of computers.vTypical access groups might be constructed around organizational units or departments, locations or hardware architecture. It's good practice to create and document a naming convention for access groups before you deploy Landscape, so that all administrators understand what constitutes an acceptable logical grouping for your organization. + +You can manage access groups from the **Access groups** tab in your organization's home page. See how to [create access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#create-access-groups), [add computers to access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#add-computers-to-access-groups), and [associate roles with access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#associate-roles-with-access-groups). From 0a366d6c906be6dd1c256548ce03f56021a22329 Mon Sep 17 00:00:00 2001 From: Joey Mucci Date: Wed, 22 Apr 2026 19:51:02 +0000 Subject: [PATCH 2/5] reword and add nesting info --- docs/reference/terms/access-groups.md | 14 ++++++++++++-- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/docs/reference/terms/access-groups.md b/docs/reference/terms/access-groups.md index b9e0ff10..8026306a 100644 --- a/docs/reference/terms/access-groups.md +++ b/docs/reference/terms/access-groups.md @@ -7,9 +7,19 @@ myst: (reference-terms-access-groups)= # Access groups -In Landscape, **access groups** are logical groupings used by administrators to assign specific administrative rights to computers on a per-group basis. Each computer can only be in one access group. In addition to computers, access groups can contain package profiles, scripts and custom graphs. +In Landscape, **access groups** are logical groupings used by administrators to assign specific administrative rights to instances on a per-group basis. Each instance can only be in one access group. In addition to computers, access groups can contain package profiles, scripts and more. -A new Landscape installation comes with a single access group, called global, which gives any administrators who are associated with roles that include that access group control over every computer managed by Landscape. Most organizations will want to subdivide administration responsibilities by creating logical groupings of computers.vTypical access groups might be constructed around organizational units or departments, locations or hardware architecture. +A new Landscape account comes with a single access group, called "global". Any administrators associated with roles that include this access group have control over every instance managed by Landscape. Most organizations will want to subdivide administration responsibilities by creating logical groupings of computers. Typical access groups might be constructed around organizational units or departments, locations or hardware architecture. + +When new access groups are created, a parent access group is specified. If an administrator has rights to manage a certain access group, that administrator will also have rights for its children access groups. Every other access group has the global access group as its parent, either directly or indirectly. A nested access group structure might look something like the diagram below. + +```bash +global +├── desktop +└── server + ├── database + └── web +``` It's good practice to create and document a naming convention for access groups before you deploy Landscape, so that all administrators understand what constitutes an acceptable logical grouping for your organization. From c7d8247c35564ec3401138f2c357d3bef166e5c7 Mon Sep 17 00:00:00 2001 From: Joey Mucci Date: Wed, 22 Apr 2026 20:21:34 +0000 Subject: [PATCH 3/5] add managing access groups header --- docs/reference/terms/access-groups.md | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/docs/reference/terms/access-groups.md b/docs/reference/terms/access-groups.md index 8026306a..ce09989b 100644 --- a/docs/reference/terms/access-groups.md +++ b/docs/reference/terms/access-groups.md @@ -1,15 +1,15 @@ --- myst: html_meta: - description: "Reference for Landscape access groups used to assign administrative rights to computers and organize management responsibilities." + description: "Reference for Landscape access groups used to assign administrative rights to instances and organize management responsibilities." --- (reference-terms-access-groups)= # Access groups -In Landscape, **access groups** are logical groupings used by administrators to assign specific administrative rights to instances on a per-group basis. Each instance can only be in one access group. In addition to computers, access groups can contain package profiles, scripts and more. +In Landscape, **access groups** are logical groupings used by administrators to assign specific administrative rights to instances on a per-group basis. Each instance can only be in one access group. In addition to instances, access groups can contain package profiles, scripts and more. -A new Landscape account comes with a single access group, called "global". Any administrators associated with roles that include this access group have control over every instance managed by Landscape. Most organizations will want to subdivide administration responsibilities by creating logical groupings of computers. Typical access groups might be constructed around organizational units or departments, locations or hardware architecture. +A new Landscape account comes with a single access group, called "global". Any administrators associated with roles that include this access group have control over every instance managed by Landscape. Most organizations will want to subdivide administration responsibilities by creating logical groupings of instances. Typical access groups might be constructed around organizational units or departments, locations or hardware architecture. When new access groups are created, a parent access group is specified. If an administrator has rights to manage a certain access group, that administrator will also have rights for its children access groups. Every other access group has the global access group as its parent, either directly or indirectly. A nested access group structure might look something like the diagram below. @@ -23,4 +23,13 @@ global It's good practice to create and document a naming convention for access groups before you deploy Landscape, so that all administrators understand what constitutes an acceptable logical grouping for your organization. -You can manage access groups from the **Access groups** tab in your organization's home page. See how to [create access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#create-access-groups), [add computers to access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#add-computers-to-access-groups), and [associate roles with access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#associate-roles-with-access-groups). +## Managing access groups + +### In the new web portal +You can view, add, and delete access groups under **Org. settings** > **Access groups**. See how to [create access groups](/how-to-guides/web-portal/web-portal-24-04-or-later/manage-access-groups.md#create-access-groups), [add instances to access groups](/how-to-guides/web-portal/web-portal-24-04-or-later/manage-access-groups.md#add-instances-to-access-groups), and [associate roles with access groups](/how-to-guides/web-portal/web-portal-24-04-or-later/manage-access-groups.md#associate-roles-with-access-groups). + +### In the classic web portal +You can manage access groups from the **Access groups** tab in your organization's home page. See how to [create access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#create-access-groups), [add instances to access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#add-computers-to-access-groups), and [associate roles with access groups](/how-to-guides/web-portal/classic-web-portal/manage-access-groups.md#associate-roles-with-access-groups). + +### Via the API +See the Legacy API reference for [changing an instance's access group](/reference/api/legacy-api-endpoints/computers.md#changecomputersaccessgroup) From ea2f17466331eb5c9ecdb0e853b34d4d9c165d42 Mon Sep 17 00:00:00 2001 From: Joey Mucci Date: Wed, 22 Apr 2026 20:31:42 +0000 Subject: [PATCH 4/5] proofread --- docs/reference/terms/access-groups.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference/terms/access-groups.md b/docs/reference/terms/access-groups.md index ce09989b..dc04dcf0 100644 --- a/docs/reference/terms/access-groups.md +++ b/docs/reference/terms/access-groups.md @@ -9,9 +9,9 @@ myst: In Landscape, **access groups** are logical groupings used by administrators to assign specific administrative rights to instances on a per-group basis. Each instance can only be in one access group. In addition to instances, access groups can contain package profiles, scripts and more. -A new Landscape account comes with a single access group, called "global". Any administrators associated with roles that include this access group have control over every instance managed by Landscape. Most organizations will want to subdivide administration responsibilities by creating logical groupings of instances. Typical access groups might be constructed around organizational units or departments, locations or hardware architecture. +A new Landscape account comes with a single access group, called "global". Any administrators associated with roles that include this access group have control over every instance managed by that account. Most organizations will want to subdivide administration responsibilities by creating logical groupings of instances. Typical access groups might be constructed around organizational units or departments, locations or hardware architecture. -When new access groups are created, a parent access group is specified. If an administrator has rights to manage a certain access group, that administrator will also have rights for its children access groups. Every other access group has the global access group as its parent, either directly or indirectly. A nested access group structure might look something like the diagram below. +When new access groups are created, a parent access group is specified. If an administrator has rights to manage a certain access group, that administrator will also have rights for its child access groups. Every other access group has the global access group as its parent, either directly or indirectly. A nested access group structure might look something like the diagram below. ```bash global From 7ac90a6d171b538d1e3fcb85dfbcda7d49fbc977 Mon Sep 17 00:00:00 2001 From: Joey Mucci Date: Wed, 22 Apr 2026 22:06:47 +0000 Subject: [PATCH 5/5] remove broken link --- .../repository-mirrors/manage-repositories-with-the-api.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/how-to-guides/repository-mirrors/manage-repositories-with-the-api.md b/docs/how-to-guides/repository-mirrors/manage-repositories-with-the-api.md index 3ed1f97c..aed72430 100644 --- a/docs/how-to-guides/repository-mirrors/manage-repositories-with-the-api.md +++ b/docs/how-to-guides/repository-mirrors/manage-repositories-with-the-api.md @@ -79,8 +79,6 @@ Note: the secret key must NOT have a passphrase. To remove the passphrase from a gpg --edit-key A1234B5678C9101112D12141516E17181920FGH0 ``` -See the [gpg](http://manpages.ubuntu.com/cgi-bin/search.py?q=gpg) man page for more details. - List the keys: ```bash