01
A focused experience
Replace a collection of generic prompts with a clear flow designed for one job.
Use · Build
Focused workflows, built on ISA Warden
Use purpose-built extensions for specific jobs—or publish the workflow your customers and teams need. ISA Warden supplies the context, permissions, and shared host capabilities.
Why extensions
Specialized work, familiar controls
Extensions focus the experience while continuing to rely on ISA Warden’s host services and access model.
02
Shared project identity
Use the same group project name and ID across every project-aware extension.
03
Isolated extension data
Keep each extension’s files in its own group folder rather than exposing another extension’s content.
04
Execution that fits the setup
Use local, private or configured cloud resources according to the models and services the workflow calls.
Extension marketplace
Find a workflow for the job
Evaluate each extension by the outcome it creates, the information it uses, and the host capabilities it needs.
Document comparison
ISA Compare
Review every exact addition, removal and modification between two confidential documents.
- Inputs
- Two PDF, DOCX, text, Markdown or structured-text documents
- Outputs
- An aligned, deterministic change review
- Model and data behavior
- Extraction and comparison run locally and do not require an external AI provider. Saved source text and project state use the selected group’s extension folder.
- Code boundary
- No native-code permission declared
- Access summary
- Projects and extension-owned group files
Evidence-based candidate review
ISA CV Compare
Compare up to 20 CVs with one role and company context using a consistent rubric.
- Inputs
- Role context and PDF, DOCX, text or Markdown CVs
- Outputs
- Scores, strengths, gaps, evidence and confidence for human review
- Model and data behavior
- ISA Warden owns document ingestion and scoped retrieval. The active model may be local, private or cloud-backed, depending on workspace configuration.
- Code boundary
- No native-code permission declared
- Access summary
- Projects, group files, document ingestion and extension chat threads
Meeting minutes
ISA Scribe
Turn a recording, transcript or pasted notes into editable meeting minutes and follow-up work.
- Inputs
- Microphone recording or imported/pasted transcript text
- Outputs
- Summary, decisions, actions, questions, risks and Markdown minutes
- Model and data behavior
- Audio stays off dashboard storage. Local transcription remains on-device; a configured external provider receives audio only after host confirmation for that job.
- Code boundary
- No native code
- Access summary
- Projects, audio, transcription, group files and extension chat threads
Tender and quote workflow
RAW Calculator
Turn RAW tender posts into supplier requests, manage responses and compare offers.
- Inputs
- RSX/XML specifications, supplier information and quote responses
- Outputs
- Selected posts, quote packages, comparisons, drafts and award support
- Model and data behavior
- RSX parsing and deterministic data processing run in the extension. Optional model-driven enrichment uses the active group-authorized model.
- Code boundary
- No native code
- Access summary
- Extension-owned quote projects, group files, chat threads, document snapshots and authenticated-user context
Shared projects
The same project can support several workflows
A group project has one stable identity in the host registry. Each extension can recognize that identity while its own files remain separate and inaccessible to the others.
Active group Shared project ID
ISA Compareisolated content
ISA CV Compareisolated content
ISA Scribeisolated content
Know what an extension can do
Review the facts before assigning an extension
A distribution record should make its identity, access and data behavior clear before an administrator adds it to a workspace or group.
Identity
Publisher, author, version and compatible ISA Warden release.
Access
Every requested permission and the host service it enables.
Code boundary
Whether native code or a privileged host modification is included.
Models and providers
Required or recommended models, sources, device needs, external handling and costs.
Stored data
What persists locally or in group storage, retention rules and uninstall behavior.
External flows
Any email, remote model, transcription or other service that can receive data.
Marketplace lifecycle
Discover, evaluate, use, and improve
- 01
Discover
Find a focused workflow by problem, audience, outcome, or publisher.
- 02
Evaluate
Review value, pricing, compatibility, permissions, providers, and code boundaries.
- 03
Use in context
The host applies the current user’s rights and the selected workspace and group.
- 04
Update and grow
Builders publish improvements while customers retain control over access and updates.
The marketplace connects people looking for focused workflows with builders turning specialist expertise into products.
Use · Build
Use a focused workflow or publish the one people need
Explore purpose-built extensions for specific jobs, or turn your own workflow and expertise into a product.