Share the useful context at the right level.
A private working note, a project decision and a company handbook serve different audiences. Memrain's sources let an operator organize those boundaries and give each client the combination it needs.
Illustrative setup
Can my assistant use my notes, our project runbook and the company handbook together?
Give the connection a personal write source and a read set containing the permitted personal, project and company sources. Retrieval follows that explicit grant.
Illustrative scenario, not a live product result.Use sources as the sharing unit.
A source owns its content, and a credential carries one write source plus a set of readable sources. The operator can create separate places for personal notes, shared project knowledge and company reference material. Those names describe your organization; they do not create automatic role inheritance. Each connection's read set states which of those sources it may use.
Read broadly where the work requires it.
A person's assistant can retrieve across an allowed combination of sources while writing new notes to its assigned source. Shared reading does not automatically grant shared editing. When a personal observation becomes a team decision, an authorized workflow can save the reviewed material in the team's source with a reference to its origin. This makes sharing a deliberate publishing step.
Verify the boundaries as the team grows.
Check each connection with whoami and test representative pages after changing its read set. Source scoping is enforced in the application and documented as pilot-grade; the operator panel has broader access. Company use needs the documented fail-closed configuration and a review of organizational requirements. Independent deployments provide a separate option when groups need stronger operational separation.
Keep the context. Move the work forward.
Connect your knowledge to the AI you already use. Find your starting point and make the next conversation count.