Document Management¶
Use this section to administer document collections, diagnose access problems, and operate the services that store and index document files. A document record combines metadata, attached files, and versions. Associating a content type adds its profile form and data model to the document; documents without a content type use standard metadata and files.
Administrative Responsibilities¶
| Scope | Responsibilities |
|---|---|
| Domain and collection administration | Folder organization, document access, security profiles, reader/editor groups, and audit investigation. |
| Host administration | Database connections, file repositories, editor and extraction services, workers, capacity, and recovery planning. |
| Process development | Content-type forms and scripts that create, publish, version, archive, or remove documents. |
Administrative work requires the corresponding administration features and scopes; document access alone does not grant host configuration rights. Test access changes with representative reader and editor accounts in the relevant domain.
Example: A Contract Collection¶
The shared example uses Documentation → Contracts as its document folder, Contract as the content type, and Contract Access as the document security profile. Contract readers read published records; contract editors maintain the collection. Sample contract has number EXAMPLE-001, effective date 2026-01-01, and contract/schedule files.
Follow the collection setup for access configuration. The developer defines the profile, and the user registers the document.
Choose a Task¶
- Configure folders and document access.
- Operate storage, editors, search, and recovery.
- Read the user procedures.
- Understand scripted document operations.
Archiving a document version is a document state change. It is separate from the host's archive database connection. A document folder is an organizational location, not an independent backup of its files.