Feature tour: understand workspaces

Meaning

Documents need a home. Loose files scatter across drives, inboxes, and personal folders — and nobody shares the same map. A workspace in PaperOffice is the professional home for related documents. It is not just a folder name. It is the boundary where rights, AI-DMS processing, document types, and automation apply together. Teams use workspaces to keep invoices, contracts, or project files in one place with clear ownership. When a document arrives, it belongs to a workspace first. That membership decides who can see it, which agents may run, and how search and retention behave. Think of a workspace as the operating unit for Document AI — clear purpose, clear ownership, and a clear set of files.

Why

Workspaces matter because documents without a home create noise. Files land in the wrong place, permissions become inconsistent, and agents cannot target the right set of content. A well-defined workspace gives every file a professional context. Finance keeps invoices separate from HR records. Project teams keep correspondence close to contracts. Compliance can apply retention where it belongs. Without workspaces, PaperOffice would be a flat pile of files. With workspaces, Document AI works on the right scope — and people find the right documents faster. Scattered documents also slow audits and onboarding. New colleagues cannot learn a process if files sit in personal drives. Workspaces provide a shared professional map. Automation becomes safer because agents never roam across unrelated business areas.

Flow

Here is the simple flow. A workspace organizes documents by purpose and team. Documents land in that workspace through upload, sync, or connectors. Inside the workspace, OCR and metadata prepare each file. AI-DMS classifies and links content. Collaboration stays controlled: shares and roles decide who can view, edit, or export. The three ideas stay connected: workspace, documents, and collaboration. When these pieces align, Document AI is not abstract — it is a reliable daily workflow. Search finds the space by name and purpose, so teams jump to the right home without hunting menus.

In practice, teams open a workspace, review the documents list, and act with confidence that permissions already match the business boundary. Collaboration features do not override that boundary — they operate inside it.

Rights

Rights and collaboration belong inside the workspace boundary. Membership defines who enters the space. Shares grant access without mixing unrelated teams into one pile. Agents and exports respect the same boundary, so automation never leaks into the wrong audience. Review membership when teams change. Prefer clear ownership over clever exceptions. A calm rights model is part of Document AI maturity — just like clean document types and reliable intake.

Document the purpose of each workspace in the name or notes so people understand intent without opening settings. Retire unused workspaces deliberately rather than leaving ghost spaces. When credentials and memberships stay current, incidents become rare.

Create

Creating a workspace is straightforward. Name it after a real team, client, or process — keep the name short and searchable. Set the workspace type to match security and operating needs. Enable AI-DMS for this scope so recognition and classification run where they belong. Invite only people who need access. You do not need a perfect structure on day one. Start with one workspace that reflects real work, then refine as the team grows. If an existing workspace already matches the team, reuse it instead of creating duplicates. Duplicates split permissions and confuse agents.

Operate

Operate every day from the workspaces list. Search and filter before scrolling endlessly — own spaces, shared spaces, active spaces, AI-DMS. Open documents from the workspace name link so you land in the right operating scope. Review shares and AI settings as teams change. Prefer one workspace per real business boundary instead of mixing unrelated departments. Keep names honest so people recognize purpose at a glance. Healthy workspace hygiene is how Document AI stays understandable at scale.

After documents arrive, confirm that document types and AI-DMS results look sensible for that scope. Small checks early prevent large cleanup later. Return to Workspaces when switching contexts — for example from finance invoices to project contracts.

Abschnitt

Open Workspaces and review what already exists. Create one workspace for a real team or project. Add documents through upload or connectors, then apply AI-DMS. Assign rights carefully and only share what each team needs. Workspaces give every document a clear home — and that is the foundation of Document AI in PaperOffice.