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.
2 participants
Assign license on invite feature