In this section · 4 articles

Your editors can't open Headless CMS or publish

Someone has no Headless CMS menu, is told they don't have permission, can't publish, or a change to a field never finishes. Find the cause and give them what they need.

Applies to
Headless CMS 1.0 and later
Who can do this
Administrator, Platform owner
Permission
feature.rbac.assignment.edit
On this page

Symptom

One of these:

  • Someone has no Headless CMS menu.
  • They see You don't have permission to do this.
  • Content schemas shows View only — you can't change schemas.
  • The entry editor shows no publish button, and says Save your draft and ask someone who can publish.
  • Moving an entry up or down says Changing the order changes what applications receive, so it needs permission to publish.
  • A change to a field stays on Processing… for many minutes, then fails.

Check these, in order

1. Their role has none of the Headless CMS permissions

This happens even to people with Core's Administrator role. That role gets the permissions of the add-ons that were there when it was first set up. An add-on installed later adds nothing to it. See You see "This action is unauthorized." or Access Denied for how a platform owner can refill it.

Fix: Give the person one of Headless CMS's own roles, or add its permissions to their role:

RoleCan
CMS AdministratorEverything in Headless CMS.
Content PublisherWrite, translate, publish and unpublish entries.
Content EditorWrite and translate entries, but not publish.

See Give someone a role. To check what someone holds, follow See why someone can do something.

2. They have no menu to reach it

The Headless CMS menu is only in the Platform Administration sidebar. Someone who works in another experience, such as Administration, has no menu item for it, even with the right permissions. The screens themselves work for them, for example at https://crm.example.com/admin/hcms/content.

Fix: Add the Headless CMS screens they need to their experience's sidebar with Menu Manager. See Add or change a sidebar item. For menus that are missing in general, see A menu or screen is missing, or the menu is empty.

3. They can write but not publish

Content Editor can't publish, unpublish or change the order of entries. A role may also allow publishing only the entries the person created.

Fix: Give Content Publisher, or Publish on content entries (feature.hcms.entry.publish).

4. They need a permission no standard role gives

These are never part of Core's Administrator role, and must be given one by one, on purpose:

  • Retire a version (feature.hcms.schema.retire_version) and Emergency stop a field (feature.hcms.schema.emergency_stop). They can't be undone for applications that read your content.
  • Remove for good in the trash (feature.hcms.entry.remove). CMS Administrator has it.

Fix: Grant the permission to the person who needs it. See Grant a permission directly.

5. Headless CMS is turned off

While the add-on is off, nobody sees its screens. Fix: a platform owner turns it back on under Addons. See Disable or delete an add-on.

6. A change to a field stays on Processing…

When a field change has to check many entries (more than 500 entries counted once per language), Headless CMS checks them in the background, in its own queue named hcms. If your Laramin queues background work (Connection in Developer Tools › Developer Settings › Queue Settings is Database or Redis) and nothing works through that queue, the field's drawer shows Processing… for 10 minutes or more, then says The entries could not be checked. Nothing was changed. Try again. The field doesn't change, and when you open it again nothing shows that a check is waiting. Your Laramin's scheduled jobs work through the main queue only, not hcms. On Sync, where a new installation starts, the check runs straight away and this doesn't happen.

Fix: Ask whoever runs your server to keep a queue worker running that includes the hcms queue:

Bash
php artisan queue:work --queue=default,hcms

Then make the field change again. For background work in general, see Scheduled jobs don't run.

Still not working?

Raise a ticket from Support Center in your Laramin app. Include this page's link, the person's roles and experience, and the exact message they see.