An administrator setting that reserves a distinct range of page-IDs per environment — so dev, staging and production never create the same ID, and you can move pages between them safely.

Part of
Type
Back-office
Reserves
Per
Set by
Overview
When a project runs on several servers — dev, staging, production — content created on each gets database IDs. Without coordination, two servers could both create ‘page 42’.
Platform IDs reserve a distinct band of page-IDs per environment, so IDs never collide and you can export/import pages between environments reliably. It’s set up once by an administrator.
Key features
A distinct band of page-IDs per environment so content stays portable across every server.
Each environment gets its own band of page-IDs.
Two servers never create the same id.
Move pages dev → staging → production without conflicts.
Pure configuration, done at setup time.
Only matters in multi-environment workflows.
Invisible to editors; it just keeps moves safe.
See it in action
Reserve a distinct band of page-IDs for each server so content stays portable.

Give each environment a distinct band of IDs so content created anywhere stays portable.
For developers
PlatformController manages the id ranges.
MelisCmsPlatformSelect / MelisCmsPlatformIDsSelect feed BO selects.
It guarantees page export/import (the tree JSON) stays collision-free across servers.
// Page IDs are allocated within the environment's // reserved range, so an exported page tree imports // cleanly on another server without id conflicts.
Part of Melis CMS
Platform IDs are one of the CMS back-office tools — here are the others.
See how multi-environment projects stay collision-free.