Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(organizations): disable email updates for regular organization m…
…embers TASK-997 (#5233) ### 🗒️ Checklist 1. [x] run linter locally 2. [x] update all related docs (API, README, inline, etc.), if any 3. [x] draft PR with a title `<type>(<scope>)<!>: <title> TASK-1234` 4. [x] tag PR: at least `frontend` or `backend` unless it's global 5. [x] fill in the template below and delete template comments 6. [x] review thyself: read the diff and repro the preview as written 7. [ ] open PR & confirm that CI passes 8. [x] request reviewers, if needed 9. [ ] delete this section before merging ### 📣 Summary <!-- Delete this section if changes are internal only. --> <!-- One sentence summary for the public changelog, worded for non-technical seasoned Kobo users. --> UI for changing emails is disabled for `Members` of a multi-member organization. ### 👀 Preview steps 1. Make sure your user's email is correct in both the user section of the django admin as well as the email address section. If there is a difference it would only show the former here. See https://www.notion.so/kobotoolbox/task-1236 2. Make an MMO that has an owner, admin, and a member, as well as a regular user 3. Navigate to the account settings page 4. Visit the security section 5. If the user is a regular user, or an MMO owner or admin, they should be able to change their email address as normal 6. If the user is a member of an MMO the text box and button should be gone ### 📖 Description <!-- Delete this section if summary already said everything. --> <!-- Full description for the public changelog, worded for non-technical seasoned Kobo users. --> Remove the text box and button entirely if the user is a `member`. Replaced with just text of the email returned from `/me`. ### 💭 Notes <!-- Delete this section if empty. --> <!-- Anything else useful that's not said above,worded for reviewers, testers, and future git archaeologist collegues. Examples: - screenshots, copy-pasted logs, etc. - what was tried but didn't work, - conscious short-term vs long-term tradeoffs, - proactively answer likely questions, --> Make sure the user either has the proper email reflected in the user section of the django admin or was created through an email confirmation link. See https://www.notion.so/kobotoolbox/task-1236 --------- Co-authored-by: James Kiger <[email protected]>
- Loading branch information