People
Roles for users, reviewers and administrators of the workflow.
Security & governance
Identity and Access
Decide who can use, configure and approve each agent, and which systems the agent itself may reach.
Access is defined on two levels
People and agents both get only the access they need.
Agents
Service accounts and scopes for each connected system.
Organisations
Data separated between customers and, where agreed, between teams.
How access is managed
Agreed per implementation.
Define roles
Who can view, review, approve or change the workflow.
Scope systems
Which records and actions each connection allows.
Review
Check access when people or workflows change.
Remove
Revoke access when it is no longer needed.
Least privilege by default
Broader access is a deliberate, recorded decision.
- Separate reviewer and administrator permissions.
- Use your identity provider where the setup supports it.
- Record approvals with the person who gave them.
Common questions
Where the components used in your implementation support it, we can discuss SSO during scoping.
Access for our team is limited to what is needed to build and support the workflow, and agreed with you.
We choose the model and provider for each task during scoping, based on the language, accuracy, latency and data-handling requirements. The workflow is not tied to one provider, so a step can be changed later if the agreed requirements change.
Discovery call
Start with the work that slows you down.
Bring us a process, a recurring enquiry or a pile of documents. We will explore where agents fit and what a useful implementation needs.
Book a discovery call