Can automated actions make changes to our production environment without approval?
That depends on your configuration. By default, actions that modify state require human approval. You can selectively enable automatic execution for validated playbooks, approved action types, and defined targets. Nothing runs outside your configured allowlists.
What happens if an automated remediation fails?
A supported playbook records the attempt and result and can route a failure to a human operator. Check integration responses and the target state; an attempted action is not a verified fix.
How does Martin handle permissions?
Martin operates under the caller’s actual RBAC role. If the caller cannot perform the action in the web interface, Martin cannot do it on their behalf. Medium-risk actions require a second approver, and high-risk or out-of-scope actions are blocked entirely.
Can we disable specific types of automated remediation?
Yes. Every consequence type, playbook, escalation path, and just-in-time response is independently configurable. You can run in monitor-only mode and enable enforcement incrementally as you build confidence.
Does this work with our existing tooling?
Yes. Fig Group governs and orchestrates your existing tooling rather than replacing it. Playbooks can call RMM, PSA, identity, cloud, backup, and security tooling via integration or webhook, then capture the full outcome in the same audit trail.