Field Level Security I’m working on a CRM where I’ve added a role management capability that allows field-level visibility on records beyond default view access. Records that are usually completely hidden in legacy CRMs can now be displayed with minimal fields, configurable per role. Regular FLS still exists, but the issue with traditional FLS is that it restricts fields even for records you own.
Personal and Org CRM Users can have a personal CRM where their records are not visible to the organization unless they explicitly publish them. This is not a traditional sales CRM—it’s relevant for orgs where internal competition exists.
Collision Detection If a user creates a private record and a record already exists in the org, both parties receive an anonymous or open alert. Users can provide a reason and request collaboration, and a collaboration room is created if the request is accepted.
Duplicate Records and Golden Records Duplicate records are encouraged. Once a private record is published and an org record already exists, a golden record is created where individual records are clustered and displayed contextually based on a user’s role.
I’m interested in perspectives from people who’ve sold into or operated within complex, political orgs (universities, partnerships, government, VC, etc.).
I’m building this independently, but open to collaborating with someone who enjoys talking to ICPs and pressure-testing problem statements in the field.
Happy to share more details or learn from anyone who has dealt with similar issues.
— Yaswanth