The more I watch Rick's sessions from 2017, 2018 and 2019, more confused I get - so I guess I'd write it down.
There are 3 core steps (some have more, I want to stick to 3) to create a decent model that works well:
- Understand the usecase + create ERD(list entities and relations)
- Identify the access patterns - R/W workloads, query dimensions and aggregations
- Data modeling - avoid relational patterns, use 1 table(if there aren't any "documents", 1 should be fine)
- R.R.R = Review > Repeat > Review (go on till it makes sense)
Entity 4 = Permission (of a user, on a connection)
As explained above about connections, the info pertaining to the "creator" of a connection will always point to the user who created any given connection), however the access - or "permission" - on a connection (of a user) would define which connections to show for a user, and this info in itself would be a different "Entity" in the system.