> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wisdom.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Parameterized Agents

Parameterized Agents let you define an input schema on any agent so it accepts runtime variables, an org ID, a department name, a list of assets to analyze, or a recipient email. One agent definition can then run for multiple subscribers, with each run scoped to that person's data permissions and parameter values. This guide walks you through defining input parameters, configuring subscriptions, and managing templates.

## How it works

An adaptable execution workflow that maps central logic templates to individual subscriber environments through a four-stage process.

<Steps>
  <Step title="Define input parameters" icon="sliders">
    Open your agent in edit mode and define an input schema: variable name, type, description, and an optional default value. Supported types are text, number, boolean, email, and Slack.
  </Step>

  <Step title="Collect runtime parameters" icon="input-text">
    When a user manually triggers a parameterized agent, a generated input form collects their values. Submitted values are injected wherever you reference the parameter throughout the agent's prompts and node configurations.
  </Step>

  <Step title="Iterate over parameter value sets" icon="arrows-repeat">
    Provide multiple value sets and the agent runs once per set, each in an independent context. No list type exists.
  </Step>

  <Step title="Manage subscriptions and templates" icon="users-gear">
    Admins can publish an agent as a template and push-enroll users as subscribers. Each subscriber has their own parameter bindings. When the agent runs:

    * Each subscriber receives a run scoped to their identity and parameters.
    * Runs execute under the runner's (owner's) identity, and RLS/CLS are enforced based on the runner's permissions, not the subscriber's.
    * Failures are isolated: one subscriber's error does not affect any other subscriber's run.
  </Step>
</Steps>

### Subscription visibility

Depending on your subscription status, agents will appear in one of two distinct tabs within your workspace:

| Tab            | What it shows                                                                                     |
| :------------- | :------------------------------------------------------------------------------------------------ |
| **My Agents**  | Agents you created and agents you are subscribed to. Subscribed agents display a Subscribed pill. |
| **Agent Runs** | A history of each agent execution, with logs, node-by-node inspection, and reviewed runs.         |

## Target users

Parameterized Agents are available to:

* **Admins**: Define input schemas, publish templates, and push-enroll subscribers.
* **Agent Builders**: Build parameterized workflows and test with different input values.
* **All users**: Subscribe to published templates and trigger agents with their own parameters via the input form.

## FAQs

<AccordionGroup>
  <Accordion title="What parameter types are supported?">
    Text, number, boolean, email, and Slack. File and attachment input support is on the roadmap.
  </Accordion>

  <Accordion title="Is scheduled fan-out supported?">
    Yes. Scheduled fan-out is supported in the latest version.
  </Accordion>

  <Accordion title="Does each subscriber's run use their own row-level security?">
    No. Runs execute under the runner's (owner's) identity, and RLS/CLS are enforced based on the runner's permissions, not the subscriber's.
  </Accordion>

  <Accordion title="Can subscribers see each other's run logs or outputs?">
    No. Each subscriber can only see their own runs. Run logs and outputs are not shared across subscribers.
  </Accordion>

  <Accordion title="Can an admin update a template after users have subscribed?">
    Yes. Template updates propagate to all subscribers on the next run. Existing subscriber parameter bindings remain valid unless the input schema changes in a breaking way.
  </Accordion>

  <Accordion title="What is the difference between a subscriber and a viewer?">
    Viewer access (IAM) controls who can see that the agent exists at all. Subscription controls who runs the agent and receives its output. These operate independently—an admin can push-enroll a subscriber, which implicitly grants viewer access if it isn't already present.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Understand domains" icon="layer-group" href="/setting-up-wisdom-ai/manage-domains/understand-domains">
    Learn how domains organize the data logic and permissions your agents run against.
  </Card>

  <Card title="Domain Health" icon="heart-pulse" href="/product-updates/spring-2026/domain-health">
    Measure and improve your domain's readiness before opening it to subscribers.
  </Card>
</CardGroup>