Object Levels
Every object has a level field, a number that fixes the object's position in DemandFlow's access and ordering hierarchy. The value is per-entity (e.g. all PPL objects are level 220, all PATENT objects are level 420), comes from the entity's definition, and must be supplied on create.
What level controls
- Visual hierarchy in places that show mixed lists of objects (search, dashboards, audit views), lower-level objects sort before higher-level objects.
- Permission scoping in some workflows, actions that operate "below level X" only touch objects at higher numeric levels.
- Aggregation grouping, analytics that roll up across entities use level to define the rollup boundary.
Where to find an entity's level
The level is fixed in the entity's definition file. The simplest way to discover it for a known entity is to read an existing object of that type:
curl -H "Authorization: Bearer $TOKEN" \
"https://rest.demandflow.com/v1/entities/PPL/SUB" | jq '.[0].level'
# → 220Or read the entity's DEFINITION object and look at the top-level level property.
Common levels
A few examples, for orientation only, your tenant may differ:
| Entity | Level |
|---|---|
PPL (Person) | 220 |
PATENT | 420 |
PATENTA (Patent application) | 430 |
KBPUBLIC (Public KB article) | 52400 |
LINK | 0 |
What to supply on create
Just the number from the entity definition:
{
"entity": "PPL",
"level": 220,
"comboKey": "SUB:<your-sub-id>|ENT:",
"name": "Ada Lovelace"
}Levels generally stay fixed for the lifetime of an object, there's no normal reason to change one with PATCH.