🧩 Summary
Course Hub User in the CRM uses the Course builder User table, which is an unnecessary layer of indirection (it passes straight through the the Applications User with no filtering).
In order to unwind this, we would need to:
- Create a new sync directly from the Applications base
- Check all of these things in the CRM base, and repoint them to the new table:
- Automations
- Interfaces
- Cross-links to other tables
I don't think this is worth doing at the moment, but if we ever do a big refactor of the CRM it would be preferable to end up without this indirection.
✅ Definition of done
The User table synced to the CRM comes directly from the Applications base
📌 Notes / Designs
No response
🧩 Summary
Course Hub User in the CRM uses the Course builder User table, which is an unnecessary layer of indirection (it passes straight through the the Applications User with no filtering).
In order to unwind this, we would need to:
I don't think this is worth doing at the moment, but if we ever do a big refactor of the CRM it would be preferable to end up without this indirection.
✅ Definition of done
The User table synced to the CRM comes directly from the Applications base
📌 Notes / Designs
No response