Content statuses

In BCMS, content statuses let you tag entries with labels like draft, published, or in-review. They help structure your content lifecycle without enforcing strict publishing rules.

Only one status can be applied to an entry at a time.


How content statuses work

  • Only Admins can define statuses - that is, create or delete them globally from the dropdown menu in any entry.

  • All users who have edit access to an entry can change its status, selecting from the list of statuses created by an admin.

  • Statuses are purely informational and don’t affect your data unless you handle them in your code.

BCMS keeps content statuses lightweight and flexible—great for teams who want control without unnecessary complexity.


Example use cases

  • draft — Content in progress

  • review — Awaiting internal or external approval

  • ready — Ready for publishing or deployment

  • published — Final, live content

  • archived — Old or retired content not shown in UI


Setting a status

  1. Open an entry in the BCMS dashboard.

  2. In the top-right corner, find the Status dropdown.

  3. Select a status.

Admins will also see the Edit Statuses option in the dropdown, which allows them to add, rename, or delete global statuses.


Using statuses in code

Each entry includes a status field:

entry.statuses[0]?.label; // e.g. "Published"

You can get all entries with a specific status like this:

async function getPublishedBlogPosts() {
  const entries = await bcms.entry.getAllByStatus('blog', 'Published');
  console.log(entries);
}

Notes

  • The second argument ('Published', 'Draft', etc.) can be a status ID or label.

  • The first argument ('blog') is the template name or ID.

  • getAllByStatus returns parsed entries, ideal for frontend use.

  • getAllRawByStatus returns raw BCMS entries, useful for deeper system-level work.


Why use statuses

  • Keeping status management centralized (admin-only) avoids confusion and accidental clutter.

  • Letting all users with entry access change status keeps your workflow fast and flexible.

  • Supporting only one status per entry keeps your logic clean - no need to check arrays or toggle combinations.

BCMS balances control and usability: Admins define the system, contributors move the content forward.