You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a portfolio member
I want to be notified when I've been removed from the portfolio
so that I know I can no longer access it in the registrar.
Acceptance criteria
This new email should be sent to users when they're removed from a portfolio.
Registrar: This email should be sent if the person was removed via the registrar
Django admin: No email should be sent if the person was removed via Django admin, User Portfolio Permissions table.
Add static messaging in Django:
Add a static message to the top of the "Are you sure?" UserPortfolioPermissions deletion page that reads: "If you remove someone from a portfolio here, it will not send any emails when you click "save."
Add a static message to the top of the "Are you sure?" PortfolioInvitation deletion page that reads: "If you cancel the portfolio invitation here, it won't trigger any emails. It also won't remove the user's portfolio access if they already logged in. Go to the User Portfolio Permissions table if you want to remove the user from a portfolio."
Link to the " UserPortfolioPermissions" table in that message.
Use slim blue alert, placed right below the heading "Are you sure?" for both tables.
@Katherine-Osos so if a user is removed from the registrar and was an admin then: 1.) an email would be sent saying this user has been removed 2) an email would be sent to all other admins saying that an admin has been removed. So 2 different emails get sent, correct? Or should this email only be sent if the user is a non-admin member?
Adding refinement so I remember I asked a question here.
Issue description
As a portfolio member
I want to be notified when I've been removed from the portfolio
so that I know I can no longer access it in the registrar.
Acceptance criteria
Add static messaging in Django:
Additional context
Links to other issues
The text was updated successfully, but these errors were encountered: