Skip to content

Administrative IA designed #4407

@jordanh

Description

@jordanh

Issue - Enhancement

As the IT administrator of Parabol—either cloud-hosted or privately hosted—I want to:

  • configure SAML for one (or more) domains
  • 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
  • view an audit log of significant events: logins, logouts, billing cycle events, CRUD events for User, Org, Team, and Meeting objects
  • see overall usage statistics: number of users, active users, team names/sizes, team meeting frequency
  • enable disable integrations organization wide
  • view team details: membership, activity, integration usage

Questions to consider during design

  • Does this design support org of orgs/team of teams? Is that a pre-requisite?
  • Are there different permission roles (billing leader vs. super admin vs. team lead vs regular user) and how do they interact with the design?
    • Note: a tension today are team leads not believing there are X teams and Y users attached to an org
  • How is this navigated to in our overall IA?

Acceptance Criteria (optional)

  • A series of lo-fi designs

  • Feedback collected from the internal team

  • Estimated effort: 15 points (see CONTRIBUTING.md)

See also:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions