Secured Online Community Space Development
Budget: $250 – $750 SGD
I’m ready to launch a private, role-based community portal and need an experienced developer to build the first four modules, all sitting behind a unified access-control layer. I have no firm preference on stack, so feel free to use Snowflake, AWS, or a mix—provided the solution is secure, scalable, and keeps user-access management (UAM) clean and auditable.
Core modules for this initial phase
• Discussion Chat – must include user tagging, file sharing, and threaded replies.
• Collaborative Document Library – real-time editing, robust version control, and inline commenting are required.
• Event Calendar – visual monthly/weekly views with RSVP tracking.
• Event Listing – searchable, filterable directory of upcoming and past activities.
Every module must honour the same roles, rights, and approval flows so administrators can grant or revoke access at group, feature, and document levels without manual workarounds.
Acceptance criteria
1. Single sign-on and granular RBAC applied consistently across all four modules.
2. Real-time performance test demonstrating sub-second chat delivery for ≥100 concurrent users.
3. Audit log proving document edits, version history, and permission changes.
4. Clean, responsive UI that can be re-skinned easily.
Once these foundations are in place, I’m open to adding milestones for extras such as analytics dashboards, mobile push notifications, or additional collaborative tools. Let me know which stack you’d choose, your estimated timeline for each module, and any questions you need answered before kicking off.
Core modules for this initial phase
• Discussion Chat – must include user tagging, file sharing, and threaded replies.
• Collaborative Document Library – real-time editing, robust version control, and inline commenting are required.
• Event Calendar – visual monthly/weekly views with RSVP tracking.
• Event Listing – searchable, filterable directory of upcoming and past activities.
Every module must honour the same roles, rights, and approval flows so administrators can grant or revoke access at group, feature, and document levels without manual workarounds.
Acceptance criteria
1. Single sign-on and granular RBAC applied consistently across all four modules.
2. Real-time performance test demonstrating sub-second chat delivery for ≥100 concurrent users.
3. Audit log proving document edits, version history, and permission changes.
4. Clean, responsive UI that can be re-skinned easily.
Once these foundations are in place, I’m open to adding milestones for extras such as analytics dashboards, mobile push notifications, or additional collaborative tools. Let me know which stack you’d choose, your estimated timeline for each module, and any questions you need answered before kicking off.