Group members
Group members is one of Demiton's published registers for Australian civil construction. Members of each group in your identity directory. Demiton keeps it current from the systems a contractor already runs and publishes the record's shape as a versioned JSON Schema, so the same question works whichever system produced the record.
Part of Counterparties in the register catalog.
- Register ID
group_membersUse this name to ask for the register. The API calls it a shelf ID.- Each record is
- A stateThe current value of something, replaced when it changes.
- Status
- DeclaredDefined, and fills when a source produces its first record.
- Data
- OrganisationPrivate to each organisation's own workspace.
- Version
- v1 (1.0.3)Current version.
Standards
This register's contract was designed against these standards and laws. Holding these records does not by itself certify compliance.
- Fair Work Act 2009Fair Work Act 2009 - employee records and National Employment Standards
- Privacy Act 1988Privacy Act 1988 - Australian Privacy Principles; employee-records exemption; health information s.6FA
- ISO 30414Human resource management - Requirements and recommendations for human capital reporting and disclosure
- Privacy Act 2020 (NZ)Privacy Act 2020 and Health Information Privacy Code 2020
- UK GDPRUK GDPR and Data Protection Act 2018
Connectors
On the roadmap
Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.
- Mitti
- Oracle Aconex
- PayappsPartial
- SitematePartial
Fields
9 fields: 4 required, 4 optional, 1 defined by each organisation.
Required
Every record carries these fields.
- observed_atDate and time
When this membership state was read from the directory.
Example:
2026-07-01T06:30:00+10:00- group_source_idText
The directory group's own identifier (Graph group object id)
Example:
crew-8101- member_entity_idWhole number
The Demiton canonical worker spine node the membership edge points at (the member)
Example:
5501- member_source_idText
The member's own identifier in the source directory (Graph member
id)Example:
5501
Optional
Present when the source system records them.
- group_kindText
The directory's own group classification.
Example:
project_crew- member_typeText
The directory object type of the member.
Example:
worker- legal_entity_idWhole number
The employing/owning legal entity the membership is scoped to.
- membership_kindText
Whether the edge is a direct membership or a resolved transitive clearance.
Example:
crew_member
Defined by each organisation
Their contents come from the organisation's own forms or systems, so they differ between organisations.
- group_display_nameText
The group's human label as authored in the tenant directory.
Example:
Emerald Street Rejuvenation Crew
Example record
A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.
{ "group_display_name": "Emerald Street Rejuvenation Crew", "group_kind": "project_crew", "group_source_id": "crew-8101", "member_entity_id": 5501, "member_source_id": "5501", "member_type": "worker", "membership_kind": "crew_member", "observed_at": "2026-07-01T06:30:00+10:00", "source_system": "ASSIGNAR"}Use this contract
The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.
https://docs.demiton.io/registers/group_members/v1.jsonShow the full JSON Schema
Loading the schema…
Talk to the team
Tell us what you run - your ERP, field, payroll and document systems - and we will show you the registers Demiton would fill from them, on your data, in a 30-minute call.