Processing chain approval is not the same as approving an item in a review session. Review approval decides whether generated output is accepted. Processing chain approval decides where your data is allowed to go.
Processing chains and parties
A model’s processing chain is every organisation its requests can reach. That includes the gateway and every provider the gateway may route the model to. A gateway such as OpenRouter can send one model to several providers, so its chain can list several parties. Each organisation in the chain is a party. Enterspeed reviews every party and gives it one of two statuses:
A task configuration’s processing chain is the chain of every model it uses: the specialist’s model and the model of each AI evaluation quality check. Every party in it that Enterspeed has not approved needs your approval.
An approval covers the party, not one model. Once you approve a party, every model and every task configuration that sends data to it is covered.
Approving a party records that your organisation holds the data processing agreement with that party.
What is refused until you approve
Your tenant’s approval mode is set by Enterspeed. It decides how much is refused while a party is still waiting for approval.
Adding a model to your tenant, or switching a disabled one back on, is also refused while a party in its chain is waiting for approval.
In Strict mode, a task configuration that is missing approval is shown as Disabled — approval needed. A disabled configuration stops every one of its versions, including an older version whose chain was already covered.
In Non-strict mode, the configuration shows Processing chain approval not given. It still runs, but you can’t save changes to it or publish a version until the parties are approved.
Enterspeed can turn processing chain approval off for a tenant. Then nothing is refused, and the settings page says that processing chain approval is turned off for your organisation.
Approve the parties
1
Open the approval page
Go to Settings → Processing chain approval. Needed to run your task configurations lists every task configuration that is missing approval, grouped by environment. Each one shows which model needs which parties.You can also click Review processing chain on a disabled task configuration to approve only that configuration’s parties.
2
Confirm the statement
Check the statement. It names each party you are approving, and confirms that your organisation is responsible for the data processing agreement with it.
3
Click Approve
Task configurations whose processing chain is now approved can run again.
A configuration that stays disabled
Retry items that failed for missing approval
An item whose processing chain is not approved fails before any data leaves Speedtrain. Its failure says that the task configuration is blocked by processing chain approval and links to Settings → Processing chain approval. Once the parties are approved, retry the failed items. In a review session, Retry n failed retries every failed item in one go. You can also retry a single item.Read approval from the MCP server
The Management MCP server shows processing chain approval but cannot approve. When a save, publish, start or retry is refused for missing approval, the agent names the party, tells you to approve it in Settings → Processing chain approval, and does not try to work around it. Task configurations and review session status carry the approval state indataHandlerConsent, and two read-only tools list what is missing and what is approved. Management MCP tools