Use case:
Inviting freelancers to write a piece. Then we want to comment internally about said piece before giving the feedback to the client.
Current work around: Automatically create a “thread” entity (that the freelancers has no permission to) linked to the freelancers work. Then chat in there. But that’s quite hidden and is bad UX.
Ideally I just create a comment field in the work itself and don’t give the freelancer access to it.
Use case 2. Client portal has a status field. I don’t want the clients who are shared in the portal to see this status. Workaround: new database and linked with one to many. Downside: worse UX (bc of the arrow to open), and results in a lot of databases.
If you expose the single and multi select. It essentially gives field permissions (for those types) without much extra dev time.
Lmk if this makes sense. Thanks!