mosaic/stack
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Row-Level Security (RLS) policies #10

New Issue
Closed
opened 2026-01-28 19:03:38 +00:00 by jason.woltje · 0 comments
jason.woltje commented 2026-01-28 19:03:38 +00:00
Owner
Copy Link

Implement PostgreSQL RLS for workspace isolation.

Policies needed:

  • tasks: Users can only see/modify tasks in their workspaces
  • events: Users can only see/modify events in their workspaces
  • projects: Users can only see/modify projects in their workspaces
  • activity_log: Users can only see activity in their workspaces

Implementation:

  • Enable RLS on all workspace-scoped tables
  • Create policies based on workspace_id
  • Set current_user context in session
  • Test isolation between workspaces

Requirements:

  • Zero data leakage between workspaces
  • Performance acceptable (index workspace_id)
  • Works with Prisma
Implement PostgreSQL RLS for workspace isolation. **Policies needed:** - tasks: Users can only see/modify tasks in their workspaces - events: Users can only see/modify events in their workspaces - projects: Users can only see/modify projects in their workspaces - activity_log: Users can only see activity in their workspaces **Implementation:** - Enable RLS on all workspace-scoped tables - Create policies based on workspace_id - Set current_user context in session - Test isolation between workspaces **Requirements:** - Zero data leakage between workspaces - Performance acceptable (index workspace_id) - Works with Prisma
jason.woltje added this to the M2-MultiTenant (0.0.2) milestone 2026-01-28 19:03:38 +00:00
jason.woltje added the databasesecurityp0 labels 2026-01-28 19:03:38 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
ai
AI/LLM integration
 api
Backend/API work
 api
auth
Authentication
 database
database
Database/schema work
 devops
Docker/deployment
 docs
Documentation
 frontend
graph
knowledge-module
migration
Data migration
 orchestrator
Orchestrator service (apps/orchestrator/)
 p0
Critical priority
 p1
High priority
 p2
Medium priority
 p3
Low priority
 performance
Performance work
 phase-1
phase-2
phase-3
phase-4
phase-5
plugin
MoltBot plugin work
 search
security
Security-related
 setup
Initial setup
 testing
Testing/QA
 web
Frontend work
No Label database p0 security
Milestone
No items
No Milestone M2-MultiTenant (0.0.2)
Projects
Clear projects
No project
Assignees
Clear assignees
jason.woltje
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: mosaic/stack#10
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?