Skip to content

Add detailed admin portal flow doc#8

Open
SheeladityaVinayKumar wants to merge 8 commits into
mainfrom
docs/admin-portal-flow
Open

Add detailed admin portal flow doc#8
SheeladityaVinayKumar wants to merge 8 commits into
mainfrom
docs/admin-portal-flow

Conversation

@SheeladityaVinayKumar

Copy link
Copy Markdown

What

Adds docs/admin-portal-flow.md — a detailed, step-by-step flow for the admin portal, the V1 primary surface (college / TPO is the primary V1 user per architecture.md).

Contents

  • Three roles — student, alumni, admin; admin runs the portal and manages both student and alumni records.
  • Admin flow [V1]: login/auth → full college setup (identity, details, images/branding, academic config) → dashboard → manage alumni & student records (add, invite, batch invite, search/filter, edit).
  • Later phases [tagged]: verification & approval, moderation, events, insights/analytics, exports (booklet/CSV).
  • College setup includes full college details + images so the college can present itself well (marketing / attracting admissions), tying back to the "market the college" motivation in architecture.md.

Conventions followed

  • College-agnostic — nothing KEC-specific hardcoded; all details/images entered by the admin.
  • [V1] vs [Later] tags throughout; open decisions kept as TODOs linked to research.md (auth, verification, data source, data model, student→alumni transition).
  • Plain language, living-doc style consistent with the rest of docs/.

🤖 Generated with Claude Code

Document the V1 admin flow: login, full college setup (details +
images), and managing student and alumni records. Capabilities tagged
[V1] vs [Later]; open items kept as TODOs linked to research.md.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@SheeladityaVinayKumar SheeladityaVinayKumar self-assigned this Jun 12, 2026
@SheeladityaVinayKumar
SheeladityaVinayKumar requested review from ashutosh-pokhriyal23 and pphulara and removed request for pphulara June 12, 2026 09:53
Embed a GitHub-rendered flowchart at the top of the doc (login,
college setup, manage alumni/student records). Keep the ASCII version
in a collapsible details block as a text fallback.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
SheeladityaVinayKumar and others added 6 commits June 12, 2026 15:52
A student automatically becomes an alumnus when their batch/session
completes; no manual admin step. Resolve the related TODO and update
the roles table, flowchart, and open-questions list.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Admins do not self-register; the research team provisions each college
and provides the admin login credentials for V1. Reflect this in both
the Login section and the flowchart.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Drop the role-routing and tenant-existence branches (research team
provisions the college, so it always exists at login). Redesign the
flowchart with numbered phases, a legend, and rules baked into nodes
so it reads on its own. Rewrite the Login section to match.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Add a title banner, switch slanted note shapes to rectangles so text
no longer clips, label the entry Login / Signup, mark account creation
as not-yet-decided (research team's work), and complete the
batch-transition label. Align the Login section text to match.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Break the 'becomes an Alumnus' and 'Later' nodes onto multiple lines
so the boxes grow taller and the full text shows instead of clipping.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Self-submitted student/alumni details now go through an admin review
step (submit -> review -> live) instead of going live automatically.
Mark the exact details/fields collected as not-yet-decided, pending
research. Reflect both in the flowchart and the §4 text.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants