SECURITY & GOVERNANCE
Control who can see, decide, and act.
Fonix is designed around defined authority. Users and AI employees receive access according to their role, company context, assigned responsibilities, and approved capabilities.
DEFINED AUTHORITY, EVERYWHERE
Access follows role and context.
Fine-grained permissions
Roles and permissions determine which pages, records, and actions are available to each user.
Company-aware access
Business activity operates within a selected company context, with broader access reserved for specifically authorized roles.
Two-factor authentication
Supported accounts can use two-factor authentication as an additional sign-in control.
Governed AI authority
AI employees operate through assigned roles, approved tools, autonomy settings, and usage limits.
Human approval
Sensitive automated actions can be held for explicit human approval.
Visible system actors
AI employees have named identities so their tasks and activity do not appear as anonymous system behavior.
Activity and change history
Operational activity can be associated with the actor, action, target, and relevant process context.
Provider and cost controls
AI providers, models, credentials, usage, and agent budgets can be managed through the AI engine.
GOVERNED, NOT UNLIMITED
Intelligence should never imply unlimited authority.
Fonix separates what an AI employee can understand from what it is permitted to do. An agent can be constrained through:
- Assigned company and role context
- Explicit permissions
- Approved tools
- Input and output contracts
- Autonomy level
- Human approval requirements
- Confidence-based escalation
- Usage and cost limits
- Pause and status controls
EVALUATE THE DEPLOYMENT
Review the real deployment— not a generic statement.
A Fonix security review should cover:
Hosting and network architecture
Identity and session controls
Roles and permission design
Company boundaries
Secrets and provider credentials
Backup and restoration responsibilities
Logging and retention
AI provider data flow
Approval and audit paths
Enabled integrations and communication providers
Incident and operational ownership
CONTROL IN PRACTICE
Permissions and approval, working together.
A role defines what a person or agent can see and do within a company context. A human approval gate holds sensitive actions—automated or manual—until an authorized person confirms them.
QUESTIONS, ANSWERED
Frequently asked questions
Does Fonix claim a security certification?
Only independently verified certifications should be displayed. Request the current security and deployment documentation during your evaluation.
Where is Fonix hosted?
Deployment architecture is agreed during solution design. Hosting, data residency, backups, integrations, identity, and operational responsibilities should be reviewed for each deployment.
Is customer data used to train public AI models?
Data handling depends on the selected provider and deployment configuration. Fonix should be evaluated with a documented provider and data-flow review appropriate to your organization.
Can administrators restrict individual AI tools?
Yes. AI employees can be limited through roles, permissions, approved tool lists, autonomy settings, and human approval requirements.
Can activity be reviewed?
Fonix includes audit and activity mechanisms across core operational and AI capabilities. The precise retention and reporting requirements should be agreed during implementation.
