Skip to content

Commit bd8c911

Browse files
authored
Merge pull request #23613 from docker/follow-up-formatting
fix: formatting in admin guides
2 parents 63ade45 + d717767 commit bd8c911

File tree

4 files changed

+26
-26
lines changed

4 files changed

+26
-26
lines changed

content/guides/admin-set-up/comms-and-info-gathering.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Communicate early with users to inform them that:
1818
- They'll be upgraded to a supported version of Docker Desktop as part of the subscription onboarding
1919
- Settings will be reviewed and optimized for productivity
2020
- They'll need to sign in to the company's Docker organization using their
21-
business email to access subscription benefits
21+
business email to access subscription benefits
2222

2323
### Engage with your MDM team
2424

@@ -44,7 +44,7 @@ If you suspect your company has multiple Docker organizations:
4444

4545
- Survey your teams to see if they have their own organizations
4646
- Contact your Docker Support to get a list of organizations with users whose
47-
emails match your domain name
47+
emails match your domain name
4848

4949
## Gather requirements
5050

@@ -60,8 +60,8 @@ configuration:
6060
Review these areas together:
6161

6262
- Security features and
63-
[enforcing sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md)
64-
for Docker Desktop users
63+
[enforcing sign-in](/manuals/enterprise/security/enforce-sign-in/_index.md)
64+
for Docker Desktop users
6565
- Additional Docker products included in your subscriptions
6666

6767
To view the parameters that can be preset, see [Configure Settings Management](/manuals/enterprise/security/hardened-desktop/settings-management/configure-json-file.md#step-two-configure-the-settings-you-want-to-lock-in).

content/guides/admin-set-up/deploy.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,8 +7,8 @@ weight: 40
77
> [!WARNING]
88
>
99
> Communicate with your users before proceeding, and confirm that your IT and
10-
MDM teams are prepared to handle any unexpected issues, as these steps will
11-
affect all existing users signing into your Docker organization.
10+
> MDM teams are prepared to handle any unexpected issues, as these steps will
11+
> affect all existing users signing into your Docker organization.
1212
1313
## Enforce SSO
1414

content/guides/admin-set-up/testing.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -14,23 +14,23 @@ SSO and SCIM setup.
1414
> [!IMPORTANT]
1515
>
1616
> Some users may need CLI based logins to Docker Hub, and for this they will
17-
need a [personal access token (PAT)](/manuals/security/access-tokens.md).
17+
> need a [personal access token (PAT)](/manuals/security/access-tokens.md).
1818
1919
## Test Registry Access Management and Image Access Management
2020

2121
> [!WARNING]
2222
>
2323
> Communicate with your users before proceeding, as this step will impact all
24-
existing users signing into your Docker organization.
24+
> existing users signing into your Docker organization.
2525
2626
If you plan to use [Registry Access Management (RAM)](/manuals/enterprise/security/hardened-desktop/registry-access-management.md) and/or [Image Access Management (IAM)](/manuals/enterprise/security/hardened-desktop/image-access-management.md):
2727

2828
1. Ensure your test developer signs in to Docker Desktop using their
29-
organization credentials
29+
organization credentials
3030
2. Have them attempt to pull an unauthorized image or one from a disallowed
31-
registry via the Docker CLI
31+
registry via the Docker CLI
3232
3. Verify they receive an error message indicating that the registry is
33-
restricted by the organization
33+
restricted by the organization
3434

3535
## Deploy settings and enforce sign in to test group
3636

content/guides/admin-user-management/onboard.md

Lines changed: 15 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -19,11 +19,11 @@ Members are granted controlled access to resources and enjoy enhanced organizati
1919

2020
### Benefits of inviting members
2121

22-
- Enhanced visibility: Gain insights into user activity, making it easier to monitor access and enforce security policies.
23-
- Streamlined collaboration: Help members collaborate effectively by granting access to shared resources and repositories.
24-
- Improved resource management: Organize and track users within your organization, ensuring optimal allocation of resources.
25-
- Access to enhanced features: Members benefit from organization-wide perks, such as increased pull limits and access to premium Docker features.
26-
- Security control: Apply and enforce security settings at an organizational level, reducing risks associated with unmanaged accounts.
22+
- Enhanced visibility: Gain insights into user activity, making it easier to monitor access and enforce security policies.
23+
- Streamlined collaboration: Help members collaborate effectively by granting access to shared resources and repositories.
24+
- Improved resource management: Organize and track users within your organization, ensuring optimal allocation of resources.
25+
- Access to enhanced features: Members benefit from organization-wide perks, such as increased pull limits and access to premium Docker features.
26+
- Security control: Apply and enforce security settings at an organizational level, reducing risks associated with unmanaged accounts.
2727

2828
For detailed information, see [Manage organization members](/manuals/admin/organization/members.md).
2929

@@ -37,9 +37,9 @@ Integrating Docker with your identity provider streamlines user access and enhan
3737

3838
SSO:
3939

40-
- Simplifies sign in, as users sign in with their organizational credentials.
41-
- Reduces password-related vulnerabilities.
42-
- Simplifies onboarding as it works seamlessly with SCIM and group mapping for automated provisioning.
40+
- Simplifies sign in, as users sign in with their organizational credentials.
41+
- Reduces password-related vulnerabilities.
42+
- Simplifies onboarding as it works seamlessly with SCIM and group mapping for automated provisioning.
4343

4444
For more information, see the [SSO documentation](/manuals/enterprise/security/single-sign-on/_index.md).
4545

@@ -49,22 +49,22 @@ Streamline user provisioning and role management with [SCIM](/manuals/enterprise
4949

5050
With SCIM you can:
5151

52-
- Sync users and roles automatically with your identity provider.
53-
- Automate adding, updating, or removing users based on directory changes.
52+
- Sync users and roles automatically with your identity provider.
53+
- Automate adding, updating, or removing users based on directory changes.
5454

5555
With JIT provisioning you can:
5656

57-
- Automatically add users upon first sign in based on [group mapping](#simplify-access-with-group-mapping).
58-
- Reduce overhead by eliminating pre-invite steps.
57+
- Automatically add users upon first sign in based on [group mapping](#simplify-access-with-group-mapping).
58+
- Reduce overhead by eliminating pre-invite steps.
5959

6060
### Simplify access with group mapping
6161

6262
Group mapping automates permissions management by linking identity provider groups to Docker roles and teams.
6363

6464
It also:
6565

66-
- Reduces manual errors in role assignments.
67-
- Ensures consistent access control policies.
68-
- Help you scale permissions as teams grow or change.
66+
- Reduces manual errors in role assignments.
67+
- Ensures consistent access control policies.
68+
- Help you scale permissions as teams grow or change.
6969

7070
For more information on how it works, see [Group mapping](/manuals/enterprise/security/provisioning/group-mapping.md).

0 commit comments

Comments
 (0)