Designed a fully-featured account members/seats UI

[ackernaut]

Background

Folks want the ability to better review and manage their list of organization members (all seats on the account).

This was bulleted here in #5661

bulk administer users: filter a list by search criteria bulk select to pause or remove them search criteria: email, preferred name, create/last active dates, optional: team name

Mentioned here

Is it possible to see the member list alphabetically so it’s easier to search?

And mentioned in this Loom sometime after 27:14 .

We could write these as a few user job stories:

When managing licensed seats on my enterprise account, I want the ability to find inactive users, or users who are not part of my organization (by email), so that I can free up active seats and manage license consumption

When reviewing members on my account, I want to search and filter so that I can identify folks who are inactive so that I can remove old accounts

A few snapshots

Today

From the Oct 2021 prototype

• Here’s the prototype
• Here’s the view in Figma
• Feel free to comb through these transcripts for verbatim comments
• Some of these comments were about the user table. Others were about the most active members table.

Acceptance criteria

• Proposed a members ‘rich table’ interface concept addressing these concerns:
  • This UI component can fit in a regular page layout regardless of final navigation or IA concerns of the admin area
  • How might this adapt for mobile?
  • Admins can perform fuzzy search; maybe even using specific search queries in the future
  • What data fields do we present per member? The UI component has table headers with labels for the fields that are presented. A little discovery work may be necessary here, but a minimal we can find a good place to start
  • Admins can sort by table headers where logical and reasonable
  • Consider if the table header is sticky (it doesn’t scroll out of view) so that folks remember what the fields are
  • Admins can use filters, especially filters like active, inactive
  • Stretch goal: folks can filter which members have or do not have the top level email domain (e.g. find users with or without @parabol.co)
  • How do we load a lot of members on a large account? Lazy loading?
  • Can admins export user data? Which fields? What’s the control look like? What’s the workflow like? See #5665
  • What other admin actions can be performed? How are they performed? Today members can leave an account. Today billing leaders can promote or remove the billing leader role, and remove members

Estimated effort

• 21 hours

[github-actions[bot]]

Stale issue

[avivapinchas]

Value: 3 See the discussion in Sprint Poker #​​1

Powered by Parabol

[avivapinchas]

Effort: L See the discussion in Sprint Poker #​​1

Powered by Parabol

[gcrickman]

An Enterprise customer 🔒 asks:

Are there any plans for Parabol to build functionality to manage teams centrally through the organization at some point? ie be able to list them, add users to them or remove folks from a team by a super admin?

[github-actions[bot]]

Stale issue

[jordanh]

Likely we'll reopen this as it is a perennial need and we even have a SBIR proposal going out that would continue the design/implementation work here. That notwithstanding, iceboxing for now

[enriquesanchez]

We reviewed some feedback around this during today's User feedback retro 🔒:

Can I suggest to improvements for the portal:

• The exact license information (numbers, renewal date) somewhere visible;
• Payment history, upcoming payments, payment method, etc (would be helpful especially when introducing new billing admins)
• Last login/usage date

Also added to Problems, Ideas & Opportunities 🔒