Zia Agents

    Zia Agents connects SecureAI to the Zoho Zia agents your organization runs, so that the agents, the tools they call, the knowledge bases they read, the models behind them and the workflows they take part in all become visible in one inventory. SecureAI reaches Zia over OAuth, using a client you register in the Zoho API Console. Once an instance has fetched, the agents appear under Governance > AI Inventory and in the Zoho Zia Agents report set, and each one consumes a license.

    What a Zia instance covers

    The Zia Agents card sits under Directories/Agent Platforms in the application catalogue and offers a single service.

    • Zia Agents, under Governance, discovers and manages Zoho Zia agents, tools, knowledge base, models and workflows.

    Because that is the only service, the card carries one capability tag, Governance. A Zia instance does not act as an identity provider and is not assessed for risk posture.

    Note: SecureAI spells this application two ways. The catalogue card reads Zia Agents, while the creation panel is titled Instance Creation - Zia and the instance list shows Zia under Application Name. They are the same application.

    Prerequisites

    Before you add a Zia instance, arrange the following on the Zoho side.

    • A client registered in the Zoho API Console, of a type that issues a client secret. Registration returns the Client ID and Client Secret SecureAI asks for. See Register Your App.
    • The redirect URI that SecureAI displays, recorded against that client as its Authorized Redirect URI. SecureAI shows the exact value on the Connection step, so read it from there rather than assembling it yourself.
    • The data center your Zoho account belongs to. Zoho stores data regionally and each region has its own endpoints, so the wrong choice will fail to authorise. See Multi DC Support.
    • An account with access to the Zia agents you want discovered, since SecureAI sees only what that account can reach.

    Creating a Zia instance

    1. Go to Application Settings and click Manage Applications.
    2. Click the Zia Agents card. The Instance Creation - Zia panel opens on the General step.
    3. In Instance Name, enter a name that identifies the Zoho environment this instance points at. SecureAI fills the field in for you, and the name has to be unique.

    Note: If you keep a name that is already in use, SecureAI reports that an instance of that name already exists and that nothing was saved.

    1. To record what the instance is for, click Description and type into the box that appears. The description is optional and shows in the instance list.
    2. Leave Zia Agents selected under Choose Capabilities. It is selected for you and is the only service on offer.
    Fig 1: The General step of Instance Creation - Zia.
    1. Click Next.

    Note: Next saves the instance straight away. It appears in the instance list with the status Not Configured and stays that way until you finish the connection.

    Setting up the connection

    1. Check Connection Name, which SecureAI fills in for you and which you can rename.
    2. From Grant Type, select how SecureAI should obtain its token. Authorization Code signs in as a user and is the default. Client Credentials authenticates as the client itself.
    3. Read the value in Redirect URL and register it in the Zoho API Console as the Authorized Redirect URI of your client, if you have not already. SecureAI builds the value from its own host and the path /OAuthCode.do, and notes underneath the field that this is what has to be registered.

    Note: Register the redirect URI before you click Configure. Zoho rejects an authorisation request whose redirect URI does not match the one recorded against the client.

    1. Enter the Client ID and Client Secret the API Console issued for that client.
    2. From Data Center, select the region your Zoho account belongs to. The options are US, EU, IN, AU, JP, CA, SA, and CN.
    Fig 2: The Connection step of Instance Creation - Zia.
    1. Click Configure, then complete the Zoho sign-in and consent if you chose Authorization Code.

    SecureAI checks the credentials before it tries the connection. If either is missing it reports Client ID and Client Secret are required. against both fields.

    Fig 3: The Connection step reporting missing credentials.

    Managing a Zia instance

    The instance list on the Application Settings page is where a saved instance is maintained. Alongside the name, description and application, it reports Associated Services, when data last came in, how often SecureAI re-fetches, and a status.

    • Not Configured means the instance was saved but its connection was never completed.
    • Configured means the connection is in place.
    • Not synced means no data has been fetched yet.
    • Sync in progress means a fetch is running.
    • Sync completed means the last fetch finished.
    • Sync failed means the last fetch did not finish.

    To pull data straight away rather than waiting for the schedule, click Fetch beside the instance in Last Fetch Time.

    To change how often SecureAI re-fetches, click the edit icon beside the value in Fetch Interval, select Hourly, Daily or Weekly, set the Every value, then click Apply.

    To change an instance, click the edit icon in Actions. The Edit Instance panel presents the same content as creation, split across a General tab and a Connection tab, with Save to commit.

    Note: Client Secret keeps the stored secret masked in Edit Instance. Leave it as it is to keep the existing value, or type a new secret to replace it.

    To remove an instance, click the delete icon in Actions, then click Delete to confirm or Cancel to keep it. Deleting an instance permanently removes it along with every service, connection and discovered configuration under it, and every agent, user, model and tool synced through it, including their reports and dashboard data. The action cannot be undone.