Layer 1
Guardrails
Each role operates only inside a defined scope of tasks, tools, and instructions.
Security & Oversight
Security in plain English: safe systems, clear boundaries, and client control
This page answers the core question: is this safe, and how do you stay in control? Our approach is minimum data, maximum control, with clear oversight and safe-failure behavior built into every Digital Role.
Security approach
We design Digital Roles as bounded operational systems. They are not open-ended bots. Scope, tools, approvals, and escalation behavior are configured before the role is allowed to operate.
What we collect / what we do not
- Collect only the data needed to perform the configured workflow.
- Use server-side integrations for operational systems where possible.
- Do not put secrets in the client bundle.
- Do not log sensitive payload contents in routine operational logs.
Access control and MFA
- MFA on hosting, DNS, CRM, and email/admin systems.
- Least-privilege access for integrations and team accounts.
- Scoped credentials and role-based permissions wherever supported.
- Key rotation and credential review on a regular cadence.
Audit logs and traceability
- Request ID, timestamp, endpoint, and result codes logged for APIs.
- Role actions and approval events recorded for review.
- Escalations and pause events are traceable.
- Logs support troubleshooting and accountability without over-collecting content.
Safety Built In
Five simple safety layers that keep each role predictable
You stay in control with clear boundaries, approvals, escalation, logs, and a pause switch on every role.
Layer 2
Approval Thresholds
High-risk or customer-impacting actions can require approval before execution.
Layer 3
Escalation
Uncertain cases pause and notify your team instead of guessing or improvising.
Layer 4
Audit Logs
Actions, approvals, and outcomes are recorded for review and troubleshooting.
Layer 5
Pause Switch
You can disable a role instantly and fall back to manual handling at any time.
Incident response basics
We define a response path for outages or abnormal behavior: pause the role if needed, notify the owner, fall back to manual handling, and review logs before resuming automated behavior.
Reliability and monitoring
- Uptime monitoring for core pages and operational endpoints.
- Alerting for service failures and repeated endpoint errors.
- Fallback processes documented before go-live.
- Review and tuning after launch to reduce false positives and missed escalations.
Clear boundaries on what systems can and cannot do
Boundary-setting is explicit and role-specific. Examples include blocked actions, approval-only actions, and pause triggers.
Blocked entirely
Examples: contract signing, policy publication, refunds, or off-policy booking confirmation without human approval.
Approval thresholds
High-value, customer-impacting, or uncertain actions can require explicit approval before execution.
Pause and escalate
Unclear or out-of-scope cases pause and notify the owner rather than guessing.
Looking for implementation details? See the Small Business AI Oversight and How We Prevent AI Mistakes, plus the framework hub for additional control guidance.
Need a security-first rollout plan?
We can define boundaries, approvals, escalation timing, and fallback procedures before deployment.
What Happens Next
- 1We review what you shared (even if it is rough)
- 2We recommend the simplest role that helps first (in plain English)
- 3We offer a quick friendly walkthrough (15 min) if it looks like a fit
- 4We outline a simple next step and what to automate first
Typical response: 1-2 business days
Typical implementation timeline: 2-4 weeks for one Digital Role
Best suited for businesses with active operational volume.