Skip to main content

TM Custom Admin UI/UX Enhancement Request

This proposal outlines enhancements for the backend admin UI of Typing Mind CUSTOM, developed in response to an invitation from Typing Mind support (Ngoc). While our primary use case is B2B and B2C Coaching, these features may benefit various organizations offering AI access to numerous users, such as educational institutions or online course providers.

A. Access Level Management

We propose the following access level permissions:

  1. Owner
  • Highest level of access and control

  • Full administrative rights, including:

    • Managing all access levels

    • Overseeing super admins, managers, users, and critical platform settings

  1. Super Admin
  • Extensive permissions, just below owner level

  • Ability to adjust settings, except for critical functionalities reserved for the owner (e.g., account deletion, payment information)

  • Ideal for top-level platform managers delegated to manage specific user cohorts

  1. Manager
  • Responsible for day-to-day user management

  • Capabilities include:

    • Adding and managing users

    • Creating and associating AI agents with member accounts

    • Accessing chat messages

    • Restricting member access

    • Assisting with general moderation tasks

This level is crucial for scalability, allowing delegation of platform management tasks

  1. User
  • Core participants of the platform

  • Access to engage with AI based on instructor guidance:

    • Teachers: Assign predefined tasks aligned with weekly topics

    • Coaches: Guide clients through predefined coaching steps for personal growth

    • Corporate trainers: Facilitate new team member onboarding and knowledge assessment

  1. User Cohort
  • Organize users into manageable groups

  • Features:

    • Create and name cohorts

    • Add users to cohorts

    • Associate cohorts with specific Managers

    • Display cohort data in Analytics

While potentially manageable with tags, an additional layer (e.g., "tag categories") could enhance cohort management

Additional access levels (lower priority):

  1. Guest
  • Limited access without full registration

  • Ideal for free trial periods (e.g., 7-day test access)

  1. Restricted User
  • Easily restrict access without complete removal

  • Useful for managing users with lapsed subscriptions or unfulfilled access conditions

B. Chat Features

Given the sensitive nature of chat content in coaching scenarios, we propose:

  • Granular chat access control:

  • Owner: Full access

  • Super-admin and Manager levels:

    • Toggle access for entire cohorts

    • Toggle access for individual users

This level of control supports GDPR compliance for European users

Additional chat functionalities:

  • User message deletion (if technically feasible)

  • Enhanced chat message filtering:

  • By user ID (with dynamic search functionality)

  • By date range

  • By chat content keywords

Facilitates efficient review and feedback processes

C. Analytics Enhancements

  • Interactive "Messages by user" graphs:

  • Click to view last chat message for a specific user and date

  • Consider scalability solutions for large user bases (e.g., zoom functionality, separate window display)

  • Cohort-specific data display in Analytics

Thanks,

Stef

7 comments

Log in to comment and vote

Comments7

  • Sapphire Horizon

    •

    Oct 31, 2024

    Ngoc Nguyen Is there any chance that at least some of the listed features could be taken into consideration by the TypingMind Development team? User roles are probably the most pressing feature. Thanks, Stef

  • Coral Deer

    •

    Sep 14, 2024

    Good idea, up voted

  • Gold Orbit

    •

    Sep 11, 2024

    Yes I’m B2C, so the current seating pricing isn’t ideal for offering free trial. This hurts conversion.

    • Sapphire Horizon

      •

      Sep 12, 2024

      ben Gotcha Ben. Dont forget to upvote this feature request so it becomes more visible to TM :-)

  • Gold Beaver

    •

    Sep 11, 2024

    I am also hugely in favor of an access level overhaul, but I would go at it differently.

    • Create scopes for each action (i.e. read/contribute/owner)

    • Ability to create custom Roles and assign scopes as needed.

    This way, you could could create whatever role you want with whatever permissions you want. This is how cloud platforms like Google and Azure operate.

    • Gold Beaver

      •

      Sep 11, 2024

      This way, I could create a role called "Plugin Creator" and the only access I would give it would be "Plugins.Create" or something like that.

    • Sapphire Horizon

      •

      Sep 12, 2024

      BH Love that, BH. Dont forget to upvote this feature request so it becomes more visible to TM :-)