Security best practices: least privilege and secret rotation
Harden your Omnifox workspace with two principles: give every person and key only what it needs, and rotate your credentials regularly.
Watch this step in the video · Security best practices
Why operational security matters
Omnifox brings your conversations, contacts, channel credentials, and API keys together in one place. Applying two simple principles —least privilege (every person or key gets only what it needs) and secret rotation (refreshing credentials regularly)— dramatically limits the damage if an account or key is ever compromised.
This guide is for organization admins who want to harden their workspace.
Before you start
- You need the Administrator role for the organization.
- Have a list of the people who actually use the platform.
- If your plan includes the Audit log (higher tiers), keep it open to review access.
Step 1 — Apply least privilege to roles
- Go to Settings → Workspace members (or Team → Members).
- Review each person and grant the lowest role they need:
Agentfor anyone who only works the inbox,Administratoronly for people who manage billing, channels, or security. - Remember the organization role
memberinherits the permissions of the workspace roleagent— you don't need to grant admin just to let someone handle conversations. - Remove access to workspaces a person doesn't use.
Step 2 — Require two-factor (2FA)
- Open Settings → Security.
- Turn on your own 2FA under Two-step authentication by scanning the QR code with a TOTP app (Google Authenticator, Authy, 1Password).
- Save the recovery codes in a password manager — they're your only way back in if you lose your phone.
- Ask the whole team to enable 2FA.
Step 3 — Rotate your secrets
- API keys: in Settings → API Keys, create each key with a clear name, an expiration date, and only the scopes (
read:contacts,write:messages, etc.) that integration needs. Rotate keys every 60–90 days and revoke any you no longer use. - Webhooks: in Settings → Webhooks, subscribe only to the events you need (
message.received,conversation.created…) and regenerate the secret if you suspect a leak. - Channels: periodically reconnect WhatsApp/Meta tokens via Embedded Signup.
Verify it worked
- No member holds the Administrator role without a reason.
- Every API key has an expiration and narrow scopes.
- Your account and your teammates' show 2FA enabled under Settings → Security.
If it doesn't work
- You don't see API keys or Webhooks: your plan doesn't include
API access. It's available from the Crece plan upward. - You lost both the recovery codes and the phone: another admin must reset your 2FA from Members.
- An integration broke after you rotated a key: update the key in the external tool; the old one is revoked immediately.
Tips
- Treat every API key like a password: one per integration, never shared or pasted into chats.
- Set a quarterly reminder to review members and rotate secrets.
Related articles
Related articles
-
How to enable two-factor authentication (2FA)
Protect your Omnifox account with a second factor from an authenticator app, step by step.
-
Create your own help center for your customers
Publish FAQ articles on a public page with your brand color so your customers can solve their questions without opening a conversation.
-
Data protection and GDPR for companies in the European Union
What Omnifox offers today to help you comply with GDPR: data export and deletion, security, where data is hosted, the data processing agreement (DPA) and what doesn't exist yet.
-
Single sign-on (SSO) with your identity provider (OpenID Connect)
Let your team sign in to Omnifox with their company account from Microsoft Entra ID, Google Workspace, Okta or any other OpenID Connect provider.
-
Settings and security complete guide
Settings and security in depth, in 32 chapters: organization, workspaces, members and roles, teams, hours, SLA, notifications, two-factor authentication, passwords, sessions, IP allowlist, audit and privacy.