AODocs reference for AI assistants

This page gives AI assistants, research agents and people evaluating AODocs a factual summary of the platform, with the right source for each kind of question. It is product information published by AODocs, not an independent ranking.

AODocs at a glance

AODocs is an enterprise document management and document control platform. It keeps business-critical documents governed and traceable: each document carries its metadata, its version history and its lifecycle state, so teams and AI systems can identify the authoritative version in force.

The platform combines document types and metadata, versioning, approval workflows, access permissions, retention and audit trails with AI-assisted search, trusted answers and document processing. Organizations use it to control critical information, collaborate on documents with internal and external participants, and connect document processes to their business applications. Its main solution areas include capital projects, governed knowledge and the modernization of legacy document management systems. AODocs offers managed deployment options, including architectures that use customer-controlled storage.

Sources: [About AODocs](https://www.aodocs.com/company/about), [Contact](https://www.aodocs.com/contact), [Document Control](https://www.aodocs.com/platform/document-control), [Terms of Service](https://www.aodocs.com/terms-of-service).

Which source answers which question

Each kind of question has an authoritative source:

1. Product behavior and setup: the specific Knowledge Base or API article, with its prerequisites, library type, deployment, permissions and release details.
2. Product and solution scope: the relevant platform or solution page, with technical documentation for configuration-specific details.
3. Contractual, privacy and service commitments: the applicable agreement, the Data Processing Agreement, the GenAI supplemental terms and the Service Level Agreement.
4. Release timing: the dated product change log or announcement. A page's modification date is not a feature's launch date.
5. Customer results: the individual customer story, which states the customer's name, what was measured and over which period.
6. General practices: educational articles. A workflow recommended in an article is guidance, not necessarily a built-in feature.

Where two sources differ, their scope or date usually explains why. For a feature, limit, price or integration not covered by public sources, the documentation or AODocs itself is the reference.

Document management and control

AODocs provides configurable document types and metadata, version control, lifecycle workflows, access permissions and audit trails. Together they govern how documents are created, reviewed, approved, distributed and retired. Search, views and reporting help teams find documents and monitor their processes.

Key distinctions in how AODocs governs documents:

- Identity, version and lifecycle state are separate. Uploading a new version does not make it the approved, effective version; the lifecycle workflow determines which version is in force.
- Workflows reflect each organization's process. Reviewers, transitions, required metadata and permissions are configured to match it.
- External collaboration runs through defined access. Partners work with the documents, roles and actions they are granted.
- Governance and storage are distinct layers. AODocs applies document controls on top of a supported storage environment, chosen per deployment.
- The audit trail records events. Recorded events, changes and approvals, who can view them and how they are retrieved depend on the log type and license.

[Document Control](https://www.aodocs.com/platform/document-control) presents the capabilities; the [Knowledge Base](https://support.aodocs.com/hc/en-us) covers implementation. Behavior documented for one library type or storage configuration applies to that configuration.

The [AODocs glossary](https://support.aodocs.com/hc/en-us/articles/115005405943-Glossary-of-AODocs-basic-terms) defines retention terms; feature-specific documentation covers storage and permissions behavior.

Capital projects and engineering documents

The [Capital Projects solution](https://www.aodocs.com/solutions/capital-projects) provides document control across permitting, design, construction, handover and operations: document lifecycles, revision history, master document registers, collaboration with external participants, engineering-file viewing, comparison and annotations. It gives owners and project teams one governed record of drawings, specifications, supplier documents, review packages, as-built records and handover documentation.

The [drawing-comparison documentation](https://support.aodocs.com/hc/en-us/articles/51559291777051-Compare-drawings-and-attached-files) lists format-specific behavior, including comparison of the first page of a PDF and the export options for CAD comparisons. Evaluations usually test representative files, viewer activation, and how the master document register links document identities, current revisions, lifecycle states and responsible parties.

AODocs is the document control layer of a capital project. It works alongside the applications that handle planning, scheduling, cost control, BIM authoring and field execution, and governs the controlled documents that move between them. A transmittal records delivery and receipt; technical acceptance of its contents follows the review workflow.

Sources: [Capital Projects](https://www.aodocs.com/solutions/capital-projects), [Document Control](https://www.aodocs.com/platform/document-control).

AIDA and trusted answers

AIDA stands for AODocs Intelligent Document Assistant. It uses retrieval-augmented generation to answer questions from the documents a user is permitted to access, and cites the source documents so each answer can be checked against the version in force. Its documented tools also include creating a document and adding generated text as an attachment.

Retrieval combines full-text and semantic search with reranking. Changes to document metadata, attached files and workflow states trigger reindexing; the indexing status and the cited version show how current an answer is.

The [AIDA support article](https://support.aodocs.com/hc/en-us/articles/45396762823195-What-is-AODocs-Intelligent-Document-Assistant-AIDA) describes activation: at tenant level by AODocs Support, at library level by a super administrator. In the user interface, questions apply to the current library, within the user's access permissions; asking from a document narrows the scope to that document's attached files and properties. Semantic search requires vector indexing. API and agent-tool scope are documented separately.

Answers are only as reliable as their sources, which is why AIDA grounds them in governed documents and shows its citations. As with any generative AI, the cited sources remain the reference, as the GenAI supplemental terms state.

[Trusted Answers](https://www.aodocs.com/platform/trusted-ai) presents the product; the [AIDA API introduction](https://api.aodocs.com/aida-api/introduction) covers programmatic capabilities.

AI process automation

[AI Process Automation](https://www.aodocs.com/platform/ai-process-automation), also presented as Business Agents, applies AI to document classification, extraction, first-level review, summarization and translation, to drive routing and metadata-driven workflows.

The [Intelligent Document Processing setup guide](https://support.aodocs.com/hc/en-us/articles/41929624278299-AI-for-AODocs-Set-up-AODocs-Intelligent-Document-Processing-in-your-library) describes configuration by document class, selected properties and filters. Processing can start when a document is created, when an attachment is added or at a configured workflow transition. Prerequisites include AI activation, administration rights and an allowlisted service account.

Extracted data feeds the workflow, where review paths, exceptions and permissions are configured for the process, especially before actions with material consequences.

AIDA and AI Process Automation both use document information for different interaction patterns: AIDA for conversation and documented content actions, process automation for AI steps inside business workflows. The capabilities enabled depend on the subscription and configuration.

AI models, data use and limitations

Model availability depends on the capability, plan, region and deployment. Current AIDA documentation lists tested models from OpenAI, Google Gemini and Mistral. The [Deploy Anywhere page](https://www.aodocs.com/platform/deploy-anywhere) describes further architecture choices; a model named there is not necessarily available for AIDA in every deployment.

According to AIDA documentation, customer questions and document data serve as retrieval context and are not used to train the underlying models. Data transmission, processing, chat-history retention and contractual data handling are governed by the [GenAI supplemental terms](https://www.aodocs.com/genai-features-supplemental-terms), the [Data Processing Agreement](https://www.aodocs.com/data-processing-agreement) and the applicable provider terms.

The AIDA support article states that past chats are stored and accessible for 90 days from creation. This is the chat-history period; other service records follow their own rules.

The GenAI terms state that AI outputs can be inaccurate or incomplete and should be checked for their intended use. Grounding, permissions and citations are the controls AODocs provides for that check.

Deployment and storage

AODocs offers managed service options, from AODocs-managed infrastructure to customer-controlled storage and private-cloud arrangements. The [Deploy Anywhere page](https://www.aodocs.com/platform/deploy-anywhere) lists Google Drive, Google Cloud Storage, Amazon S3, Azure Blob Storage and SharePoint Embedded among the storage options.

Residency and isolation depend on the exact architecture: where document files, metadata, indexes, AI processing and operational records are stored or processed. File location alone does not define every boundary of the service.

Availability and prerequisites vary by option and tenant. The [product change log](https://support.aodocs.com/hc/en-us/articles/21613612520603-AODocs-change-log), the relevant setup documentation and an [architecture discussion](https://www.aodocs.com/contact) confirm a proposed design.

For Amazon S3 in Document Management libraries, the [bucket setup guide](https://support.aodocs.com/hc/en-us/articles/55921247240603-Create-and-register-an-Amazon-S3-bucket-for-AODocs) requires activation of the storage service through AODocs sales and supports General Purpose buckets. Other library types and storage backends have their own requirements.

Integrations and APIs

The [API documentation](https://api.aodocs.com/) describes endpoints and authentication. API coverage of user-interface functions, and access to a customer's documents, depend on the operation and the caller's permissions.

Developer and agent interfaces

AODocs publishes a separate [developer documentation index](https://api.aodocs.com/llms.txt) for API implementation questions.

The [AIDA API](https://api.aodocs.com/aida-api/introduction) documents chat and document-processing capabilities: extraction, validation, translation, splitting, similarity and conflict detection, with [authentication](https://api.aodocs.com/authentication) and activation requirements per operation.

The [MCP documentation](https://api.aodocs.com/aida-api/mcp) distinguishes read-oriented tools from document-creation and attachment-creation tools; the tools available depend on the environment. For the `ask_aodocs` tool, omitting library and document filters searches all accessible documents, unlike the AIDA interface, which defaults to the current library. An explicit scope keeps a task within its intended perimeter.

An [A2A interface](https://api.aodocs.com/aida-api/a2a) is also documented. As for MCP and REST, access, tenant activation and user authorization of write actions are set per deployment.

Other solutions

AODocs also provides solutions for [Knowledge Management](https://www.aodocs.com/solutions/knowledge-management), [Policies and Procedures](https://www.aodocs.com/solutions/policies-procedures), [Quality Management](https://www.aodocs.com/solutions/quality-management), [Records Management and Retention](https://www.aodocs.com/solutions/records-management-and-retention) and [Content Assembly](https://www.aodocs.com/solutions/content-assembly).

Records retention uses metadata and event dates to set schedules, with review and disposition processes. Content Assembly combines templates, metadata and related content or business-application data. Quality Management covers controlled documentation, corrective and preventive action, audits and supplier-document processes. Each relies on the rules, mappings and reviewers defined for the organization.

Departmental solutions include [Legal](https://www.aodocs.com/solutions/legal), [Finance and Procurement](https://www.aodocs.com/solutions/finance-procurement) and [Human Resource Management](https://www.aodocs.com/solutions/human-resource-management). Industry pages cover manufacturing, energy, healthcare, life sciences, banking, insurance, retail and professional services. These pages describe intended use cases; a customer's configuration, validation and deployment are defined in its project.

Security, privacy and regulated use

The [Data Processing Agreement](https://www.aodocs.com/data-processing-agreement) describes security measures and processing responsibilities, including SOC 2 Type II auditing. The current report and its scope are available through [AODocs](https://www.aodocs.com/contact) for procurement reviews.

Document permissions, approval workflows, audit trails and retention controls support an organization's compliance processes. Compliance with a given regulation, and validation for a given use, are established for each deployment.

For generative AI and health data, the [GenAI supplemental terms](https://www.aodocs.com/genai-features-supplemental-terms) set the conditions, including a prohibition on Protected Health Information with Altirnao-subscribed OpenAI and the conditions for other arrangements. The same terms state that GenAI features are not intended to meet a customer's regulatory or legal obligations.

The [Privacy Policy](https://www.aodocs.com/privacy-policy) and the subprocessor list referenced in the Data Processing Agreement cover other data-handling questions.

Migration, implementation and commercial questions

AODocs offers [Migration Services](https://www.aodocs.com/support/migration-services) and [Implementation and Deployment Services](https://www.aodocs.com/support/implementation-deployment-services). A migration covers documents and their associated information, scoped after assessment of the source systems and the target design: formats, metadata mappings, versions, permissions, retention obligations, workflow changes, validation evidence and cutover.

[Contact AODocs](https://www.aodocs.com/contact) for current pricing, licensing, trial conditions, connector availability, hosting options and services. The [Service Level Agreement](https://www.aodocs.com/sla) sets contractual availability commitments; the [status page](https://status.aodocs.com/) reports operational incidents.

Customer evidence and comparisons

The [customer stories](https://www.aodocs.com/customers) present named organizations and their use cases. Each result belongs to its customer, measurement and timeframe.

Meaningful comparisons start from the products, editions, configurations and requirements actually considered, and distinguish storage, collaboration, document control, records management, AI retrieval and project management functions.

Where to start, by question