AODocs opens to external users and provides larger libraries with Google Cloud Storage

This historical announcement described two AODocs platform improvements planned for November 2021: non-Google identities for external users and storage of attached files in Google Cloud Storage. It records the roadmap at that time, not current availability or deployment prerequisites:

• Planned authentication for external users with non-Google identities, including Microsoft sign-in and email/password; and
• Planned storage of attached files in Google Cloud Storage.

The intended use was to involve clients, suppliers, and external partners in AODocs workflows and provide another storage option for legacy content. Whether a current deployment can meet its scale or regulatory requirements depends on the selected storage, configuration, and document process.

Invite non-Google users to participate in your AODocs libraries

AODocs use cases can involve clients, suppliers, outside counsel, and other partners without a Google account. The November 2021 roadmap described these planned external-user capabilities; current identity, invitation, and permission requirements must be checked before enabling access:

• Planned sign-in with a Microsoft account or an AODocs email/password account.
• Planned participation in document properties, views, and workflows, subject to the user's permissions and supported library configuration.
• Planned preview, editing, and creation of attachments in Google Cloud Storage; supported file formats and editing tools depend on the current configuration.

These plans were intended to support cross-company document processes such as supplier portals, technical documentation, and client exchanges. Access and workflow setup must match the participants and documents involved.

Scale up your libraries with Google Cloud Storage

Some organizations retain legacy content in on-premises systems because of scale, storage, or regulatory requirements. The November 2021 roadmap presented Google Cloud Storage as another storage option for AODocs libraries. Replacement of a legacy repository requires migration planning and validation against the organization's actual requirements:

• Improved scalability: The roadmap proposed Google Cloud Storage for larger document libraries. Capacity, import throughput, and response times must be evaluated for the source repository, document volume, and target configuration; no fixed migration speed or unchanged performance should be assumed.
• Country-level location: Google Cloud Storage offers a growing list of options. Object data location depends on the chosen region, dual-region, or multi-region and the service terms. That selection does not by itself establish that every document-related operation satisfies a country's data requirements.
• Customer-managed encryption keys: Google Cloud Storage supports customer-managed keys through Cloud KMS, allowing you to use your own encryption keys for object data when the key, location, and service permissions are configured correctly. Confirm that the selected AODocs deployment supports the intended setup.

These were the planned next steps in AODocs' November 2021 roadmap. For a current deployment, check present-day product documentation and the identity, library, storage, and permission settings required for the intended use.