Feature tour: storage mounts

Meaning

Documents need a controlled path into PaperOffice. Files sit on NAS shares, sharees, and cloud folders — and teams lose time copying them by hand. A storage mount is the professional storage path from an external source into a workspace. It is not a one-off upload. It is the durable link that decides where files come from, how often they are read, and which workspace receives them. When a storage mount is active, documents arrive where AI-DMS, document types, and agents can process them with clear ownership. Think of storage mounts as the intake valves for Document AI: trusted source, clear target, and visible status. Operators should understand this page before changing production settings. A clear mental model prevents accidental misrouting and keeps Document AI predictable for every team that relies on the same workspace boundary. In PaperOffice, this page is part of a larger Document AI system: workspaces hold documents, storage mounts feed them, agents automate them, and document types classify them. Understanding this page means understanding how your team keeps professional control over information.

Why

Storage Mounts matter because manual upload piles do not scale. Each storage mount owns one storage path, so finance sharees do not mix with project shares. Ownership stays explicit: source type, mount or share, and target workspace appear in one list. When documents arrive through a storage mount, AI-DMS and agents run in the right boundary instead of a mixed dump. Teams reduce copy-paste rituals and keep audit-friendly intake. That is why storage mounts are the operational bridge between external storage and PaperOffice workspaces. That operational clarity is what separates professional Document AI from ad-hoc file sharing. When the purpose of the page is explicit, teams spend less time searching and more time completing the real work. Use this page as the daily control surface, not as a rarely opened settings screen. The more consistently teams work here, the fewer exceptions accumulate outside the intended process.

Flow

Ingest follows a simple flow. First, choose a source: a storage mount, an IMAP share, or a cloud folder. Second, the storage mount maps that source into a workspace with rules and labels teams understand. Third, documents arrive ready for OCR, classification, and automation. Search finds storage mounts by name when the list grows. Filters by NAS, email, or cloud keep large fleets readable. The storage mount list is the control room for intake — not a hidden background job. Keep this flow in mind when onboarding colleagues. If someone only learns buttons without the flow, mistakes appear later in status columns and review queues. Practice the happy path once with a real example from your organization. Real examples beat abstract training because status, labels, and rights become concrete.

Rights

Sources and control must stay intentional. Only trusted mounts and sharees should be connected. Each storage mount targets one workspace boundary so rights and AI settings stay coherent. Crawl status and errors remain visible in the list, so teams can react when a path fails. Sharing and collaboration still happen inside the workspace that receives the files — the storage mount does not bypass membership. Review source credentials and target workspace before activation. Security is not an afterthought on this page. Every list, filter, and open action should reinforce the same rights model so automation never outruns authorization. If a colleague cannot see an entry, that is usually membership — not a broken filter. Confirm access before assuming a technical failure.

Create

Creating a storage mount is deliberate. Name it with a short label teams will recognize. Pick the source type that matches the real path — NAS, email, or cloud. Bind the workspace so documents land in the correct home. Then activate and verify the first crawl. Do not save incomplete storage mounts into production fleets. A clear name, correct source, and correct workspace prevent silent misrouting. After creation, watch file counts and error indicators in the overview. Take a moment after create to confirm the first result looks correct. Early verification is cheaper than correcting a fleet of misconfigured entries later. Prefer fewer, well-named entries over many vague ones. Names and scopes that teams recognize reduce support tickets and accidental edits.

Operate

Operate storage mounts every day with search and filters before scrolling the full list. Open a storage mount by name when settings must change. Watch errors and file counts as sources evolve. Pause or fix a storage mount when a mount credential expires. Keep inactive or broken paths visible until they are repaired or removed. Healthy intake is quiet — problems show up in status columns first. Treat the storage mounts list as an operations board, not a one-time setup screen. Healthy daily operation is quiet. When indicators stay green and lists stay readable, Document AI remains trustworthy for auditors and for the people who depend on it. Schedule a short weekly review of this list when volume is high. Ten minutes of hygiene prevents hours of firefighting later.

Abschnitt

Open Storage Mounts, review active sources, and create one storage mount for a real path. Bind it to the correct workspace, start the crawl, and confirm the first files arrive. PaperOffice keeps intake visible and controlled — so Document AI always works on the right documents. Start with one deliberate action today, verify the outcome, and only then scale the pattern to the rest of the team.