Design: Review workflow for managing permissions in Django admin

[Katherine-Osos]

Sub-issue description

Design should review any added tables/fields to ensure they're displayed logically and consistently with other patterns on the page and are appropriately contextualized for an Analyst.

In scope:

• Django tables related to permissions
  • Portfolio invitations
  • User portfolio permissions
  • Portfolios (section for "portfolio members")
• Emails related to adding / removing a member and editing permissions (initiated from Django admin)

Out of scope:

• All member/permission functionality within the registrar
• Emails related to adding / removing a member and editing permissions (initiated from registrar)

Acceptance criteria

• Designer reviews the member pages described above
• Designer documents any changes needed within the designated slack channel
• Developer determines which changes are small enough to be completed as part of this ticket; then makes those changes
• Developer creates tickets for larger updates that need to be addressed later

Additional context

NOTE: Dev effort on this shouldn't be more than a "2" (2 full work days).

• Dev is responsible for answering questions from design, making minor changes (such as those that we would normally make on a PR).
• Anything that would take more than 4 hours to complete alone should be its own ticket. (communicate with Alysia).

Discussions for this design review should take place in this Slack channel: < insert link to slack channel >

[github-actions]

cc/ @Katherine-Osos — adding you to this design-review issue!