You see "This action is unauthorized." or Access Denied
Laramin refuses an action with a message, or shows a full Access Denied page. Walk through the layers Laramin checks, from workspace membership to the record's business, and fix the one that refuses.
- Applies to
- Core 12.7 and later
- Who can do this
- Administrator, Team member
On this page
Symptom
One of these:
-
A message pops up: This action is unauthorized. or You don't have permission to perform this action. The screen stays where it was, and nothing is changed.
-
A full page: 403 · FORBIDDEN, Access Denied, "You do not have permission to view this page. If you believe this is an error, please contact your administrator.", with Go to dashboard and Switch account.
When Laramin knows which permission was missing, the page also shows Permission, Roles that have it and who can grant it, and it may offer Request access. Note the permission: it tells your administrator exactly what to add.
Check these, in order
Laramin checks these layers in this order. The first one that says no is the one to fix.
1. The person isn't a member of the workspace
Signed in, they see No business yet. Inside an add-on, a record from that workspace may be reported as not existing.
Fix: add them to the workspace. See You see "No business yet" or "Nothing to open here".
2. The role doesn't have the permission
This is the most common cause. Fix: an administrator checks what the person may do, and why:
- With the Roles & Permissions add-on: See why someone can do something, then Change or delete a role or Grant a permission directly.
- To look up a permission's name: Permission key reference.
3. The permission came with an add-on installed later
A role gets an add-on's permissions only if someone adds them. The built-in Administrator role is filled once, when it's created, so an add-on installed afterwards gives administrators none of its permissions.
Fix: a super admin adds the add-on's permissions to the role with Roles & Permissions. Without that add-on, whoever runs the server can run the command below. It resets the Administrator role to Laramin's chosen set, including add-ons installed since, and replaces any changes you made to that role.
Couldn't copy. Select the code and press Ctrl+C (⌘+C on a Mac).
php artisan permission:seed-admin-role --forceSee Super admin vs Administrator.
4. Only super admins may do it
Some areas are kept for super admins, whatever role someone has, such as Addons, Extra Utilities and Developer Tools. Opening them gives Access Denied without naming a permission.
Fix: a super admin does the task. See Super admin vs Administrator for the full list.
5. The role applies in another workspace or team
With Roles & Permissions, a role can apply in one workspace or team only. Some add-ons, such as Property CRM, also let people only read records while All Workspaces is chosen.
Fix: switch to the workspace or team where the role applies. See Switch workspace and Switch team.
6. The permission covers only the person's own records
Some add-ons have "own" permissions, such as Edit Post (Own). People who hold only those may see a list but can't open or change other people's records. For example, Activities answers This action is unauthorized. when they select Claim.
Fix: give the wider permission, or accept that they work on their own records only. See the add-on's article below.
7. The record belongs to another business
Some add-ons check that the record is in the workspace you're working in, and say so, for example "That record belongs to a different business than the one you are working in."
Fix: switch to the record's workspace.
8. It's your own account, or a super admin's
Nobody can reset or set their own password from the Users list: "You can only change your own password from your profile's Password screen." Super admins' accounts are hidden from everyone else.
Fix: use your own profile, or ask another super admin.
9. One action needs two permissions
Some actions check a second permission besides the obvious one. For example, AI Manager's Test Connection also needs the provider's edit permission, and Language's Translation Strings needs its view permission. The add-on articles below say which.
Only in the mobile app or an integration
The message "API access is disabled for your account. Ask an administrator to enable it." means Enable API Access is off for that person. See Someone can't sign in to the mobile app and An API request is refused or returns the wrong thing.
Add-on articles
- You can't open, claim or complete a task (Activities)
- Someone can't see or change Property CRM records (Property CRM)
- You can't give someone a role or permission (Roles & Permissions)
- An AI provider can't be connected or switched on (AI Manager)
- A translation doesn't show (Language)
- Your editors can't open Headless CMS or publish (Headless CMS)
- Writers can't find the Blog, or can't submit or publish (Blog)
Still not working?
Raise a ticket from Support Center in your Laramin app. Include this page's link, the exact message, the Permission if the page showed one, the workspace you were in, and what you were doing.
Thanks. That helps us decide what to write next.
Thanks for telling us what was missing.
You already answered for this article today. Thanks.
We got a lot of answers from your network just now. Try again in a few minutes.
We couldn't send that. Check your connection and try again.
Links in this article
Printed from help.laramin.in. The online article may have changed since.