You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/manuals/admin/organization/activity-logs.md
+2-4Lines changed: 2 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,6 +7,8 @@ aliases:
7
7
- /docker-hub/audit-log/
8
8
---
9
9
10
+
{{< summary-bar feature_name="Activity logs" >}}
11
+
10
12
Activity logs display a chronological list of activities that occur at organization and repository levels. It provides a report to owners on all their member activities.
11
13
12
14
With activity logs, owners can view and track:
@@ -18,10 +20,6 @@ For example, activity logs display activities such as the date when a repository
18
20
19
21
Owners can also see the activity logs for their repository if the repository is part of the organization subscribed to a Docker Business or Team plan.
20
22
21
-
> [!NOTE]
22
-
>
23
-
> Activity logs requires a [Docker Team or Business subscription](/manuals/subscription/_index.md).
Copy file name to clipboardExpand all lines: content/manuals/admin/organization/insights.md
+6-3Lines changed: 6 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,9 +4,7 @@ keywords: organization, insights
4
4
title: Insights
5
5
---
6
6
7
-
> [!NOTE]
8
-
>
9
-
> Insights requires a [Docker Business subscription](../../subscription/details.md#docker-business) and administrators must [enforce sign-in](/security/for-admins/enforce-sign-in/). This ensures users sign in with an account associated with their organization.
7
+
{{< summary-bar feature_name="Insights" >}}
10
8
11
9
Insights helps administrators visualize and understand how Docker is used within
12
10
their organizations. With Insights, administrators can ensure their teams are
@@ -24,6 +22,11 @@ Key benefits include:
24
22
- Optimized license use. Ensure that developers have access to advanced
25
23
features provided by a Docker subscription.
26
24
25
+
## Prerequisites
26
+
-[Docker Business subscription](../../subscription/details.md#docker-business)
27
+
- Administrators must [enforce sign-in](/security/for-admins/enforce-sign-in/) for users
28
+
- Insights enabled by your Customer Success Manager
Copy file name to clipboardExpand all lines: content/manuals/desktop/setup/install/enterprise-deployment/pkg-install-and-configure.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,7 @@ params:
11
11
text: EA
12
12
---
13
13
14
-
{{% restricted title="Early Access" %}}
15
-
The PKG installer is currently an [Early Access](/manuals/release-lifecycle.md) feature and is available to all company and organization owners with a Business subscription and Docker Desktop version 4.36 and later.
16
-
{{% /restricted %}}
14
+
{{< summary-bar feature_name="PKG installer" >}}
17
15
18
16
The PKG package supports various MDM (Mobile Device Management) solutions, making it ideal for bulk installations and eliminating the need for manual setups by individual users. With this package, IT administrators can ensure standardized, policy-driven installations of Docker Desktop, enhancing efficiency and software management across their organizations.
Learn how to configure and set up a private marketplace with a curated list of extensions for your Docker Desktop users.
17
15
18
-
It is designed specifically
19
-
20
16
Docker Extensions' private marketplace is designed specifically for organizations who don’t give developers root access to their machines. It makes use of [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md) so administrators have complete control over the private marketplace.
21
17
22
18
## Prerequisites
@@ -85,7 +81,7 @@ Each setting has a `value` that you can set, including a `locked` field that let
85
81
86
82
To find out more information about the `admin-settings.json` file, see [Settings Management](/manuals/security/for-admins/hardened-desktop/settings-management/_index.md).
87
83
88
-
## Step three: List allowed extensions
84
+
## Step three: List allowed extensions
89
85
90
86
The generated `extensions.txt` file defines the list of extensions that are available in your private marketplace.
This creates an `extension-marketplace` directory and downloads the marketplace metadata for all the allowed extensions.
141
137
142
-
The marketplace content is generated from extension image information as image labels, which is the [same format as public extensions](extensions-sdk/extensions/labels.md). It includes the extension title, description, screenshots, links, etc.
138
+
The marketplace content is generated from extension image information as image labels, which is the [same format as public extensions](extensions-sdk/extensions/labels.md). It includes the extension title, description, screenshots, links, etc.
143
139
144
140
## Step five: Test the private marketplace setup
145
141
@@ -186,7 +182,7 @@ When you select the **Extensions** tab, you should see the private marketplace l
186
182
187
183
Once you’ve confirmed that the private marketplace configuration works, the final step is to distribute the files to the developers’ machines with the MDM software your organization uses. For example, [Jamf](https://www.jamf.com/).
188
184
189
-
The files to distribute are:
185
+
The files to distribute are:
190
186
*`admin-settings.json`
191
187
* the entire `extension-marketplace` folder and its subfolders
0 commit comments