User can't access a workspace: insufficient permissions
Steps to fix the insufficient-permissions error when a user belongs to the organization but can't enter a workspace or doesn't see the modules they should.
Watch this step in the video · Workspace members
A very common case: you invited someone, they're inside the organization, but they can't enter a workspace — or they get in and the sidebar is almost empty. It's nearly always about where and with which role they were added. This guide walks you through it.
The usual cause: org member ≠ workspace member
Omnifox has two levels of membership:
- Organization — the company's global account.
- Workspace — each work space inside that organization.
Being in the organization does not grant automatic access to every workspace. The person must be added to the specific workspace, with a role that gives them at least conversations.view or whichever module they need.
Steps to fix it
- Go to Settings → Workspace members (with the correct workspace active in the top bar).
- Look for the person in the list. Not there? Click Add member, pick them from the organization members, and assign a role (Agent or Admin).
- If they are listed but access is limited, check the role column: an organization
memberrole inherits Agent permissions in the workspace; if they need more, bump them to Admin or use a Custom role with the exact permissions. - Confirm the module they're asking about has its
viewpermission: no Reports means missingreports.view; no Contacts means missingcontacts.view, and so on. - Make sure the member isn't deactivated (shown with a "Deactivated" tag). If they are, reactivate them.
Verify
Ask the person to sign out and back in, or reload. They should be able to select the workspace from the top bar and see modules according to their role. The sidebar is recomputed on load, based on their permissions.
If it still doesn't work
- Gets into the workspace but the menu is empty: their role has almost no
viewpermissions; review the role (especially a Custom role with nothing ticked). - Can't even select the workspace: they aren't added to that workspace — go back to step 2.
- Sees the module but can't edit: they have
view, missingmanage(see the granular permissions article). - Billing locked:
billing.manageis Owner-only — that's expected. - Asked for a code on sign-in: that's not a permissions issue, it's two-factor authentication (2FA); they need to complete their code.
Tip: to invite a brand-new person to the company, first go to Settings → Workspace members (organization), then add them to the workspace.
Tip: when in doubt, apply least privilege — give the Agent role and raise permissions only if they ask.
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.