SalesWiki uses role-based access to serve different facts from one shared knowledge base

Developer project SalesWiki explores how a single shared sales knowledge base can serve different roles — such as account executives and marketers — without exposing every record to every user. The system separates broad account knowledge, sensitive sales notes, contact references, and legal material into distinct storage areas, with a card's directory location determining its access class. Role and account policies are enforced server-side, meaning a salesperson preparing for a call and a marketer selecting a campaign signal each receive only the facts relevant to their decision. Contact details are kept out of the shared vault entirely, replaced with opaque references resolved by an approved external store to isolate access and deletion concerns. The project acknowledges gaps, including the need for a real identity provider in production deployments, and treats information requests and change requests as separate, distinct paths.