Access Control
Hi, new to twenty, been searching for an answer on this but haven’t seem to have found one yet. I’m trying to figure out if there’s a way to have leads, opportunities, contacts, etc separate for each workplace user? Will be using Twenty for a realty company and each Realtor should only see data relevant to them or their team. Thanks
7 Replies
hi there. we work with realty customers as well so i understand where that requirement comes from 😉
my understanding is that this permission feature is not live yet: https://github.com/twentyhq/core-team-issues/issues/257
maybe someone from the core team can advice.
GitHub
➡️ Row level permissions · Issue #257 · twentyhq/core-team-is...
About Ability to set conditional access for records Misc Ability to add permission on attachments (see discussion)
Thanks for the response, hopefully the team can push this sooner then later, it’s kind of a deal breaker without this
How do you work around that then if using it for real estate, or do clients just deal with it till this is implemented. Thanks again
first batch of onboarded users were users with full rights: leadership, operations, marketing. they usually have a specific set of requirements, dedicated onboarding etc etc.
for the second batch, you either wait for the feature, or, like in our case, there are more upsides than downsides, so founder decided to just onboard the whole shebang.
also we pull data automatically so we don't need a salesrep to enter anything manually. when they joined, they see their oportunities perfectly updated.
Ok thanks for taking the time to answer me, long term we would like to use the api to also update leads from agent websites, twenty seems like a good fit without having to create everything from scratch. Thanks again
Like @nogeo wrote, that's the one feature which will be done probably in this quarter, one way to work around is creating views with specific filters matching given workspace members based on some criteria but those views can be modified again so you'd have to trust your people that they won't mess with others data
Thanks for clarifying that and for your suggestion on filters as a workaround
No problem!