Repository navigation
Authentication and Roles
This page explains how users access Tapitude Creator Hub and what each role is allowed to do.
Tapitude currently has two authenticated roles:
admin
creatorPublic viewers do not have accounts.
Admins manage creator accounts and oversee the creator platform.
Admins can:
- Log in to the admin dashboard.
- View basic admin dashboard counts.
- View creator accounts.
- Create creator accounts manually.
- Edit creator account details.
- Disable or reactivate creator accounts.
- Delete creator accounts.
Current admin pages live under:
/adminAdmin routes are protected by:
- Session authentication
-
adminrole checks - CSRF protection on POST requests
Creators manage their own Tapitude profile and posts.
Creators can:
- Log in to the creator dashboard.
- View dashboard metrics.
- Edit their profile and public brand information.
- Create a new post shell.
- Edit post text, publish timing, media display mode, and media.
- Upload or delete media for their own posts.
- Delete their own posts.
Current creator pages live under:
/creatorCreator routes are protected by:
- Session authentication
-
creatororadminrole checks - Active-account checks
- CSRF protection on POST requests
- Ownership checks in controller queries
Public viewers do not log in.
Viewers can:
- Open a creator public content hub.
- Load published posts for that creator.
- Like posts.
Current public content hub URL pattern:
/content-hub/:creatorSlugOlder wiki references to /c/:creatorSlug and /p/:postSlug do not match the current codebase.
Current user statuses:
active
disabledAn active creator can log in and manage content.
A disabled creator should not be able to use the creator dashboard. The current content hub controller also checks the creator account status and hides public content hubs for inactive creator accounts.
Admin deletion currently removes the user and creator profile. Related content and media cleanup should be reviewed before production handoff.
- User submits the login form at
/auth/login. - The app looks up the user by email.
- The app checks account status.
- The app compares the password with the stored bcrypt hash.
- The app stores the user id in the session.
- The app redirects admins to
/admin/dashboard. - The app redirects creators to
/creator/dashboard.
The app uses:
- Bcrypt password hashing.
- Session cookies.
- MongoDB-backed sessions.
- Current-user attachment middleware.
- Role checks.
- CSRF protection.
Recommended follow-up:
- Confirm every form includes
_csrf. - Ensure
.env.exampleincludesCSRF_SECRET. - Continue owner-scoping all creator post/media updates by both
_idandcreatorId.