Control and connections
Protect access and business data
Use safe sign-in, permissions, approval, credentials, audit history, and production controls.
10 min read · Written for business teamsSecurity in Acerite is a set of everyday business controls: each person has their own account, access matches responsibility, sensitive settings need authority, and important actions leave a record.
The organization reduces the chance of unauthorized replies, exposed credentials, cross-location data access, or untraceable changes.
Every user, with additional responsibility for owners, administrators, security teams, and IT.
Security habits for every team member
- Use your own account and never share passwords.
- Enable multi-factor authentication when available.
- Review active sessions and sign out unfamiliar devices.
- Do not copy customer information into unapproved tools.
- Report unexpected access, replies, or settings immediately.
Separate viewing, approval, and control
Why this matters: A person who needs to read location reports does not automatically need authority to connect providers, invite administrators, or publish replies.
Assign the smallest access needed for the job. High-impact actions should remain limited to named roles, and sensitive automation should have a clear owner who reviews exceptions and failed work.
Protect connected-service credentials
- Enter credentials only in the authenticated Acerite connection form.
- Do not send passwords, API keys, recovery codes, or tokens in chat or email.
- Replace a credential immediately if it may have been exposed.
- Remove access when a provider or integration is no longer used.
Control important production changes
Major data or platform changes should have a verified backup, tested change plan, health check, and recovery path. AI and integration activation should separately confirm credentials, permission, budget, and feature policy.