Skip to main content

​
Workspace AI processors

​
Sources

Docs: Security and privacy, Personas (what Ponder shows when chat is unavailable), Ponder Primer (Clean up text and Keep the Parable named), Protection Primer. Web App: Workspace administrators open Protection → AI Processors. Parable staff set a Workspace’s allowed processors from Product Admin → Tenants → the Workspace → AI Processors. Some Parable features run an AI model over your Workspace’s data: Ponder chat, Ponder’s Clean up text, Parable naming and judgment tools, the AI functions in SQL, semantic Pool search, and schema inference on uploads. An AI processor is the service that runs the model. Protection → AI Processors lists every processor that can receive your Workspace’s data, with its retention terms, and lets a Workspace administrator switch processors off and choose the models features use.

​
Who can change it

Other members of the Workspace cannot open the page. A processor that Parable has not allowed for your Workspace shows Not allowed by Parable, and you cannot switch it on.

​
The processors

The page shows the processors and terms for your Workspace’s environment, and is the current record: it reads them from Parable’s own configuration. The same processors appear on the sub-processor list in the Trust Center.

​
Switch a processor off

  1. Open Protection → AI Processors.
  2. Turn off the processor’s switch.
  3. Read Before you save. Parable works out what the change would do and lists each feature that stops. For example, switching OpenRouter off stops Ponder chat on every Persona profile, and switching Vertex AI off makes Pool search match keywords only, refuses embed() in SQL, and stores uploads without AI-inferred column metadata.
  4. Choose Save changes in the page header, or Discard.
Once a processor is off, Parable sends it none of your Workspace’s data for the features that follow these settings. A feature that needs a switched-off processor stops with a clear message; it never falls back to another processor. Ponder chat, Ponder’s language features, the SQL AI functions, Pool search and schema inference on uploads all follow these settings. Schema inference on uploads runs on Google Vertex AI. It used to run on Anthropic, so a Workspace that switched Anthropic off to stop it must now switch Vertex AI off instead. With Vertex AI off, uploads still succeed; they are stored without AI-inferred column metadata.

​
Choose default models

Default models has one row per feature you can set. A default is the model a feature uses when nothing names one: a call that names its own model, such as ponder() with explicit model arguments, always uses that model.
  1. Turn on Use a Workspace default for the feature.
  2. Choose the model:
    • Ponder chat profiles take a model from Ponder’s model catalog. New Personas start from it; existing Personas keep their rankings.
    • ponder() and model() take a processor and the model’s provider, name, variant and version.
    • Jev takes a Jev model version.
    • Schema inference takes a processor and its model id.
  3. Read Before you save and save.
Turn a feature’s switch off to go back to Parable’s default. Changing the default for ponder(), model() or Jev changes what scheduled Plots compute. Before you save, the review counts the scheduled Plots that will recompute on their next run: the Plots your Plot schedules and Report schedules run whose SQL calls the function without naming a model. For Jev it also counts the Plots that may recompute, because they take the model from a column and rows that leave it empty use the default. When Parable cannot count them, the review says that scheduled Plots calling the function without naming a model recompute on their next run.

​
The embedding model

Parable sets the embedding model for every Workspace, so vectors stored for your data stay comparable. The page shows it under Embedding model for reference; it cannot be changed from the Workspace.