If you have an active AODocs Content Services subscription, you can choose one of the following storage platforms to store attached files in your Document Management libraries:
This article explains the differences between these options.
Automatically generated table of contents
Adding files to AODocs
In libraries using Google Cloud Storage or Azure Blob Storage, Google users and Microsoft users can:
- upload local files
- import files from OneDrive
- create Microsoft Office files – Word, Excel, or Powerpoint
The screenshot below shows a document in a library using Google Cloud Storage.
In libraries using Google Drive, Google users can:
- import files from Google Drive
- upload local files and convert them to the corresponding Google format (for example, convert a Microsoft Word file to a Google document)
- create Google format attached files
The screenshot below shows a document in a library using Google Drive.
Data localization options
For Google Cloud Storage, if your content is stored:
- in AODocs' own cloud file storage, the content is located in Google data centers located in the European Union and in the United States (US central Iowa, composed of four zones)
- in your own cloud file storage, the physical location depends on your choice of data center for the cloud file storage buckets
For Microsoft Azure Blob Storage, the physical location of your content depends on your choice of data center for your Azure containers. Learn more about data residency in Azure.
For Google Drive storage, Google Workspace administrators can decide to set a specific region for the AODocs storage account data. Learn more about Google Workspace data location options.
Recommended limits
Learn about the recommended limits in AODocs.
Current limitations for libraries using Google Cloud Storage or Azure Blob Storage
Below is a list of the main constraints that currently apply to libraries using Google Cloud Storage or Azure Blob Storage.
In libraries using Google Cloud Storage or Azure Blob Storage, users:
- must create libraries from scratch or by copy – the option to create libraries from templates is not yet available for libraries using Google Cloud Storage or Azure Blob Storage
- can’t export or copy any documents from or to libraries using Google Cloud Storage or Azure Blob Storage
- can't download attached files from views – learn more: Access attached files directly from a view
- can't use AODocs–Virtru integration
- can't set additional Google Drive permissions on attached files
- can't activate or use the Cherry Picker
We’re working on lifting these limitations and enhancing your experience with AODocs. We’re interested in your feedback and we’d love to discuss your needs!