Add Technician role to role-based access documentation#37861
Add Technician role to role-based access documentation#37861rachaelshaw merged 11 commits intodocs-v4.82.0from
Conversation
Added Helper role with specific permissions to the role-based access documentation.
Corrected capitalization of 'Helper' in roles table.
Updated role terminology from 'Helper' to 'Technician' and adjusted permissions table accordingly.
melpike
changed the title
|
@melpike, has anything changed since I last reviewed? |
@mike-j-thomas No, I had to switch the repo to the correct doc and I just resolved some conflicts. |
noahtalerman
requested review from
lucasmrod
and removed request for
mike-j-thomas
|
UPDATE: @noahtalerman: Chatted w/ Mike T and added @lucasmrod as the technical reviewer. @melpike, language looks good, but I don't have context for the permissions. Please can you add a technical reviewer? |
Hey @lucasmrod when you get the chance, can you please verify that these changes are accurate? |
rachaelshaw
temporarily deployed
to
Docker Hub
GitHub Actions
Inactive
|
@melpike I noticed that there were extra copies of the old permissions tables below the new ones, with a few items at the bottom that didn't make it into the new tables (probably because merge conflicts after the most recent release). I went ahead and made the fix in this commit, will you double-check the diff and make sure the changes look right to you? |
|
@rachaelshaw Sorry about that!
Your PR looks correct! |
If we're comfortable with advertising the new role on the website a bit early, I think adding the updated permissions table to `main` as soon as possible will help avoid some nasty merge conflicts in upcoming release branches. Changes: + Copied over updated roles table from @melpike's [PR](#37861) + Added "coming soon" note w/ link to the user story --------- Co-authored-by: melpike <79950145+melpike@users.noreply.github.com>
rachaelshaw
temporarily deployed
to
Docker Hub
GitHub Actions
Inactive
6 participants
Added Helper role with specific permissions to the role-based access documentation.
Related issue: Resolves #35696