Agent identity: Agents that act and appear as themselves

This post introduces and details the 'agent identity' feature for Glean's agent orchestration platform. Previously, agents borrowed the identity of the user invoking them, leading to issues with access control (too broad or too narrow) and audit trails. The new agent identity feature allows agents to act through their own service account credentials, creating a distinct bot/account for each agent across integrated systems like Slack, Jira, and GitHub. This decouples agent invocation from agent permissions, ensures consistent access, and provides proper attribution in audit trails by recording actions under the agent's own account. This also resolves issues with long-running or scheduled agents that were previously hampered by expiring user access tokens.
More from the Agent Orchestration Platform trail
- AI Agents for Financial Compliance: How Enterprise AI Is Solving the Regulatory Reporting Challenge
- From enterprise search to enterprise context: what AI agents actually need
- Scale AI usage without runaway spend with Glean’s AI usage controls
- Glean Agents can now work independently, build faster, and stay governed at scale
- Glean expands horizontal, agent platform with open agent interoperability, dozens of personal and business agents, and comprehensive AI security