Granular per-module permissions (view vs. manage) and custom roles

Learn the difference between view and manage permissions for each Omnifox module, and how to build custom roles that grant exactly the access each person needs.

Jun 26, 2026

Watch this step in the video · Organization roles

In Omnifox, access is controlled per module and per permission level. The rule is simple: almost every module has two levels, view and manage. Getting that distinction right is the foundation for handing out access without over- or under-exposing anything.

View vs. manage: what each level does

  • view lets someone open and read a module, but change nothing. For example, contacts.view shows the contact list; reports.view opens the reports.
  • manage adds create, edit and delete inside that module. contacts.manage lets a user edit and delete contacts; channels.manage lets them connect or reconfigure channels.

If a person doesn't even hold the view permission for a module, that module won't appear in the sidebar (the rail filters every icon by permission). So when someone says they "can't see" Reports or Contacts, it's almost always a missing *.view.

Built-in roles

Every member has a per-workspace role that ships with a permission set:

  • Owner — full access (the * wildcard), including billing.
  • Admin — everything except billing.manage (billing is Owner-only).
  • Supervisor — mostly read: sees reports, audit log, contacts, conversations, templates; manages snippets and the calendar.
  • Agent — the operational set: conversations (conversations.view/write), contacts, snippets, templates and calendar.

At the organization level there are also scoped roles: Billing Admin (billing only) and User Admin (member management only).

Create a custom role

When none of the presets fit, use the Custom role to switch permissions on one by one.

  1. Go to Settings → Workspace members (organization) or Settings → Workspace members for per-space access.
  2. Open the person's row and switch their role to Custom.
  3. Tick the exact permissions they need, module by module: e.g. conversations.view + conversations.write so they can handle chats, but without contacts.manage if you don't want them editing the customer record.
  4. Save. Changes apply on the next render — the sidebar recalculates immediately.

Verify

Ask the person to reload Omnifox and check the sidebar: only modules where they hold at least view should appear. If in doubt, sign in as that person (or ask for a screenshot) and confirm they can see but not edit where appropriate.

If it doesn't work

  • Change not reflected: ask them to reload; the rail is computed on load.
  • Sees the module but can't edit: they have view but are missing manage.
  • Billing locked: billing.manage is Owner-exclusive — not even Admin has it.
  • Org role vs. workspace role: a person can be a member in the organization but still needs a workspace role to enter that space.

Tip: follow least privilege. Start with view and add manage only where the person genuinely needs to change things.

Tip: for larger teams, define a "template" custom role per function (sales, support, supervision) and reuse it when onboarding each member.

Related articles

Was this helpful?

Related articles

Message us on WhatsApp