Update base permissions docs to explicitly state changes impact new & existing customers. - #24145
Conversation
Automatically generated comment ℹ️This comment is automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
fpt: Free, Pro, Team |
|
👋 @adamrr724 Thanks for opening an issue and submitting a PR! I edited your PR slightly, removing the word I'll get this triaged for review! ⚡ |
sophietheking
left a comment
There was a problem hiding this comment.
@adamrr724 👋 thanks for opening this PR! I left a suggestion to update the note slightly.
Please feel free to @mention me here to get this merged!
…ns-repositories/setting-base-permissions-for-an-organization.md Co-authored-by: Sophie <29382425+sophietheking@users.noreply.github.com>
|
Hi @sophietheking! All committed and ready for merge. Thank you so much! |
|
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Why:
Closes #24144
What's being changed (if available, include any code snippets, screenshots, or gifs):
Adding a note that states base permissions changes take effect on both new and existing customers.
Check off the following: