Bind ownership at registration.
An agent carries a named owner and scope rather than borrowing an untracked service account.
Register internal agents as Business deployments, choose their connected tool scopes, and assign the members or groups who may use them.
Configure the internal agent’s tools and scopes before making it available to employees.
A wider agent grant cannot expand an employee’s authority. The effective toolset is the intersection of both permissions.
| Requested operation | Agent grant | Elena · Sales | Omar · Support |
|---|---|---|---|
| Read a customer account | Granted | Available | Available |
| Draft customer email | Granted | Available | Unavailable |
| Update a support ticket | Granted | Unavailable | Available |
| Delete a customer account | Not granted | Not offered | Not offered |
An agent carries a named owner and scope rather than borrowing an untracked service account.
Read, draft, update and delete can have different grants. An action outside the effective scope is not offered to the agent.
When an employee loses access, their agent loses delegated authority. Earlier activity remains available for investigation.
Registration associates an owner with each agent. Tool calls carry the agent and user identities.
Grants can reach down to a single action. An ungranted tool is not offered to the agent.
An agent working for Sales cannot borrow another team’s private access.
Offboarding removes access while the record of previous activity remains available for review.
Fabriq sits between the agents employees use and the connected systems they reach. Existing workflows can use the governed endpoint.
Disable the agent at the organization level. Subsequent access is refused; coding-agent sessions also have explicit session revocation controls.
Start with a named owner and a small task. Inspect the exposed tools, test an out-of-scope action, and review both identities and verdicts in the audit trail.