feat(profile,nav): Mokosh Role label + Team nav behind runtime feature flag (MAPPS-329) #368

Merged
YousifShkara merged 1 commit from feat/MAPPS-329-mokosh-role-label-team-flag into main 2026-06-26 08:45:02 +02:00
Owner

Two clarifications grouped because they fix the same identity-surface confusion:

Profile identity strip now reads "Mokosh Role: " with a "Bunyip hub role is separate." sub-line. The previous "Role: " against the mokosh-side role (Admin / Manager / Technician) was easy to read as Bunyip-admin too, which it is not; Bunyip's role lives behind Account Settings on the hub.

Team admin nav item is gated on a new runtime_config::flag_enabled("team_enabled") helper that reads window.MOKOSH_CONFIG.team_enabled. Hidden by default; flip MOKOSH_TEAM_ENABLED=true (or =1) on the mokosh-www container to expose it. Route::Team, the Team page, and the API stay intact - typing /team still works - so unlocking is a zero-code flip when the feature is ready. The oci-build/entrypoint.sh emit_field list picks up team_enabled alongside the existing api_base / oidc_issuer fields.

Companion to feat/MAPPS-329-auto-populate-profile-from-bunyip on the mokosh-server side, which stamps profile_completed_at when the Bunyip OIDC claims carry first + last so users no longer hit /onboarding/profile after BUNYIP-206.

#MAPPS-329

Two clarifications grouped because they fix the same identity-surface confusion: Profile identity strip now reads "Mokosh Role: <role>" with a "Bunyip hub role is separate." sub-line. The previous "Role: <role>" against the mokosh-side role (Admin / Manager / Technician) was easy to read as Bunyip-admin too, which it is not; Bunyip's role lives behind Account Settings on the hub. Team admin nav item is gated on a new runtime_config::flag_enabled("team_enabled") helper that reads window.__MOKOSH_CONFIG__.team_enabled. Hidden by default; flip MOKOSH_TEAM_ENABLED=true (or =1) on the mokosh-www container to expose it. Route::Team, the Team page, and the API stay intact - typing /team still works - so unlocking is a zero-code flip when the feature is ready. The oci-build/entrypoint.sh emit_field list picks up team_enabled alongside the existing api_base / oidc_issuer fields. Companion to feat/MAPPS-329-auto-populate-profile-from-bunyip on the mokosh-server side, which stamps profile_completed_at when the Bunyip OIDC claims carry first + last so users no longer hit /onboarding/profile after BUNYIP-206. #MAPPS-329
feat(profile,nav): Mokosh Role label + Team nav behind runtime feature flag (MAPPS-329)
All checks were successful
Check / fmt + clippy + tests (pull_request) Successful in 1m42s
Create release / Create release from merged PR (pull_request) Has been skipped
c7f28c687a
Two clarifications grouped because they fix the same identity-surface confusion:

Profile identity strip now reads "Mokosh Role: <role>" with a "Bunyip hub role is separate." sub-line. The previous "Role: <role>" against the mokosh-side role (Admin / Manager / Technician) was easy to read as Bunyip-admin too, which it is not; Bunyip's role lives behind Account Settings on the hub.

Team admin nav item is gated on a new runtime_config::flag_enabled("team_enabled") helper that reads window.__MOKOSH_CONFIG__.team_enabled. Hidden by default; flip MOKOSH_TEAM_ENABLED=true (or =1) on the mokosh-www container to expose it. Route::Team, the Team page, and the API stay intact - typing /team still works - so unlocking is a zero-code flip when the feature is ready. The oci-build/entrypoint.sh emit_field list picks up team_enabled alongside the existing api_base / oidc_issuer fields.

Companion to feat/MAPPS-329-auto-populate-profile-from-bunyip on the mokosh-server side, which stamps profile_completed_at when the Bunyip OIDC claims carry first + last so users no longer hit /onboarding/profile after BUNYIP-206.

#MAPPS-329
YousifShkara deleted branch feat/MAPPS-329-mokosh-role-label-team-flag 2026-06-26 08:45:02 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
psa-systems/mokosh-apps!368
No description provided.