Current Problem

When setting up the Rovo connector with Google Drive using Domain-wide Delegation, Atlassian Cloud dynamically sets the "Name" (and the associated email-style identifier) for the API client. This value is currently non-modifiable by the administrator.

Reference: https://support.atlassian.com/organization-administration/docs/connect-google-drive-to-rovo/#Connecting-to-Google-Drive

In large organizations with strict auditing and security naming conventions, having a fixed, system-generated name makes it difficult to the following things.

1. Identify the purpose of the API client at a glance within the Google Admin Console.
2. Align the connector with internal documentation or asset management naming standards.
3. Distinguish between multiple Rovo connectors if a customer has multiple Atlassian sites connected to the same Google Workspace.

Suggested Solution

Provide an option within the Rovo connector setup screen (Atlassian Administration) to specify a custom "Client Name" or "Display Name" before the API client is registered or the Client ID is generated. This name should then be reflected in the Google Admin Console's Domain-wide Delegation > API clients list.