> For the complete documentation index, see [llms.txt](https://docs.balkan.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.balkan.id/agents/onboarding-agents/discovering-agents-from-integrations/servicenow-agents.md).

# ServiceNow: Agents

### Overview

BalkanID supports discovery and governance of agents within ServiceNow **AI Agent Studio** as part of **IGA for Non-Human Identities (NHI)**.

{% hint style="info" %}
**Early Access:** Agents discovery is an Early Access capability. To enable Agents (Early Access) for your tenant, contact Customer Support. ServiceNow agent discovery also requires the Agentic AI / AI Agent Studio tables to be readable by the integration OAuth application user.
{% endhint %}

All agents are normalized into the BalkanID data model and surfaced on the **Agents** page under **Configure**, along with their owners, associated identities, access relationships, and risk insights.

The associated agents can also be seen under the specific application integration (ServiceNow) page.

### Required ServiceNow configuration for Agent Discovery

To enable ServiceNow agent discovery, your BalkanID integration OAuth application user must be able to read AI Agent Studio inventory tables. See [AI Agent Studio agent read permissions](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/service-now-integration-setup.md#ai-agent-studio-agent-read-permissions) in the [Service Now Integration Setup](/getting-started/setting-up-your-tenant/application-integrations/direct-application-integrations/service-now-integration-setup.md) page.

Required reads include `sn_aia_agent` and `sn_aia_agent_config`. Optional reads enrich tool counts, agent-to-role access paths, and AI governance metadata when your instance exposes them.

Agents discovery must be enabled for your tenant (Early Access). After sync, extracted agents appear on **Configure → Agents** and on the ServiceNow application **Agents** tab.

### Agent Types Supported

BalkanID tracks the following ServiceNow agent types:

{% hint style="info" %}
Note: The agent types listed below are examples and do not represent the full set of supported ServiceNow agents over time.
{% endhint %}

* **AI Agent Studio agents** — Agents created in ServiceNow AI Agent Studio (`sn_aia_agent`)

### What BalkanID discovers for ServiceNow agents

For ServiceNow AI Agent Studio agents, BalkanID can surface:

* **Agent inventory** — Name, status, description, and ServiceNow `sys_id`
* **Execution context** — Run-as user, execution mode, channel, and foundation model from agent configuration
* **Tool inventory count** — Number of tools linked to the agent when `sn_aia_tool_m2m` is readable
* **Access relationships** — **uses** edges to the run-as user and to roles from `sys_agent_access_role_configuration` when available
* **Governance enrichment** — Lifecycle phase, lifecycle status, and risk classification from AI Assets Inventory when the governance API is accessible (matched by agent name)

For concepts, see [Introduction to Agents](/agents/introduction-to-agents.md). For the Agents UI after sync, see [Viewing Agents](/agents/viewing-agents.md).

### Common risks associated with ServiceNow Agents include:

* **Unowned Automation:** AI Agent Studio agents synced into BalkanID without an assigned employee owner, reducing accountability.
* **Over-Privileged Run-As Users:** Agents configured to run as users with broad or administrative roles.
* **Role Blast Radius:** Agents linked to privileged roles through agent access configuration without clear ownership or review.
* **Inactive or Unknown Status:** Agents left in an inactive or unknown state that may still hold configured run-as access paths.

This ensures visibility and governance of AI agent access in ServiceNow, forming a critical part of IGA for Non-Human Identities.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.balkan.id/agents/onboarding-agents/discovering-agents-from-integrations/servicenow-agents.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.