Enhanced User Management & Auth Analytics in Appwrite Console

[fmt-Println-MKO]

🔖 Enhancement description

Improve the Appwrite Console (Auth section) by:

1. Adding sorting and filtering capabilities to the Users table.
2. Extending Auth analytics with user-related business metrics (logins, registrations, sessions).

This would significantly improve usability for projects with a growing user base and reduce the need to query the API externally for basic insights.

---

1️⃣ Improved Users Table (Sorting & Filtering)

Problem

The current Users table in the Auth section lacks advanced sorting and filtering functionality. As the number of users grows, it becomes increasingly difficult to efficiently manage, inspect, and analyze users.

---

Proposed Enhancements

A. Column Sorting

Enable ascending/descending sorting on all visible columns, including (but not limited to):

• Name
• Email
• Email verification status
• Phone verification status
• Registration date
• Last login date
• Status (enabled / disabled)
• User ID

Requirements:

• Sorting triggered by clicking on the column header.
• Clear visual indicator of sort direction (↑ / ↓).
• Server-side sorting to ensure scalability with large datasets.

---

B. Column-Based Filtering

Add per-column filtering options such as:

• Text fields (e.g. name, email): partial match search
• Boolean fields (e.g. verified/unverified)
• Date fields (e.g. registration date, last login): date range filter
• Status fields: enabled / disabled

Requirements:

• Filters should be combinable (e.g. verified AND registered in last 30 days).
• Active filters should be clearly visible.
• One-click reset/clear filters option.
• Server-side filtering for performance.

---

2️⃣ Extended Auth Analytics (User-Centric Metrics)

Problem

Current analytics focus mainly on traffic and lack user-focused authentication metrics. For many applications, understanding user activity and growth is critical.

---

Proposed Enhancements

Extend the Auth section with a dedicated analytics dashboard including:

---

A. Authentication Activity

• Number of logins per selected time range
• Number of failed login attempts
• Number of active sessions
• Session creations per time range

---

B. User Growth Metrics

• Registrations per selected time range
• Cumulative total users over time
• Net growth (registrations − deletions)

---

C. Session Insights

• Active sessions over time
• Average sessions per user
• Session expiration trends

---

D. Time Range Controls

Support selectable time ranges:

• Last 24 hours
• Last 7 days
• Last 30 days
• Custom date range

---

E. Visualization

• Line charts for trends (logins, registrations)
• Bar charts for aggregated views
• Numeric summary cards (e.g. “123 registrations in selected period”)

🎤 Pitch

✅ Expected Impact

• Improved usability for managing large user bases
• Faster operational workflows inside the Console
• Better visibility into key business metrics
• Reduced need for external analytics tooling or API scripts
• Stronger alignment with real-world SaaS monitoring needs

👀 Have you spent some time to check if this issue has been raised before?

• I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

• I have read the Code of Conduct

[bittoby]

Can I pick this up?

[eldadfux]

Hey @fmt-Println-MKO thanks for sharing all of this, this is definitely something we want to act on. I'll chat with the team about it and we'll keep monitoring for feedback on this thread.