SDGS PASS provides free participation in the EMJ.NEXUS ecosystem for students, employees and general consumers through one Personal registration route. Enterprises are excluded from this free individual-participation scope.
Applicable tasks, roles, permissions and participation conditions remain governed within their relevant contexts. Enterprise or institutional affiliation does not create a separate SDGS PASS registration route.
Eligible Participation Events may connect to a governed event-data architecture under applicable rules.
SDGS PASS offers free participation in the EMJ.NEXUS ecosystem for students, employees and general consumers. All three roles use the same Personal registration route. Enterprises are excluded from this free individual-participation scope. Registration, authorization and access remain subject to the rules of the relevant participation environment.
SDGS PASS · Personal registration
Personal
One registration route for all applicable SDGS PASS participant roles.
An employee’s organizational affiliation may affect applicable authorization, role and task access; the participant still registers as an individual through Personal.
28 September 2026 · ActiveStudent Personal route24 October 2026 · ScheduledInvited employee Personal route10 November 2026 · ScheduledGeneral public Personal route
Only the verified Student Personal boundary is active. Later dates remain subject to separate identity, authorization, eligibility, role, permission, task, verification and operational controls.
02
Participation contexts
Who Participation Serves
Participation may occur through applicable tasks, roles, activities and programs within verified organizational or education contexts.
01
Students
Applicable learning, project, community and task-based participation through the Personal route.
02
Employees
Applicable workplace, organizational, community and event participation through the Personal route.
03
General consumers
Applicable public, community, volunteering and event-based participation through the Personal route, subject to the scheduled general-public access phase.
03
Record formation
From task participation to a governed Participation Event.
A Participation Event records applicable task, participant role, time, verification status and control information within the relevant participation context.
Eligible events may be connected to a governed evidence architecture under applicable rules.
A Participation Event is a governed participation record.
It is not, by itself, proof of outcome, certification, assurance, compliance or sustainability performance.
After UID issuance, completion of the full SDG 1 through SDG 17 assessment pathway creates a one-time award of 170 IPP Points and 170 IPP Score. Fewer than 17 completed assessments creates no partial award.
A task claim deducts T IPP Points. Verified approval awards 2T IPP Points and adds T IPP Score.
At each annual platform cycle, the IPP Points balance resets to max(170, min(10% of the balance immediately before reset, 500)). IPP Score does not reset.
IPP Points and IPP Score are not money, securities, carbon credits, carbon offsets, tradable assets, external assurance, certification or sustainability-performance conclusions.
05
Participation governance
Participation is governed, not certified.
PASS is a participation-gateway identity. The term PASS does not represent a certification, examination result, compliance determination, assurance conclusion, rating or pass/fail status.
SDGS PASS supports governed participation through applicable roles, permissions and data boundaries.
Participation may preserve
Applicable task participation
Applicable participant role
Relevant event time
Applicable verification status
Applicable control information
Participation does not itself determine
Performance outcome
Certification or assurance
Compliance or rating
Carbon credit or carbon offset
Financial or investment outcome
Governance notice
Participation remains bounded by role, permission and context.
SDGS PASS uses one Personal registration route across applicable participant roles. Shared architecture does not create unrestricted data visibility, unrestricted data sharing, cross-role access or unrestricted cross-context use. Any subsequent use remains subject to applicable rules, permissions, data boundaries and responsible-party judgment.