Map company document access before connecting an AI assistant to the content. The project needs to know who can read which resources, how that authority changes, and where derived copies could bypass it.
Access mapping is a concrete discovery task
An access map describes source systems, resource categories, principals, groups, sharing modes, service identities, and approval ownership. It should capture actual behaviour and known exceptions rather than only intended folder organisation.
For a proposed inventory, record authoritative resource identity, audience, access source, grant and revocation process, sharing-link semantics, connector permissions, and derived storage paths. Mark unknowns and assign accountable owners.
Do not infer policy from an administrator’s ability to read everything. A broad service credential may be necessary for ingestion in some architectures, but the end-user retrieval boundary still needs explicit enforcement.
Map a fictional three-system company
The company has a public product library, an internal document store with project groups, and customer notes scoped by account. The assistant’s access design must preserve those different relationships rather than flatten them into one employee index.
A contractor can read one project folder, while a support employee can read assigned customer notes. Shared guidance has a broader audience. The map should identify both allowed pathways and the resources each person must not receive.
| Inventory element | Discovery evidence |
|---|---|
| Source resource | Stable identity and actual location |
| Principal relationship | Trusted group, role, or resource mapping |
| Shared link | Documented scope and expiry behaviour |
| Connector credential | Account and privilege scope |
| Derived artifact | Index, cache, preview, export, and log controls |
Validate the map with fictional accounts or approved read-only checks. Stakeholder descriptions are useful, but runtime behaviour can reveal inherited grants and exceptions that nobody remembered.
Turn the map into a project boundary
Define the first supported collections and excluded sources explicitly. Unresolved permission questions should constrain scope rather than be deferred until after indexing all content. Convert approved relationships into positive and negative evaluation fixtures.
Access discovery adds time before the visible demo, but it reduces redesign and accidental exposure later. Keep the map current after migrations, staff changes, new sharing modes, and connector updates. A completed spreadsheet is not a permanent guarantee.
This discovery method is proposed. The voice integration case study describes related retrieval and backend work without claiming this enterprise audit. Pair it with personal-data flow mapping.
Access mapping FAQ
Is folder structure the same as permission policy?
Not necessarily. Inheritance, shared links, groups, and service identities can change actual access.
Should unknown sources be indexed immediately?
Constrain the supported scope until the relevant access and ownership questions are resolved.
What should discovery produce?
A reviewed resource-and-identity map, known limits, named owners, and executable or operational permission fixtures for the planned integration.