Resolving Shared Inbox Permission Issues
If agents see access‑denied messages or missing tickets, the cause is usually a permission mismatch. This guide shows how to confirm and fix each common issue.
On this page
When a teammate opens the shared inbox and sees an “Access denied” message or cannot view tickets that should be visible, the problem is usually a permission mismatch rather than a system outage. Start by reproducing the exact symptom: note which user, which mailbox, and what action triggers the error. That information narrows the cause quickly.
1. Incorrect team member role
How to confirm
- Open the team settings page and locate the affected user.
- Verify the assigned role (admin, agent, viewer). Only admin and agent roles grant full ticket access in a shared inbox.
- Check whether the user was added to the correct team; a user can belong to multiple teams but only inherits permissions for the team they are viewing.
How to fix
- Change the role to “Agent” or “Admin” for the relevant team.
- Save the change and ask the user to refresh the browser.
- If the user needs limited access, keep them as “Viewer” and create a separate shared inbox for the tickets they should see.
2. Email forwarding or alias misconfiguration
How to confirm
- Go to the email‑to‑ticket settings for the shared inbox.
- Confirm that the forwarding address (for example, support@yourdomain.com) points to the inbound address provided by your help desk, not to a personal mailbox.
- Send a test email from an external address and watch whether a ticket appears in the shared inbox or stays in the personal inbox.
How to fix
- Update the forwarding rule in your email provider (Google Workspace, Microsoft 365, etc.) to use the inbound address.
- Remove any duplicate forwarding rules that send copies to individual accounts.
- Run the test email again; the ticket should now appear in the shared inbox with the correct permissions.
3. Browser cache, cookies, or stale session data
How to confirm
- Open the shared inbox in an incognito or private window.
- Log in with the same credentials; if the tickets appear, the issue is local browser data.
- Alternatively, try a different browser or device.
How to fix
- Clear cache and cookies for the help desk domain.
- Log out completely, close the browser, then log back in.
- If the problem persists, check for browser extensions that block scripts or modify headers; disable them temporarily.
4. Missing or revoked API token for automated processes
How to confirm
- If you use a script, chatbot, or external service to create tickets, open the integrations page and verify the API token status.
- Look for “Token expired” or “Revoked” flags.
- Test the integration by triggering a ticket creation manually.
How to fix
- Generate a new API token from the integrations settings.
- Update the external service with the new token.
- Run a test ticket creation; the ticket should appear in the shared inbox with the correct assignee permissions.
5. Plan‑level limits or feature restrictions
How to confirm
- Review the current plan details in the billing section.
- Verify whether the plan restricts the number of shared inboxes, team members, or ticket visibility rules.
- Compare with the feature matrix for free and paid tiers.
How to fix
- If the limit is reached, consolidate mailboxes or remove unused teams.
- For higher limits, upgrade to the flat‑rate plan (no per‑agent fees).
What to do if nothing worked
- Collect the following details: affected user email, exact error text, steps to reproduce, browser version, and any recent changes to team or email settings.
- Open a support ticket from the dashboard (use the “Help” menu).
- Attach screenshots of the permission settings and the error message.
- Support can inspect server‑side logs for denied‑access events that are not visible in the UI.
If permission problems persist, try NeuraDesk free to see a shared inbox that handles access automatically. try NeuraDesk free
Join teams already using NeuraDesk
Ready to get started?
Create your workspace and try NeuraDesk for free.
Sign up free