Product · Backend · Role Audit

What is Vybe today?

A factual audit of the current working application — not what the website claims, not what we want it to become. Every feature below was traced from UI action through to database write, permissions and admin visibility.

Executive summary

Vybe today is a polished, branded frontend with strong identity, a real auth layer, a genuinely functional events + RSVP feature, real persisted 1:1 messaging, a solid profile / account-management / account-deletion flow, and now a campus model — Campus + Announcement entities, campus_id on User/Profile/Post/Event/Community/Announcement, and Row-Level Security scoping Post/Event/Community/Announcement/Campus to a student's campus. But the core social loop — posting, liking, commenting, saving, notifications, discovery, communities — is still almost entirely mock data and optimistic local state with no database writes. There are still no admin roles beyond admin/user, no moderation, no analytics, no reporting/blocking, no search backend, and personal entities (Profile, Comment, Like, RSVP, Conversation, Message, Notification) still have no Row-Level Security — they remain readable and writable by any authenticated user.
02 · Reality check

What genuinely works

These features are backed by real database reads and writes, traced end to end.

FeatureStatusEvidence
Authentication (signup, signin, forgot, OTP, reset)COMPLETEAuthOverlay + views use the Base44 auth SDK; consents captured on User entity.
Account management (profile, comms, privacy, logout)COMPLETEAccount.jsx persists via auth.updateMe.
Account deletionCOMPLETEdeleteAccount backend function anonymises Profile + User, unsubscribes, deletes auth account.
Profile view / editCOMPLETEProfile entity by email; avatar/cover uploaded via UploadPublicFile.
Events — browse / createCOMPLETEEvent.list + realtime subscribe; CreateEventForm writes records.
Events — RSVPPARTIALRSVP records created/updated — but Event.rsvp_count is never incremented, so "going" reads 0.
Messaging — 1:1PARTIALMessages persist via realtime — but no way to start a conversation; unread_count broken; no RLS.
Campus model + data scopingCOMPLETECampus + Announcement entities; campus_id on User/Profile/Post/Event/Community/Announcement; RLS scopes reads to the student campus (admin sees all).
03 · UI exists — backend missing

Frontend-only / mock functionality

These appear functional to a user but do not touch the database.

AreaWhat the UI showsWhat actually happens
Home feedScrollable posts, avatars, imagesHardcoded mockPosts array. No Post.list() call.
Create postFull composer + "Share Your Vibe"setTimeout then navigate. // TODO: Post to backend. No Post.create(). Images discarded.
Like / reactHeart toggle + countLocal useState only. No Like.create(), no Post.likes_count update.
CommentComment sheet + sendOnly increments local count. No Comment.create(). List always empty.
Save / bookmarkBookmark toggleLocal state only. No SavedItem entity.
ShareShare icon everywhereNo-op — no handler attached.
Story reelStory ringsHardcoded array. Tapping does nothing. No entity.
Explore / DiscoverTrending grid + searchHardcoded trendingPosts. Search filters local array only.
NotificationsFull list + "mark all as read"Hardcoded array. "Read" is local state. No Notification entity read/write.
Profile post grid6-image gridHardcoded Unsplash fallbacks — not the user’s own posts.
Vybe Score / badgesScore, level, badge cardsFields exist but nothing computes them — stay at 0/1/[].
Followers / followingStatsNo follow mechanism — stay 0.
New conversation"+" button in MessagesNo handler — cannot start a chat.
04 · Backend

Existing backend architecture

Entities present, their read/write status, and what does not exist yet. Record counts are live — refreshed by the button above.

Entities (database models)

EntityUI reads it?UI writes it?RLS?Records (live)
UserYes (Account)Yes (auth, comms, delete)Noneblocked
ProfileYes (Profile)Yes (EditProfileSheet)Noneblocked
PostMockStubbedCampus-scoped ✓blocked
CommentMockStubbedNoneblocked
LikeMockStubbedNoneblocked
EventYes (Events)Yes (Create form)Campus-scoped ✓blocked
RSVPYes (EventCard)Yes (create/update)Noneblocked
CommunityNo pageNo create/join UICampus-scoped ✓blocked
ConversationYes (Messages)No start flowNoneblocked
MessageYes (Messages)Yes (send)Noneblocked
NotificationMock UINothing writesNoneblocked
CampusYes (signup picker)Admin onlyAdmin-gated ✓blocked
AnnouncementNo page yetAdmin onlyCampus-scoped ✓blocked

Entities that still do NOT exist (required)

CommunityMember, Follow/Connection, Block, Report, ModerationAction, SavedItem, Interest, AuditLog, and any Role/Permission model beyond the User.role enum. Campus and Announcement now exist (with RLS).

Backend functions

deleteAccount — the only backend function. Real, service-role, user-scoped.

No notification dispatch, no RSVP counter, no moderation, no analytics aggregation, no campus scoping, no search function.

Workflows

None. No scheduled jobs, no event triggers, no reminder flows, no notification workflows.

Relationships

Implied by ID/email string fields (event_id, post_id, conversation_id, community_id, user_email, participant_emails[]) but not enforced — no foreign-key constraints, no server-side validation that a referenced record exists or belongs to the acting user.

05 · Student

Student experience audit

What exists vs. missing across the full student journey.

CapabilityStatus
Create / manage profile (name, bio, avatar, cover)COMPLETE
Delete accountCOMPLETE
Manage privacy / consents / communication prefsCOMPLETE
Browse / search events + view detail + RSVPCOMPLETE
See who is attendingCOMPLETE
Create eventsCOMPLETE
Send / receive 1:1 messagesPARTIAL
View feed of postsUI ONLY
Create posts / upload mediaUI ONLY
Like / comment / save / shareUI ONLY
Receive notifications (in-app)UI ONLY
Search people / events / communities / postsUI ONLY
Edit / cancel own eventsMISSING
Communities (browse / join / create / post inside)MISSING
View other students' profilesMISSING
Follow / connectMISSING
Block / report users / contentMISSING
Add interests / course / faculty / yearMISSING
Profile visibility controlMISSING
Group conversationsMISSING
Event reminders / change noticesMISSING
Email / push / SMS notificationsMISSING
Campus-specific content scopingMISSING
06 · Campus admin

Campus / institution admin audit

An admin role representing a university, residence, faculty or organisation — managing only their own campus.

Does not exist

There is no campus-admin role, no campus entity to administer, and no campus-admin pages. User.role only allows admin / user. Everything below is missing:
  • Campus dashboard (active users, engagement, communities, events, reports)
  • Official event creation / management with attendance visibility
  • Verified campus announcements (official / urgent / informational)
  • Official community creation + moderator management
  • Official content publishing + campus-scoped moderation
  • Campus-scoped user views (verify, suspend from campus, review reports)
  • Campus analytics (aggregated, privacy-safe)
  • Campus profile management (name, logo, banner, description, contact, links, rules)
07 · Platform admin

Platform admin audit

A separate system-level admin managing the platform itself.

Effectively does not exist

The Base44 admin role grants platform-level user-management rights, but there is no admin UI, no admin pages, and no admin tooling in the app. Everything below is missing:
  • Campus management (create / edit / activate / assign admins / view usage)
  • User management (search, status, suspend/ban, deletion requests, role assignment, verification)
  • Content moderation queue (reported posts/comments/users/communities/events)
  • Community management + abuse handling + disabling
  • Event review + verified/official status + removal of unsafe events
  • Platform analytics (users, active users, campus growth, engagement, reports, moderation workload)
  • System settings (categories, notification defaults, moderation thresholds, legal versions, feature flags, email templates, branding)

The deleteAccount function is the only server-side privileged logic, and it is user-initiated only.

08 · RBAC

Role & permission audit

How roles are stored, how permissions are checked, and where access is enforced.

How roles are stored. User.role — a string enum of ["admin", "user"] only. No campus_admin, moderator or organiser role.

How permissions are checked. RequireAuth wraps protected routes and checks authentication only — not role. Every protected route is reachable by any logged-in user.

Server-side enforcement. Partial. RLS is now enforced on Post, Event, Community, Announcement and Campus — reads are campus-scoped and writes are owner/admin-gated. However User, Profile, Comment, Like, RSVP, Conversation, Message and Notification still have no rls key, so those records remain readable and writable by any authenticated user via the SDK client.

Can a user reach another role's pages by URL? There are no role-gated pages — but more critically, the data is not protected. The gap is not "hidden nav"; it is no access control at all on the data layer.

Verdict

RLS + campus scoping now protect the core content entities, but RBAC is still partial — roles are only admin/user, and personal entities (Profile, Messages, Notifications, RSVPs, Comments, Likes) remain unprotected. This is still a critical gap.
09 · Safety

Moderation & safety audit

Because this is a social platform, moderation is not optional.

CapabilityStatus
Report a postMISSING
Report a commentMISSING
Report a userMISSING
Report an event / communityMISSING
Block a userMISSING
Moderation queueMISSING
Admin review of reportsMISSING
Remove contentMISSING
Suspend / ban accountMISSING
Appeal / review processMISSING
Moderation notesMISSING
Audit logMISSING
Community guidelines enforcementMISSING

Moderation and safety are entirely absent

Combined with the lack of RLS, this is a serious launch blocker — both for safety and for POPIA compliance.
10 · Privacy

Privacy & account management audit

The strongest area of the app — with one critical caveat.

CapabilityStatus
View Privacy Policy / TermsCOMPLETE
Accept Privacy Policy & Terms (consent + version + date)COMPLETE
Update communication preferencesCOMPLETE
Opt in/out of marketing (separated from newsletter)COMPLETE
Newsletter vs. essential comms separationCOMPLETE
Delete accountCOMPLETE
Log outCOMPLETE
Reset passwordCOMPLETE
Consent records stored (on User)COMPLETE
Manage profile visibilityMISSING
Download / export account dataMISSING
Block usersMISSING
Manage notificationsMISSING

Critical caveat

The content layer is now scoped, but personal entities (no RLS) still undermine the privacy promise — a user's Profile and Messages remain readable by any other authenticated user.
11 · Marketing

Marketing claim verification

Each claim measured against the working application.

#ClaimVerdictWhy
1"A private social network for your campus."PARTIALLY SUPPORTEDCampus entity + campus_id on User/Profile/Post/Event/Community/Announcement + RLS now scope content to a student campus. Profiles, messages, notifications and roles are still open.
2"Discover what's happening."PARTIALLY SUPPORTEDEvents discovery is real. Post discovery is mock. No live pulse.
3"Find your people."NOT YET SUPPORTEDNo communities page, no people discovery, no follow/connect, no interest matching.
4"Join campus life."PARTIALLY SUPPORTEDEvent RSVP is real. Community join does not exist.
5"Share campus life."NOT YET SUPPORTEDPost creation UI exists but does not persist. Nothing is shared.
6"Message other students."PARTIALLY SUPPORTEDReal 1:1 messaging, but cannot start a conversation, unread is broken, no access control.
7"Know what's happening right now."NOT YET SUPPORTEDNo live pulse, no today/tonight view, no trending backed by data.
12 · Pages

Pages that exist vs. pages required

What routes exist now, and what must exist to complete the product.

Pages that exist now

RoutePurposeAccessWorks?
/landingMarketing pagePublicYes
/privacy, /termsLegalPublicYes
/reset-passwordPassword resetPublicYes
/brandBrand kitPublicYes
/Home feedAuthMock data
/exploreDiscover / trendingAuthMock data
/createCreate postAuthDoes not save
/eventsEvent hubAuthYes
/messagesDMsAuthPartial
/notificationsNotificationsAuthMock data
/profileOwn profileAuthYes
/accountSettingsAuthYes

Pages required but missing

Student

Campus Pulse / Right Now · Communities list & detail · Event detail page · Unified search · Other users' profiles · Notification preferences · Saved posts

Campus admin (entire surface)

Campus dashboard · Campus analytics · Official events · Community management · Announcements · Moderation queue · Campus settings

Platform admin (entire surface)

Global dashboard · Campus management · User management · Moderation queue · Reports · Platform analytics · System settings · Audit log
13 · Backend

Missing database / backend functionality

Only what is actually required to support the intended product.

Required new entities

✓ Campus and Announcement now exist (with campus_id + RLS).

  • CommunityMember — community_id, user_email, role (member/moderator), joined_at
  • Follow — follower_email, following_email
  • Block — blocker_email, blocked_email
  • Report — reporter_email, target_type, target_id, reason, status
  • ModerationAction — admin_email, target_type, target_id, action, reason
  • SavedItem — user_email, post_id
  • AuditLog — actor_email, action, target, metadata

Required field additions

  • User: campus_id + roles (campus_admin, platform_admin)
  • Post: campus_id, author_email, status
  • Event: campus_id, official/verified flag, edit/cancel support
  • Community: campus_id, owner, membership roster
  • Profile: campus_id, interests, course, faculty, year, visibility

Required logic / functions / workflows

  • Post create + image upload; feed read (campus-scoped); like, comment, save with counter maintenance
  • Notification dispatch on like/comment/RSVP/message/follow/event
  • Conversation start + correct unread_count + mark-as-read + RLS
  • RSVP create/update/delete with Event.rsvp_count maintenance
  • Campus-scoped queries across events/communities/announcements
  • Backend search across people/events/communities/posts
  • Moderation actions (suspend/ban/remove) — service-role, admin-gated
  • Analytics aggregation (privacy-safe); Event reminder workflow (scheduled)
  • RLS on every entity — ownership + campus-scoping rules
14 · Gap analysis

Gap matrix

Feature-by-role. ✅ complete · ◐ partial · ▢ UI only · ◓ backend only · ✗ missing. Each row has a ready-to-use fix prompt.

FeatureStudent UIStudent BECampus UICampus BEPlatform UIPlatform BEStatusWhat's missing / fix prompt
Auth / login✅✅✗✗✗✗◐
Admin roles + role gates
Profile create / edit✅✅✗✗✗✗◐
Campus, interests, visibility, RLS
View other profiles✗✗✗✗✗✗✗
Discovery + routing + RLS
Feed (posts)▢✗✗✗✗✗▢ UI
Post read/write wiring
Create post▢✗✗✗✗✗▢ UI
Post.create + upload
Like / comment / save▢✗✗✗✗✗▢ UI
Like/Comment/Saved entities + writes
Notifications (in-app)▢◓✗✗✗✗▢ UI
Writer logic + UI binding
Notifications (email/push/SMS)✗✗✗✗✗✗✗
All channels + workflows
Communities (browse/join/create)✗◓✗✗✗✗◓
CommunityMember + pages + join
Events (browse/create/RSVP)✅◐✗✗✗✗◐
rsvp_count, edit/cancel, campus scope
Event detail / attendees✅✅✗✗✗✗◐
Standalone page, reminders
Messaging (1:1)◐◐✗✗✗✗◐
Start conv, unread, RLS
Group messaging✗✗✗✗✗✗✗
Group conversations
Search / discovery▢✗✗✗✗✗▢ UI
Backend search
Campus Pulse / Right Now✗✗✗✗✗✗✗
Entire feature
Campus scoping / data separation✗✅✗✗✗✗◓
RLS on personal entities + wire posts to campus
Follow / connect✗✗✗✗✗✗✗
Follow entity + UI
Block / report✗✗✗✗✗✗✗
Block + Report entities + UI
Moderation queue✗✗✗✗✗✗✗
All moderation
Account delete✅✅✗✗✗✗◐
Admin-side handling
Privacy / consent✅✅✗✗✗✗◐
Consent record, legal versions
Campus admin dashboard✗✗✗✗✗✗✗
Entire surface
Campus announcements✗✅✗✅✗✅◓
Announcement UI + admin create form
Platform admin dashboard✗✗✗✗✗✗✗
Entire surface
Campus management✗✗✗✗✗✗✗
Campus CRUD + assignment
User management (suspend/ban/roles)✗✗✗✗✗✗✗
Admin UI + service functions
Analytics✗✗✗✗✗✗✗
Aggregation + dashboards
System settings / feature flags✗✗✗✗✗✗✗
Settings entity + UI
Audit log✗✗✗✗✗✗✗
AuditLog entity
15 · Build priority

Recommended build priority

Each line has a live Check button that probes whether the issue is actually resolved (entity readability, user campus link) and auto-ticks the item when it passes. Items that can't be probed at runtime show Manual. Tick an item once you've applied its fix; progress is saved on this device. Items pre-ticked below were verified against the entity files on disk — not a live probe.

Phase 1

Must have before public launch

3/9 done
  1. 1.Row-Level Security on every entity — ownership + campus-scoping rules. The foundation.on file
  2. 2.Campus model + campus→user link. campus_id on User, Profile, Post, Event, Community, Announcement.on file
  3. 3.Roles beyond admin/user — campus_admin, platform_admin — with server-side enforcement + role-gated routes.on file
  4. 4.Wire the core social loop to the database — post create (real upload), feed read (campus-scoped), like, comment, save with counter maintenance.
  5. 5.Notification writer logic + bind Notifications UI to the entity.
  6. 6.Fix events — maintain Event.rsvp_count; add edit/cancel; campus-scope listing.
  7. 7.Fix messaging — start conversation flow; correct unread_count; RLS so only participants see a conversation.
  8. 8.Reporting + blocking — Report/Block entities + UI + a minimal moderation queue.
  9. 9.Search backend — real campus-scoped query across people/events/communities/posts.
Phase 2

Required for a strong product

0/7 done
  1. 1.Communities surface — list/detail, create/join/leave, CommunityMember, post-inside, moderators.
  2. 2.Campus Admin surface — dashboard, official events, announcements, campus-scoped moderation, campus profile.
  3. 3.Platform Admin surface — campus management, user management, global moderation, platform analytics.
  4. 4.People discovery + profiles — view others, follow/connect, visibility controls, interests/course/faculty/year.
  5. 5.Event reminders + change notices — scheduled workflow → email/push.
  6. 6.Vybe Score / level / badges engine — real computation from activity.
  7. 7.Campus Pulse / Right Now — live today/tonight/trending backed by real data.
Phase 3

Advanced / growth features

0/7 done
  1. 1.Group conversations.
  2. 2.Push / SMS notifications (requires native mobile build).
  3. 3.Notification digest workflows (scheduled, opt-in).
  4. 4.Data export (account data download for POPIA/GDPR).
  5. 5.Audit log + moderation notes + appeal flow.
  6. 6.System settings / feature flags / email templates / legal version management.
  7. 7.Advanced analytics (campus growth, engagement, moderation workload).

What Vybe is capable of becoming

The architecture can support the intended product — the entities and SDK are the right starting point. But Phase 1 (RLS, campus model, roles, wiring the social loop, notifications, moderation) is required before this can truthfully be called a real social platform.

Vybe Campus · Product & Backend Audit · 2026