Activate AODocs AI using Gemini

This article explains the steps required for customers to activate AI features on AODocs on their tenant. It is for IT administrators of customer tenants.

When you have completed the technical setup below, contact the AODocs Support team by email at support@aodocs.com or open a ticket. The AODocs Support team will finalize the activation. 


Automatically generated table of contents


Overview of AODocs AI features

AODocs AI includes:

AODocs AI uses Gemini models on Google Cloud Gemini Enterprise Agent Platform (formerly Vertex AI). Supported models are always the latest ones we have tested and that are available on Agent Platform. Availability can differ by region (for example, between the United States and Europe). For the recommended model on a given AODocs instance, contact the AODocs Support team.


Technical setup by your IT administrator

Paid plan customers can authenticate using either a service account (recommended) or API-based authentication.

#Service account authentication (recommended) #API-based authentication

This method lets AODocs securely access the Gemini models via your Google Cloud Platform (GCP) project.

Create a Google Cloud Platform (GCP) project

If you don't already have a dedicated project for AODocs AI services:

1. Go to the Google Cloud Console.

2. Open the project picker and select New project.

3. Enter a project name and click Create. 

4. Note the Project ID – you will need this later.

image01.png

Activate the Agent Platform API

You must activate the Gemini Enterprise Agent Platform API (aiplatform.googleapis.com) to allow Gemini models to process your data.

Note: Google renamed Vertex AI to Gemini Enterprise Agent Platform. The Vertex AI API is now called the Agent Platform API, and the Vertex AI User role is now called Agent Platform User. Only the names changed: the API and the role are the same. Learn more: Gemini Enterprise Agent Platform name changes (Google Cloud documentation).

1. Go to the Agent Platform API page in the Google Cloud Console.

2. Select your project. Make sure your specific project ID appears in the URL.

3. Click the Enable button.

Grant the Agent Platform User role

You must grant AODocs permission to use the API within your project.

1. In the GCP Console, go to IAM & Admin > IAM.

2. Click Grant Access.

3. In the New principals field, paste the service account corresponding to your AODocs instance:

  • US Instance: document-assistant@document-assistant-prd-usc1.iam.gserviceaccount.com
  • EU Instance: document-assistant@document-assistant-prd-euw3.iam.gserviceaccount.com

In the Select a role field, search for and select Agent Platform User (roles/aiplatform.user).

Note: The Agent Platform User role grants more permissions than AODocs strictly needs. If your organization's security policy requires it, you can use a narrower custom role instead.

4. Click Save.

Send your GCP project ID to AODocs Support

Contact the AODocs Support team by email at support@aodocs.com or open a ticket. Your AODocs Support agent will explain how to send your GCP project ID to AODocs securely. 

Use this method if you prefer to use a specific API key.

Generate an API key

1. Generate an API key in the Google AI Studio or Google Cloud Platform (GCP) console. AODocs cannot do this on your behalf.

2. Create a Secret ID – use the following links to securely store and register your secret:

Send your secret ID to AODocs Support

Contact the AODocs Support team by email at support@aodocs.com or open a ticket. Your AODocs Support agent will explain how to send your secret ID to AODocs securely. 


Finalize the activation by AODocs Support

Complete the technical steps outlined above and send the required information to AODocs Support. 

You can specify:

  • the specific libraries in which you want to activate AODocs AI
  • which features (AIDA, AODocs Intelligent Document Processing) to activate in each library

AODocs Support will then finalize the activation of AODocs AI on your tenant.

After activation

  1. AODocs Support enables AIDA on your tenant.
  2. A super administrator enables it on each library in the UI (or via the Tenant & Library API).
  3. Developers can then call chat and other AIDA endpoints with the same OAuth token as the core AODocs API — see the AIDA API introduction.

Note about indexing time: When you activate document vector indexing for the first time, libraries with millions of documents may take several hours to fully index.

Note: For developers: after AODocs Support enables AIDA on your tenant, you can also manage library enablement and use AIDA features programmatically via the public AIDA API. See the AIDA API introduction.


Was this article helpful? 0 out of 0 found this helpful
If you didn’t find what you were looking for, don’t hesitate to leave a comment!
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.