The AODocs storage account is a Google Workspace account. It's a technical account that AODocs uses to perform system tasks.
All organizations using AODocs must have an AODocs storage account, including organizations using Microsoft 365.
– Consider the AODocs storage account as a technical account.
Never change the name or email address of an AODocs storage account.
– Changing the password of the AODocs storage account or enabling 2-step authentication on it doesn't impact AODocs.
In the case of organizations using Google Workspace and storing their attachments in Google Drive, the AODocs storage account also owns your managed files in Google Drive. When users import files into AODocs, the ownership is automatically transferred to the AODocs storage account. In the following example the AODocs storage account is named AODocs Storage.
When users create files in folders managed by AODocs, the files are initially created with the creator account as their owner, and they are then automatically transferred to the AODocs storage account.
AODocs uses the AODocs storage account to build an internal folder structure that is needed to perform certain AODocs functions. In particular, AODocs documents owned by the AODocs storage account are organized in a slightly different way from regular user accounts and some folders may appear “duplicated”. As a result, the AODocs storage account must be dedicated to AODocs and not be used directly by human users.
AODocs super administrators can configure multiple AODocs storage accounts.
Learn more: Manage AODocs storage accounts.
It may be necessary to have multiple AODocs storage accounts in the following situations:
- To separate access permissions and avoid a single account having access to all files managed by AODocs.
- To avoid performance bottlenecks when a large number of files are managed by AODocs. We typically recommend not to exceed 50,000 files per AODocs storage account.
For more information about AODocs performance best practices, contact the AODocs Support team by email at firstname.lastname@example.org or open a ticket.
AODocs storage accounts can be allocated only at the library level: all the files contained in a specific library must be owned by the same AODocs storage account. However, multiple libraries can share the same AODocs storage account. If several AODocs storage accounts have been configured, when you create a new library, AODocs asks you to select an AODocs storage account from the list of available accounts.
Note: Google Drive doesn't allow ownership transfer between accounts belonging to different Google domains. As a result, when a user who doesn't belong to the AODocs storage account's domain adds a file in AODocs, AODocs must make a copy of the file so the copy is owned by the AODocs storage account. Learn more: Add files and folders as an external user.
AODocs storage accounts don't use AODocs licenses, no matter how many AODocs storage accounts are configured in your domain.
Important: In Google Drive, moving files and folders or modifying file permissions directly from the AODocs storage account can disrupt AODocs processes and result in malfunction.
Learn more: Purchase extra Drive storage for your users.