Bubble Role & Privacy Fix -- 2
Budget: €250 – €750 EUR
I’m building a custom CRM in Bubble with:
• Companies
• Clients / Contacts
• Interactions (meetings, calls, etc.)
• Projects
All of these entities generate follow-ups that drive a dashboard view.
The dashboard shows:
• Follow-ups due
• Counts of companies, interactions, projects
All grouped by user, so managers can track team activity.
The app is live and mostly functional, but I’m running into role-based update and privacy issues that need a senior Bubble developer to audit and fix properly.
⸻
User Roles & Intended Logic
There are three role levels:
1. Representative (lowest)
2. Delegate
3. Manager (highest)
Intended behavior:
• Representatives can see and edit only their own data
• Delegates can:
• See their own data
• See data created by Representatives below them
• Edit their own data and data from Representatives below them
• Managers can:
• See and edit all data
• Track follow-ups, interactions, and projects by user
Ownership is set at record creation.
Higher-level roles must be able to update data introduced by lower-level roles.
⸻
The Problem
Some updates work correctly for Managers, but fail silently for Delegates, even when:
• The correct record is selected
• Workflow conditions evaluate to true
• Permission flags are set
• UI logic is correct
Additionally:
• Users can view records they are allowed to see
• But cannot always update them, even when they should
This strongly suggests issues at the data layer, not the UI.
⸻
What Needs to Be Audited
I need a quick but thorough audit, followed by direct fixes in the Bubble editor, covering:
1. Privacy Rules
• Rule priority / ordering
• Conflicts between:
• Role-based rules
• Owner-based rules
• Permission flags
• Field-level write permissions (especially follow-up fields)
2. Update Workflows
• Consistency of “Thing to change”
• Overlapping or conflicting update steps
• Follow-up date logic (nextfollowupat) possibly being overwritten or blocked
3. Data Flow & Visibility
• Why Delegates can create but not update certain records
• Ensuring higher roles can update data from lower roles
• Making sure follow-ups and KPIs show correctly by user for Managers
⸻
Deliverables
• Identify and explain any misconfigured privacy rules or workflows
• Fix them directly in the Bubble editor
• Ensure:
• Delegates can update records they are meant to update
• Follow-ups update correctly
• Dashboard reflects accurate data by user
• Run a test with at least two different roles to confirm correct behavior
⸻
Requirements
• Strong experience with Bubble privacy rules
• Proven experience debugging role-based permissions
• Comfortable working on live apps
• Not suitable for beginners
⸻
Scope & Timing
• Small but high-impact task
• Should take 1–3 hours for an experienced Bubble developer
• I’m ready to grant editor access immediately
⸻
How to Apply
Please include:
1. Your experience with Bubble (years / number of apps)
2. One example of fixing a complex permission or privacy issue
3. Confirmation that you can start immediately
• Companies
• Clients / Contacts
• Interactions (meetings, calls, etc.)
• Projects
All of these entities generate follow-ups that drive a dashboard view.
The dashboard shows:
• Follow-ups due
• Counts of companies, interactions, projects
All grouped by user, so managers can track team activity.
The app is live and mostly functional, but I’m running into role-based update and privacy issues that need a senior Bubble developer to audit and fix properly.
⸻
User Roles & Intended Logic
There are three role levels:
1. Representative (lowest)
2. Delegate
3. Manager (highest)
Intended behavior:
• Representatives can see and edit only their own data
• Delegates can:
• See their own data
• See data created by Representatives below them
• Edit their own data and data from Representatives below them
• Managers can:
• See and edit all data
• Track follow-ups, interactions, and projects by user
Ownership is set at record creation.
Higher-level roles must be able to update data introduced by lower-level roles.
⸻
The Problem
Some updates work correctly for Managers, but fail silently for Delegates, even when:
• The correct record is selected
• Workflow conditions evaluate to true
• Permission flags are set
• UI logic is correct
Additionally:
• Users can view records they are allowed to see
• But cannot always update them, even when they should
This strongly suggests issues at the data layer, not the UI.
⸻
What Needs to Be Audited
I need a quick but thorough audit, followed by direct fixes in the Bubble editor, covering:
1. Privacy Rules
• Rule priority / ordering
• Conflicts between:
• Role-based rules
• Owner-based rules
• Permission flags
• Field-level write permissions (especially follow-up fields)
2. Update Workflows
• Consistency of “Thing to change”
• Overlapping or conflicting update steps
• Follow-up date logic (nextfollowupat) possibly being overwritten or blocked
3. Data Flow & Visibility
• Why Delegates can create but not update certain records
• Ensuring higher roles can update data from lower roles
• Making sure follow-ups and KPIs show correctly by user for Managers
⸻
Deliverables
• Identify and explain any misconfigured privacy rules or workflows
• Fix them directly in the Bubble editor
• Ensure:
• Delegates can update records they are meant to update
• Follow-ups update correctly
• Dashboard reflects accurate data by user
• Run a test with at least two different roles to confirm correct behavior
⸻
Requirements
• Strong experience with Bubble privacy rules
• Proven experience debugging role-based permissions
• Comfortable working on live apps
• Not suitable for beginners
⸻
Scope & Timing
• Small but high-impact task
• Should take 1–3 hours for an experienced Bubble developer
• I’m ready to grant editor access immediately
⸻
How to Apply
Please include:
1. Your experience with Bubble (years / number of apps)
2. One example of fixing a complex permission or privacy issue
3. Confirmation that you can start immediately