Organization overview page #532
Description
Goals
- Provide organization admins with an easy to understand overview of their organization’s profile, verification status, billing status, membership, and settings.
- Provide organization members with a clear list of their fellow members and organization admins.
- Provide signed-in users who are not members an easy way to evaluate the membership of the organization and request membership.
- Provide MuckRock staff with quick actions for organization moderation and management.
Design
We’ll redesign organization pages to carry through a consistent design from user account pages. We’ll surface important information like membership and billing along with common management actions for org admins.
Sections
Similar to account pages, org pages will be broken into sections: Profile, Verification, Members, Plan, and Security.
Profile
This section will help admins see how their organization will be visible to other MuckRock users when it appears in lists, search results, and the organization’s public page (if not private).
Editing the profile will take admins to /organizations/<slug>/edit
Verification
This section will reuse and extend our existing verification components to explain the verified or unverified state of orgnizations. When an organization is unverified, we’ll provide an action for members or admins to request verification (linking to our Airtable form):
Members
This section will reuse our member list from the Update member management page task. On the org overview page, we’ll show an indicator when there’s pending invitations or requests, along with an action to invite more members.
Plan
This section will reuse the plan component from the account overview page:
There are a few stylistic enhancements to the component here—any improvements we make should also get included in account pages, as well.
Security
The security section will offer org admins with controls over access to their organization:
Three different settings will be included here:
- Whether the organization accepts requests to join
- Whether the organization allows auto-joining by users with approved emails
- Whether the organization requires two-factor authentication
These settings will be implemented in separate, more focused issues, so our goal here is just to create the section and the container that supports the presentation of security settings.
Access by role
The organization page will be accessed by users in different roles, and should account for this by showing different levels of detail to different kinds of users.
Org Admins
Org admins should have the most visibility into information and actions. All section will be available to them:
Org Members
Org members should have visibility into the org’s profile, members, and verification:
MuckRock Staff
MuckRock staff should have the same access as org admins, with additional staff-only controls:
Signed in, but not a member
Users who are viewing a public organization, but who don’t belong to it, should see more of the org’s profile and a list of its public members. They should also see a button to Request to Join the organization, if that action is enabled by admins:
Signed out
For anonymous users viewing a public org, they should only be able to see profile data and a list of the admins:
