My Bubble-built web app is almost ready, but the user account system still needs a proper role architecture. I have three distinct user types—College Coach, Athlete and Admin—and each must see and edit only what their role allows: • College Coaches: read-only access to player contact details and scouting reports, with their page views automatically logged for later display. • Athletes: ability to update only their own contact information. • Admins: full control to edit scouting reports, replace YouTube video URLs and adjust any showcase data. The data types and pages already exist (Showcase Page and Player Page); what I lack is the underlying Bubble privacy rules, conditional elements, and workflow logic that enforce those permissions cleanly across the app. I also need a simple dashboard or field structure that lets me flag which coaches have opened a specific showcase link so I can publish that list afterward. Key deliverables – Define/implement the three roles in Bubble’s database and privacy settings. – Build or refine the workflows that gate page elements and actions according to role. – Ensure view-tracking for coaches ties back to the correct showcase record. – Hand over clear notes so I can extend the system myself later. The rest of the interface is built, so this is a focused task on permissions and tracking. I’d like it wrapped up within the next month and I’m happy to give you immediate access to the Bubble editor plus sample data so you can dive straight in.