licenses: document invite-time license assignment - #25678
Conversation
Admins can assign a product license when inviting a member, but the license page claimed inviting consumes a seat or license immediately. The pool is deducted on accept, and an invitee who accepts after the pool empties joins without a license and without any notification, so admins need to confirm available licenses before bulk invites. Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Deploy Preview for docsdocker ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
The changes cleanly document the new invite-time license assignment feature. The new section in manage-licenses.md is well-structured — it explains the workflow, the deferred-deduction behavior, and the edge case where licenses run out, all in clear, concise prose that matches Docker's style. The brief cross-reference paragraph added to members.md integrates smoothly. No AI-isms, no markdown issues, no missing redirects, no front-matter problems, no high or medium severity issues found.
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Move invite-time license assignment under Licenses and invites, tighten the invite procedure and accept note, and point members.md at the new section anchor. Co-authored-by: Cursor <cursoragent@cursor.com>
Point the Docker Sandboxes link at /manuals/ai/sandboxes/_index.md so htmltest resolves the target. Co-authored-by: Cursor <cursoragent@cursor.com>
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟢 APPROVE
This PR cleanly documents the invite-time license assignment feature. The new sections in both manage-licenses.md and members.md follow Docker style conventions: no hedge words, no "allows/enables you to" violations, correct use of "select" over "click", bold only on UI elements, and internal links correctly use the /manuals/ prefix with valid anchor slugs. The brief "Accept invites" section is appropriately scoped for the admin audience — it informs admins what the invitee must do next, rather than duplicating invitee-facing guidance. Scope and tone match the existing document character.
docker-agent
left a comment
docker-agent
left a comment
There was a problem hiding this comment.
Assessment: 🟡 NEEDS ATTENTION
|
|
||
| You must assign licenses manually, or configure automatic license assignment to consume a license. Inviting a new member to your organization consumes a seat or license if you select a product in **Licenses (optional)** during the [invite flow](/manuals/admin/organization/manage/members.md), but won't auto-assign product licenses by default. Conversely, purchasing a set of licenses won't trigger automatic assignment to existing members. | ||
| A user invited with license assignment must check their Docker Home | ||
| notifications to accept the invite and assign the license. |
There was a problem hiding this comment.
[MEDIUM] "Accept invites" section implies two user actions, contradicting the earlier automatic-assignment explanation
The phrase "accept the invite and assign the license" lists two actions connected by "and", which reads as if the user must both accept the invitation and then separately assign the license. However, the "Licenses and invites" section above explains that Docker assigns the license automatically when the invitee accepts — the user only needs to accept.
Consider rewording to make clear that acceptance alone triggers assignment, for example:
A user invited with license assignment must check their Docker Home notifications to accept the invite. Docker automatically assigns the license upon acceptance.
craig-osterhout
left a comment
craig-osterhout
left a comment
There was a problem hiding this comment.
lgtm
+1 to the agent nit
ob1dev
left a comment
ob1dev
left a comment
There was a problem hiding this comment.
Looking good, please see my suggestions...
| When you invite someone to your organization, you can assign them a product | ||
| license before they accept the invitation. Docker deducts the license when the | ||
| invitee accepts the invitation: |
There was a problem hiding this comment.
suggestion: It sounds a bit ambiguous that a license might be assigned upon sensing an invite. How about rephrasing it...
| When you invite someone to your organization, you can assign them a product | |
| license before they accept the invitation. Docker deducts the license when the | |
| invitee accepts the invitation: | |
| When you invite someone, you can select a product license to assign when they | |
| accept. Docker doesn't reserve or deduct the license at invite time; assignment | |
| happens on acceptance: |
| - If no licenses remain when they accept, they still join your organization, | ||
| but without a license. Docker doesn't notify you or the invitee in this case. |
There was a problem hiding this comment.
segession: I would move the following sentence to a callout block: Docker doesn't notify you or the invitee in this case since it's a current limitation of how it's implemented.
| Confirm your available licenses before sending invitations in bulk. If licenses | ||
| run out, invitees can still join your organization but won't have an active | ||
| license. |
There was a problem hiding this comment.
issue: Even if an organization owner confirms available licenses before sending invitations in bulk, there is no guarantee they will be available for each invitee by the time they accept an invite individually.
I would rephrase it a bit...
| Confirm your available licenses before sending invitations in bulk. If licenses | |
| run out, invitees can still join your organization but won't have an active | |
| license. | |
| Licenses aren't reserved for pending invitations, so they must still be | |
| available when each invitee accepts. Monitor availability on the Members page | |
| while invitations are pending. |
| Assigning a license on invite is an alternative to assigning one manually after | ||
| they join, or relying on automatic license assignment the first time they use a | ||
| supported product. To assign a license when you invite a member: |
There was a problem hiding this comment.
nitpick: "relying on automatic license assignment the first time they use a supported product" reads as a generally available alternative.
Per the Automatic license assignment section on this same page, it's available only for AI Governance licenses, with Docker Core auto-assignment limited to organizations that purchase AI Governance.
Maybe something like or, where available, relying on automatic license assignment... adds a qualifier so readers on other plans don't infer they have that option.
| 1. Enter the email addresses or Docker IDs of the people you want to invite, | ||
| then assign their | ||
| [role](/manuals/enterprise/security/roles-and-permissions/_index.md). | ||
| 1. Under **Licenses (optional)**, select a license that's available to your |
There was a problem hiding this comment.
issue: The box Licenses (optional) is multi-select. Therefore...
| 1. Under **Licenses (optional)**, select a license that's available to your | |
| 1. Under **Licenses (optional)**, select one or more licenses that are available to your |
| You can also assign an invitee a product license. | ||
| Unlike a seat, a license isn't deducted from your organization's available | ||
| licenses until the invitee accepts. See | ||
| [Licenses and invites](/manuals/admin/organization/manage/manage-licenses.md#licenses-and-invites). |
There was a problem hiding this comment.
suggestion: Same as above "assign" → "select"... License(s) are selected upon invite and are assigned upon acceptance.
| You can also assign an invitee a product license. | |
| Unlike a seat, a license isn't deducted from your organization's available | |
| licenses until the invitee accepts. See | |
| [Licenses and invites](/manuals/admin/organization/manage/manage-licenses.md#licenses-and-invites). | |
| You can also select a product license for an invitee; Docker assigns it when | |
| they accept. Unlike a seat, a license isn't deducted from your organization's | |
| available licenses until the invitee accepts. See | |
| [Licenses and invites](/manuals/admin/organization/manage/manage-licenses.md#licenses-and-invites). |
| A user invited with license assignment must check their Docker Home | ||
| notifications to accept the invite and assign the license. |
There was a problem hiding this comment.
issue: "must check their Docker Home notifications" that's one option. The invitation email is the primary path.
| A user invited with license assignment must check their Docker Home | |
| notifications to accept the invite and assign the license. | |
| A user can accept from the link in their invitation email or from their Notifications Center. | |
| If the selected license is available, Docker assigns it automatically upon acceptance. |
FYI, Notifications Center is globally available in the header from App or Hub UIs.
4 participants
Assign license on invite feature