Questions
ISA Warden FAQ
Start with the ISA Warden app, then go deeper into extensions, development, or security and governance.
About the ISA Warden app
What is ISA Warden?
ISA Warden is a desktop AI workspace and orchestration layer. It brings models, conversations, documents, tools, agents, extensions, people, and access rules together in one environment controlled by your organization.
Can I use ISA Warden in a browser?
Not yet. ISA Warden is currently available as a desktop app. A browser-based app is planned for both organization-operated dashboards and ISA Warden-hosted dashboards. With an organization-operated dashboard, dashboard data stays in that organization’s environment; with the hosted option, dashboard data is held by ISA Warden.
Is ISA Warden an AI model?
No. ISA Warden is the layer around AI models. Your organization chooses which models and supporting capabilities are available for each workspace and group.
Can ISA Warden use local and remote AI models?
Yes. It can work with models on the device, on infrastructure selected by your organization, or through configured external APIs.
ISA Warden extensions
What is an ISA Warden extension?
An extension is a focused workflow that runs inside ISA Warden and can reuse selected host capabilities such as models, threads, files, projects, storage, audio, or transcription.
Who decides which extensions are available?
Workspace administrators add distributed extensions and decide which groups can use them. Developers can also mount source folders while building and testing.
Can an extension read all workspace data?
No. Workspace visibility does not grant file access. Extensions use their own group folder or ask the user to grant specific files or folders.
For developers
What can I build on ISA Warden?
You can build focused extension interfaces, assistants, and organization-specific workflows using the host’s selected models, documents, projects, tools, storage, and identity context.
Does my extension need to implement dashboard authentication?
No. ISA Warden supplies the authenticated workspace context through the host bridge. Extension code should not collect or store dashboard credentials.
Can I use native code?
Yes, when a workflow genuinely needs local parsing, long-running work, or operating-system integration. Native access must be declared and reviewed.
For security officers
How does ISA Warden reduce AI tool sprawl?
Organizations can provide purpose-built AI workflows inside one governed environment instead of adopting a separate point tool for every job. Security teams can apply consistent controls to the models, extensions, capabilities, and services people use.
Can organizations control where AI work runs?
Yes. Deployments can combine local, private, and selected external services according to the organization’s requirements and configuration.
How is access to capabilities controlled?
Access combines the current user’s rights, resource visibility, declared extension permissions, and host policy for the active workspace and group.
Does host permission control replace security review?
No. Deployments should still review model routes, external services, native components, data retention, and any network access used by a workflow.