A company knowledge base every assistant can quote
Policies and processes live in one private repository. Each person’s assistant reads the parts they have been given, and nothing else.
Who it’s for: Operations, HR and team leads who own the rules, and everyone who has to follow them.
One place for the rules
Most companies keep their policies in a wiki, a shared drive and a few people’s heads. When someone asks an assistant about leave, expenses or security rules, it guesses, or it quotes a copy that went stale months ago.
Put the policies in Markdown in a Git repository and the repository becomes the source. Changes go through commits and reviews like any other change, so there is always a history of who changed a rule and when.
Access per person, per repository
Notedigit grants access per user, per repository, and you can open a repository to the whole team when everyone should read it. Keep company-wide policies in one repository, open to the whole team, and sensitive ones, such as HR procedures or finance approvals, in another, and assign each to the people who should read it.
When someone connects Claude or ChatGPT, they sign in with their Notedigit account over OAuth, and their assistant sees only the repositories assigned to them.
Answers that match the current version
Notedigit clones a repository when an assistant starts reading and deletes the clone after 15 minutes without activity. A new session reads the branch as it is on your git host, so an updated policy is what the next answer quotes.
Every call is logged with the client, user, tool and note, so you can see which policies are actually being read.
How to structure the repository
- Give each policy its own file with a clear title, one topic per file. Assistants find and quote a short, focused note far more reliably than a section of a forty-page handbook.
- Add a README that lists what lives where and who owns each area. The assistant reads it the way a new employee would, and it tells people where to send corrections.
- Put the date a policy took effect and its owner at the top of the file. When someone asks whether a rule is current, the answer is in the note itself.
Setting it up
-
Step 1: Create a private repository on your git host and move the policies into it as Markdown. Most wikis and document tools export to Markdown directly.
-
Step 2: Connect the repository in Notedigit with the read-only deploy key it generates, and assign the people who should read it.
-
Step 3: Each person adds the repository’s MCP endpoint to their assistant as a custom connector and signs in with their Notedigit account.