mirror of
https://github.com/docker/docs.git
synced 2026-10-23 18:09:02 +03:00
ec568fb193997abb62fc206183b30ba01498291d
## Summary - Document that member `PUT` `role` accepts a custom role **name**, not only `owner` | `editor` | `member`. - Document `role` on team `PATCH` (core or custom role name) and on `org_group` so the PATCH 200 can include the assigned role. - Add `Editor` to `org_member.role` (title case). Live responses already return it; the old enum was Owner / Member / Invitee only. ## Test plan PM must confirm before merge: - [ ] Member PUT 200: after assigning a custom role (body is not the previous core role), is `role` still a core value (`Owner` / `Editor` / `Member`), or is it the custom role **name**? If it is the custom name, drop the `org_member.role` enum in a follow-up and describe a string (core or custom name). If it stays a core value, this PR's enum (`Owner` | `Editor` | `Member` | `Invitee`) is enough. - [ ] List members: same field. Confirm a user with a custom role lists as a core value vs the custom name. - [ ] Casing: request stays lowercase (`editor`); response stays title case (`Editor`). Confirm that split is real. - [ ] Team PATCH 200: confirm `org_group.role` is present and is the value just set (core or custom name). - [ ] Team assignment is PATCH-only, not PUT. - [ ] Unknown role names return an error; do not document them as valid. - [ ] Custom role **name** (not label or UUID) is the request identifier, matching Docker Home. --------- Co-authored-by: Cursor <cursoragent@cursor.com>
Docs @ Docker
Welcome to the Docker Documentation repository. This is the source for the Docker Docs Website.
Feel free to open pull requests or issues. Our docs are completely open source, and we deeply appreciate contributions from the Docker community!
Provide feedback
We’d love to hear your feedback! To submit feedback:
- Click New issue on the docs repository, or
- Click Request changes in the right column of every page on docs.docker.com, or
- Click Give feedback on every page in the docs.
To get community support, use the Docker Community Slack. Personalized support is available through the Docker Pro, Team, and Business subscriptions. See Docker Pricing for details.
If you have an idea for a new feature or behavior change in a specific aspect of Docker or have found a product bug, file an issue in the project's repository.
Contribute to Docker docs
We welcome contributions! To get started:
- CONTRIBUTING.md - Contribution workflow and setup
- STYLE.md - Writing style and content guidelines
- COMPONENTS.md - Component and shortcode usage
Copyright and license
Copyright 2013-2026 Docker, Inc., released under the Apache 2.0 license.
Description
Languages
Markdown
95.1%
HTML
2.3%
CSS
0.7%
Go
0.7%
JavaScript
0.7%
Other
0.2%