Agent Binding
Decide how ERP-aware your agent is — and which organization it belongs to
Every user-defined agent and process has a Binding: a single setting that decides whether the agent uses ERP.net at all, and whether it's tied to a specific organization or works across any of them. Binding gates which capabilities you can turn on, which organizational features apply, and where the agent can be run.
You'll find it on the agent's Binding settings (it was previously called Organization). You can change it later, but doing so may turn off capabilities that no longer fit.
The three choices
| Binding | What it means | ERP capabilities | Organizational features |
|---|---|---|---|
| Generic | Runs anywhere. The agent doesn't talk to ERP.net at all. | Off | Off |
| ERP.net (any organization) | Uses standard ERP.net entities and is portable across organizations. | On (standard entities only) | Off |
| Specific organization | Bound to the current organization. May use that org's MCP servers, permission policies, entity instructions, and user-defined attributes. | On (standard + org-specific) | On |
Think of it as a ladder: each step up unlocks more, and locks the agent more tightly to the world it depends on.
When to pick each one
Generic
Pick Generic when the agent doesn't need ERP.net at all — pure-language assistants, writing helpers, brainstorming partners, summarisers, translators, code reviewers, or agents that only use non-ERP capabilities like web search or general knowledge.
- The capabilities picker hides every ERP capability — there's nothing to wire up.
- The agent runs the same way regardless of which organization you're connected to (or whether you're connected at all).
- Best for agents you want to share broadly, or use across many different ERP instances without re-configuring.
ERP.net (any organization)
Pick ERP.net (any organization) when the agent works with standard ERP.net data — customers, items, sales orders, document types, warehouses, and other entities that exist in every ERP.net deployment — but doesn't depend on anything specific to one organization.
- ERP capabilities are available; org-specific features (MCP servers, permission policies, entity instructions, custom attributes) are not.
- The agent stays portable: connect it to any ERP.net organization and it will work.
- Best for reusable specialists like "Order Statuser", "Customer Lookup", "Stock Reporter" — anything that asks the same kind of question of any ERP.net instance.
Specific organization
Pick Specific organization when the agent depends on something only one organization has — its custom MCP servers, its permission policies, its entity instructions, or attributes defined by your team on top of the standard entities.
- The agent locks to the organization you're connected to when you make the choice. It will only work when that organization is the active one.
- Unlocks the full capability set, plus organizational features layered on top of standard ERP behavior.
- Best for agents that automate your workflows — agents that know your document types by ID, your specific price lists, your custom MCP servers, your team's entity instructions, or your custom-defined fields.
How to choose — quick rules
- Does the agent need to talk to ERP.net at all? No → Generic.
- Could the same agent run unchanged on another ERP.net organization? Yes → ERP.net (any organization).
- Does it depend on anything specific to this organization (your MCP servers, your permission policies, your entity instructions, custom attributes)? Yes → Specific organization.
When in doubt, pick the least specific option that still lets the agent do its job. Less specific = more portable, easier to share, easier to maintain.
What changes when you switch binding
- Generic → ERP.net — ERP capabilities become available; you can turn them on in the Capabilities tab.
- ERP.net → Specific organization — the agent locks to your current organization. Organizational features (MCP servers, permission policies, entity instructions, custom attributes) become available.
- Specific organization → ERP.net (any organization) — the lock to the organization is dropped. Any MCP servers you had pinned are cleared, and instance-specific behavior no longer applies.
- Any → Generic — ERP capabilities you had selected are removed automatically, since they no longer apply.
Other settings (name, instructions, greeting, reasoning level, base agent) are not affected by binding changes.
Binding and other features
- Capabilities — the picker only shows capabilities your binding allows. ERP capabilities are hidden in Generic; instance-only capabilities require Specific organization.
- Optimization — only meaningful for ERP-bound agents (ERP.net or Specific organization), and stored per organization. See Agent Optimization.
- Sharing — Generic and ERP.net agents are the easiest to share broadly. Agents bound to a Specific organization are still shareable, but only useful to colleagues who connect to that same organization.
- Delegation — a lead agent can delegate to a sub-agent only if both can run in the current context. If your overseer is bound to a Specific organization, its specialists should be bound the same way (or to ERP.net) so they always work in the same context. See Delegation & Sub-Agents.
- Permission policies and entity instructions — only apply to agents bound to a Specific organization.