验证:适用于内部竞争组织的客户关系管理系统(CRM)

1作者: Yaswanth216 天前原帖
大家好,我在这里写信是为了对我正在构建的客户关系管理系统(CRM)进行验证。 <p>字段级安全性 我正在开发一个CRM,增加了角色管理功能,允许在记录上实现字段级可见性,超越默认的查看权限。以往在传统CRM中完全隐藏的记录,现在可以根据角色以最小字段的形式显示。常规的字段级安全性仍然存在,但传统字段级安全性的问题在于,即使是您拥有的记录也会受到字段限制。 <p>个人和组织CRM 用户可以拥有一个个人CRM,除非他们明确发布记录,否则这些记录对组织不可见。这不是一个传统的销售CRM,它适用于存在内部竞争的组织。 <p>冲突检测 如果用户创建了一个私有记录,而组织中已经存在相同的记录,则双方都会收到匿名或公开的警报。用户可以提供理由并请求合作,如果请求被接受,将创建一个合作空间。 <p>重复记录和黄金记录 鼓励创建重复记录。一旦私有记录被发布,而组织记录已经存在,就会创建一个黄金记录,其中个别记录根据用户的角色进行聚类和上下文显示。 <p>我对那些在复杂的、政治性组织(如大学、合伙企业、政府、风险投资等)中销售或运营的人士的看法非常感兴趣。 <p>我独立构建这个系统,但也乐于与喜欢与理想客户群(ICP)沟通并在实际中测试问题陈述的人合作。 <p>很高兴分享更多细节,或向任何处理过类似问题的人学习。 <p>— Yaswanth
查看原文
Hi all, I’m writing here to get validation on a CRM I’m building.<p>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.<p>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.<p>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.<p>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.<p>I’m interested in perspectives from people who’ve sold into or operated within complex, political orgs (universities, partnerships, government, VC, etc.).<p>I’m building this independently, but open to collaborating with someone who enjoys talking to ICPs and pressure-testing problem statements in the field.<p>Happy to share more details or learn from anyone who has dealt with similar issues.<p>— Yaswanth