We scan new podcasts and send you the top 5 insights daily.
Alex Lieberman says giving every employee Claude or Codex access to the right data has become an absolute nightmare for CIOs and CISOs. They lack a good gateway or control panel for data permissioning. Tenex started building bespoke permission systems and then productized its own gateway.
The defining characteristic of an enterprise AI agent isn't its intelligence, but its specific, auditable permissions to perform tasks. This reframes the challenge from managing AI 'thinking' to governing AI 'actions' through trackable access controls, similar to how traditional APIs are managed and monitored.
A critical hurdle for enterprise AI is managing context and permissions. Just as people silo work friends from personal friends, AI systems must prevent sensitive information from one context (e.g., CEO chats) from leaking into another (e.g., company-wide queries). This complex data siloing is a core, unsolved product problem.
AI coding agents thrive because developers have broad codebase access and work in a text-based medium. Enterprise knowledge work is stalled by fragmented data access, complex permissions, and multi-modal information (calls, meetings), which are significant hurdles for current AI.
Managing human identities is already complex, but the rise of AI agents communicating with systems will multiply this challenge exponentially. Organizations must prepare for managing thousands of "machine identities" with granular permissions, making robust identity management a critical prerequisite for the AI era.
For enterprises, the raw capability of foundation models is a security risk, not a selling point. The real product value lies in building "boundaries"—robust permissions, approvals, and audit logs that make powerful models safe to deploy company-wide.
A single AI agent can provide personalized and secure responses by dynamically adopting the data access permissions of the person querying it. This ensures users only see data they are authorized to view, maintaining granular governance without separate agent instances.
While personalized, continually learning models are a compelling vision, they clash with enterprise reality. Corporate data is highly compartmentalized with dynamic, user-specific permissions (e.g., ethical walls in law firms). This makes training a single, persistent model difficult and reinforces the utility of real-time, permission-aware RAG systems.
AI tools with natural language interfaces flatten organizations by giving non-technical staff, like sales reps, the power to perform complex data queries previously limited to SQL experts. This can inadvertently bypass poorly configured access controls, revealing sensitive data and forcing companies to re-evaluate their permissioning models for the AI era.
As employees increasingly build their own dashboards and micro-applications directly using LLMs, organizational backlogs are shifting. While end-user conversational tools solve front-end discovery and prototyping rapidly, they introduce fragmentation and destroy data standardization. Central platforms are now needed to step in and retroactively wire back-end data definitions and access control standards into those self-serve assets.
Instead of building complex new control layers for AI, the emerging best practice is to treat each agent as a separate entity. This means giving them their own accounts, API keys, and permissions, mirroring how you would onboard a new human employee to manage access and security.