licenses#25181
Conversation
Document organization licenses for Docker Offload and AI Governance, including manual and automatic assignment from the Admin Console Members page. Add subscription/licenses overview, admin manage-licenses guide, and update subscription navigation weights.
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
github-actions
Bot
added
area/subscription
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
Relocate subscription seat management under admin/organization/manage so it sits with other org admin tasks. Add a redirect alias for /subscription/manage-seats/ and update cross-references across admin, enterprise, billing, and subscription docs.
Move AI Governance and Docker Offload license overview into Scale your subscription and remove the standalone Licenses hub page. Drop the Licenses card from the subscription index and tweak admin org nav weights.
Simplify license assignment and automated assignment on the Members page doc, link prerequisites to the scale page, and note that AI Governance applies to Docker Sandbox usage.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🔴 CRITICAL
4 findings: 1 high (broken anchor links), 3 medium (style, placeholder content, grammar).
|
|
||
| ## What’s next | ||
|
|
||
| - AI Governance |
There was a problem hiding this comment.
[MEDIUM] "What's next" section contains unlinked placeholder items
Both items in the "What's next" section are bare text with no links:
- AI Governance
- Docker OffloadDocker documentation "What's next" sections are expected to contain hyperlinks to related pages. Unlinked entries provide no navigation value and appear to be placeholders for pages not yet created. Either add the destination links or remove these items until the target pages exist.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Co-authored-by: Greg Mondello <72952982+gmondello@users.noreply.github.com>
aevesdocker
left a comment
aevesdocker
left a comment
There was a problem hiding this comment.
A complicated topic that's for sure .... 😳
Don't think the amount of comments I've added means it's bad - far from it, I think you've done vv well to manage the complexity - it's mostly me thinking out loud and reading bits that spark more question whilst I wrap my head around license v seat v subscriptions.
dvdksn
left a comment
dvdksn
left a comment
There was a problem hiding this comment.
I think maybe it would be helpful to disambiguate subs/seats/licenses more clearly at a higher level.
-
Define seats vs. licenses up front: a seat = Team/Business membership; a license = a per-product grant (AI Governance, Offload); separate pools that can coexist on the same member. It'd also help to note that auto-assign does two different things. Desktop sign-in provisions a seat (?), sbx provisions a license, so "Docker Core" doesn't read as a license type.
-
AI Governance fits awkwardly under "Scale your subscription." The page is about scaling a subscription, but AI Governance is standalone. Offload fits, since it sits on top of a seat; AI Governance doesn't. Suggest pulling it out.
- Out of scope and needs a follow-up: between subscriptions, seats, licenses, per-minute consumption, and Gordon, there are several billing models. Right now they're spread across the subscription section and admin pages, and the IA still treats "subscription" as the thing everything stems from, which no longer fits.
Thanks @dvdksn ! Looks like you agree with Allie on some overall feedback. While AI Governance is its own prod with its own billing behavior, the Subscription category is (awkwardly) functioning as an area where decision makers can understand available billable items/learn what is available to purchase (at a high level; i.e., using subscription as you might use it in conversation: I have a subscription for X that I pay for at a regular cadence). A license is a unit of a billable item, which AI Gov / Offload fits under. I agree the current IA around this is not perfect and will prob change as I rework this area. I'm going to keep the license section as is for the MVP on Monday, then revisit it after the fact pending a UI / Design / PM meeting on Tuesday. It's not my favorite either fwiw and had I architected this myself and not inherited it, it would look different. That said, as it stands I do think it's important to explain conceptually what billable items exist in addition to the product people will purchase. Looks like you're echoing what Allie said as well. Def going to add the distinction between seats and licenses for clarity 🖖 |
…ions for seats vs licenses, fixed duplicated weights, clarified sbx login rather than simple sbx invocation, and so on
…o ai-gov-license
ob1dev
left a comment
ob1dev
left a comment
There was a problem hiding this comment.
Looking good. Left some suggestions below. Please take a look.
| title: Manage license assignment | ||
| linkTitle: License assignment | ||
| description: Manage product licenses for your organization, including assignment, revocation, and automatic assignment. | ||
| keywords: licenses, organization, members, Docker Offload, AI governance, license assignment, admin console |
There was a problem hiding this comment.
nitpick: I know we don't have an official public name for DCP/DSoP, but maybe we should add Docker Core in addition to Docker Offload and AI Governance 🤷🏻♂️
| 1. Optional. To bulk assign or revoke licenses, choose the members you want to bulk manage, then select the **Bulk** menu. | ||
| 1. Optional. To manage automatic license assignment, turn off or turn on with the **Automatically assign licenses** toggle. | ||
|
|
||
| You must assign licenses manually, or configure automatic license assignment to consume a license. Inviting a new member to your organization may consume a seat for your Docker Core subscription, but won't auto-assign product licenses by default. Conversely, purchasing a set of licenses won't trigger automatic assignment to existing members. |
There was a problem hiding this comment.
Inviting a new member to your organization may consume a seat for your Docker Core subscription, but won't auto-assign product licenses by default.
opinion: This sounds a bit confusing because for the Docker Core product, 1x seat = 1x license.
Inviting a new member won't consume a seat/license unless the organization owner selects a license for a user they invite, which is optional. Product license will be consumed upon accepting an invitation and joining an organization.
If the organization owner sends an invite without selecting any licenses, and the user accepts it, then a user joins the organization and doesn't consume any seats/licenses.
|
|
||
| ## Automatic license assignment | ||
|
|
||
| Automatic license assignment gives members a product license when they use a supported product for the first time. Automatic license assignment is available for AI Governance licenses. |
There was a problem hiding this comment.
suggestion: since auto-assing via Docker Desktop will automatically provision Docker Core license, I would include it here too.
| Automatic license assignment gives members a product license when they use a supported product for the first time. Automatic license assignment is available for AI Governance licenses. | |
| Automatic license assignment gives members a product license when they use a supported product for the first time. Automatic license assignment is available for Docker Core and AI Governance licenses. |
| - Once the available licenses are exhausted, automatic license assignment will stop until you purchase more licenses or revoke assigned licenses. | ||
| - Members can still use Docker Sandbox or Docker Desktop, but organization policies for those products won't affect their usage. | ||
|
|
||
| AI Governance licenses include SSO and provisioning features regardless of your Docker Core subscription. Automatic license assignment requires [setting up SSO](/manuals/enterprise/security/single-sign-on/connect.md), then [provisioning with SCIM or JIT](/manuals/enterprise/security/provisioning/_index.md). |
There was a problem hiding this comment.
suggestion: for a reader who is unfamiliar with SSO/SCIM/JIT acronyms, it might not be obvious what those mean.
I would replace:
- SSO → Single sign-on (SSO):
- SCIM → System for Cross-domain Identity Management (SCIM)
- JIT → Just-in-Time (JIT)
There was a problem hiding this comment.
though: since the Docker Core license won't be available to all organizations at launch and will only be available to organizations with Docker Team or Docker Business + Docker AI Governance subscriptions, maybe we should add a callout to clarify this. Otherwise, customers without a Docker AI Governance subscription might start looking for Docker Core licenses and become confused why they can't find them in the Members section.
Co-authored-by: Oleg Burov <ob1dev@icloud.com> Co-authored-by: Alexa Kristensen <81787716+akristen@users.noreply.github.com>
6 participants
Draft PR for AI Gov MVP, with guidance around purchasing / what gets billed when purchasing AI Gov.