[Docs] Document team deletion behavior and resource handling#1089
[Docs] Document team deletion behavior and resource handling#1089PARTH-TUSSLE wants to merge 1 commit into
Conversation
Signed-off-by: PARTH-TUSSLE <parthgartan26feb@gmail.com>
|
Yay, your first pull request! 👍 A contributor will be by to give feedback soon. In the meantime, please review the Layer5 Community Welcome Guide and sure to join the community Slack. |
There was a problem hiding this comment.
Code Review
This pull request adds a new "Delete a Team" section to the documentation, detailing the effects of team deletion with an example. The reviewer suggested removing a redundant alert box that repeats information already covered in the bullet points and introduction to improve readability.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
|
|
||
| {{< alert type="info" title="Team Deletion" >}} | ||
| Deleting a team removes team memberships and ownership, but does not delete user accounts or associated resources. | ||
| {{< /alert >}} |
|
🚀 Preview deployment: https://layer5io.github.io/docs/pr-preview/pr-1089/
|
|
@PARTH-TUSSLE Thank you for your contribution! Let's discuss this during the website call tomorrow at 5:30 PM IST | 7 AM CST Add it as an agenda item to the meeting minutes, if you would 🙂 |
Notes for Reviewers
Added documentation describing team deletion behavior, including its impact on memberships, ownership, user accounts, and associated resources.
Preview for the fix :-
This PR fixes #1086
Signed commits