The permissions endpoint (GET /api/user/permissions) now reports a top-level places flag, giving you a single, role-accurate signal for whether the current user can work with places.

Places availability used to be indicated only under the admin section. Places launched as an admin-only feature, so the indicator lived there — but the places API has since been opened up to other roles. The new top-level flag reflects access for every role that can use places, so you can decide whether to surface places-related actions without special-casing administrators.

What’s available:

• A top-level places flag on the permissions response — a boolean in the default view, and a per-action object (index, show, create, update, destroy, fork, metadata) when requesting detailed permissions.

{ "permissions": { "places": true } }

The admin-bucket admin.places indicator is deprecated in favour of this top-level flag — see the deprecation notice.