GovOPlaN/govoplan-organizations
2
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases Wiki Activity

Organizations: fix admin settings 500 and decide global vs tenant governance model #4

New Issue
Closed
opened 2026-07-11 03:46:32 +02:00 by zemion · 4 comments
zemion commented 2026-07-11 03:46:32 +02:00
Owner
Copy Link
Copy Source

Context

Opening the Organizations administration/settings entry currently returns 500 Internal Server Error.

The entry has also been confusingly labelled Organization settings. The immediate label was changed to Organizations, but the underlying ownership question remains open.

Questions to resolve

  • Should organization model governance be tenant-local, global, inherited from a global model, or support multiple inherited models?
  • If global organization models exist, how do tenants inherit or override unit types, structures, relation types, and function types?
  • Does tenant-admin customization belong here, or should it be a global/system policy only?
  • What conflict model is needed if different tenants inherit different organization-model versions?

Acceptance criteria

  • Reproduce and fix the 500 when opening the Organizations admin/settings panel.
  • Decide and document the governance scope: global, tenant-local, inherited, or mixed.
  • Rename/position the admin surface so it matches the decided scope.
  • Add regression coverage for the failing admin endpoint.
  • Ensure the UI does not expose tenant-level controls for settings that are actually global-only.
## Context Opening the Organizations administration/settings entry currently returns `500 Internal Server Error`. The entry has also been confusingly labelled **Organization settings**. The immediate label was changed to **Organizations**, but the underlying ownership question remains open. ## Questions to resolve - Should organization model governance be tenant-local, global, inherited from a global model, or support multiple inherited models? - If global organization models exist, how do tenants inherit or override unit types, structures, relation types, and function types? - Does tenant-admin customization belong here, or should it be a global/system policy only? - What conflict model is needed if different tenants inherit different organization-model versions? ## Acceptance criteria - Reproduce and fix the 500 when opening the Organizations admin/settings panel. - Decide and document the governance scope: global, tenant-local, inherited, or mixed. - Rename/position the admin surface so it matches the decided scope. - Add regression coverage for the failing admin endpoint. - Ensure the UI does not expose tenant-level controls for settings that are actually global-only.
zemion commented 2026-07-30 14:37:27 +02:00
Author
Owner
Copy Link
Copy Source

Product decision: governance model accepted

Concrete organization hierarchies are tenant-owned. The system owns versioned organization-model templates, not one mutable live hierarchy inherited by all tenants.

  • A tenant explicitly instantiates a template version into its own hierarchy.
  • Template upgrades are explicit diff/migration operations with preview, provenance, and conflict handling; they never rewrite tenant structures silently.
  • System policy may constrain permitted unit, relation, and function types.
  • Tenant administrators manage concrete units and allowed customizations within that policy.
  • Multiple tenants may remain on different template versions.

This resolves the governance decision. The 500 regression, API ownership, admin placement, and upgrade UX remain implementation work.

## Product decision: governance model accepted Concrete organization hierarchies are tenant-owned. The system owns versioned organization-model templates, not one mutable live hierarchy inherited by all tenants. - A tenant explicitly instantiates a template version into its own hierarchy. - Template upgrades are explicit diff/migration operations with preview, provenance, and conflict handling; they never rewrite tenant structures silently. - System policy may constrain permitted unit, relation, and function types. - Tenant administrators manage concrete units and allowed customizations within that policy. - Multiple tenants may remain on different template versions. This resolves the governance decision. The 500 regression, API ownership, admin placement, and upgrade UX remain implementation work.
zemion added
status
ready
codex/ready and removed
status
needs-info
codex/needs-human labels 2026-07-30 14:37:58 +02:00
zemion commented 2026-07-30 17:46:45 +02:00
Author
Owner
Copy Link
Copy Source

Implemented and pushed in 326bf3f.

The admin/settings route regression is covered and no longer returns 500. The governance model is now explicit: system administrators publish immutable, versioned model templates; tenants instantiate concrete copies with source provenance; tenant models never live-inherit later global changes. Structural validation rejects invalid references, mismatched relation/function types, invalid validity ranges, duplicate relations, and hierarchy cycles.

The admin surface is tenant-appropriate, the model is documented in docs/ORGANIZATION_MODEL.md, and 9 focused settings/template tests pass. Explicit comparison/upgrades from a later template version remain separately tracked in #6.

Implemented and pushed in `326bf3f`. The admin/settings route regression is covered and no longer returns 500. The governance model is now explicit: system administrators publish immutable, versioned model templates; tenants instantiate concrete copies with source provenance; tenant models never live-inherit later global changes. Structural validation rejects invalid references, mismatched relation/function types, invalid validity ranges, duplicate relations, and hierarchy cycles. The admin surface is tenant-appropriate, the model is documented in `docs/ORGANIZATION_MODEL.md`, and 9 focused settings/template tests pass. Explicit comparison/upgrades from a later template version remain separately tracked in #6.
zemion commented 2026-07-30 21:48:55 +02:00
Author
Owner
Copy Link
Copy Source

Codex State: note

Summary

  • Decision confirmed: concrete organization hierarchies are tenant-owned and may be created/upgraded from versioned system templates; tenants do not inherit one mutable live global hierarchy.
## Codex State: note ### Summary - Decision confirmed: concrete organization hierarchies are tenant-owned and may be created/upgraded from versioned system templates; tenants do not inherit one mutable live global hierarchy.
zemion commented 2026-07-30 21:50:05 +02:00
Author
Owner
Copy Link
Copy Source

Codex State: note

Summary

  • Decision confirmed: concrete organization hierarchies are tenant-owned and may be created/upgraded from versioned system templates; tenants do not inherit one mutable live global hierarchy.
## Codex State: note ### Summary - Decision confirmed: concrete organization hierarchies are tenant-owned and may be created/upgraded from versioned system templates; tenants do not inherit one mutable live global hierarchy.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
HTTP API contracts, routers, schemas, or API smoke behavior.
 area/auth
Authentication, sessions, access bootstrap, or login behavior.
 area/db
Database sessions, models, transactions, or persistence primitives.
 area/devex
Local developer workflow, scripts, tests, tooling, or release helpers.
 area/docs
Durable documentation and project guidance.
 area/governance
Governance policy, audit, privacy, retention, or compliance behavior.
 area/marketing
Public website, product messaging, publication copy, or legal page content.
 area/migrations
Alembic migrations, schema bootstrap, or persistence evolution.
 area/module-system
Module discovery, manifests, capabilities, routing, or optional integrations.
 area/rbac
Permissions, roles, delegation, or authorization policy.
 area/release
Versioning, release locks, tags, packaging, or dependency pins.
 area/security
Security posture, static analysis, supply-chain hardening, or vulnerability remediation.
 area/tenancy
Tenant boundaries, provisioning, or tenant-scoped data behavior.
 area/webui
Shared WebUI shell, frontend components, routing, or frontend tests.
 audit/complexity
Complexity finding from Radon, Xenon, or equivalent maintainability scans.
 audit/duplication
Duplicated-code finding from jscpd or equivalent similarity scans.
 audit/false-positive
Audit finding reviewed as a narrow false positive or acceptable risk.
 audit/needs-design
Audit finding that needs an architectural or product decision before implementation.
 audit/quick-fix
Audit finding that appears narrow and directly fixable.
 audit/structural
Audit finding that needs design, refactoring, or behavior review.
 codex/needs-human
Needs an explicit human decision before Codex should implement.
 codex/ready
Suitable for Codex to pick up with the existing issue context.
 module/access
GovOPlaN access, identity, authentication, RBAC, and administration behavior.
 module/addresses
GovOPlaN Addresses module behavior or integration.
 module/admin
GovOPlaN Admin module behavior or integration.
 module/appointments
GovOPlaN Appointments module behavior or integration.
 module/approvals
GovOPlaN Approvals module behavior or integration.
 module/audit
GovOPlaN Audit module behavior or integration.
 module/calendar
GovOPlaN Calendar module behavior or integration.
 module/campaign
GovOPlaN campaign module behavior or integration.
 module/cases
GovOPlaN Cases module behavior or integration.
 module/committee
GovOPlaN Committee module behavior or integration.
 module/connectors
GovOPlaN Connectors module behavior or integration.
 module/core
GovOPlaN core runner, shared primitives, shell, or extension points.
 module/dashboard
GovOPlaN Dashboard module behavior or integration.
 module/dataflow
GovOPlaN Dataflow module behavior or integration.
 module/datasources
GovOPlaN governed datasource contracts, catalogs, and integrations.
 module/decisions
GovOPlaN formal Decisions module behavior or integration.
 module/dist-lists
GovOPlaN Distribution Lists module behavior or integration.
 module/dms
GovOPlaN Dms module behavior or integration.
 module/docs
GovOPlaN Docs module behavior or integration.
 module/encryption
GovOPlaN Encryption key custody, cryptographic policy, and E2EE integration.
 module/erp
GovOPlaN Erp module behavior or integration.
 module/evaluation
GovOPlaN Evaluation module behavior or integration.
 module/files
GovOPlaN files module behavior or integration.
 module/fit-connect
GovOPlaN Fit Connect module behavior or integration.
 module/forms
GovOPlaN Forms module behavior or integration.
 module/forms-runtime
GovOPlaN Forms Runtime module behavior or integration.
 module/helpdesk
GovOPlaN Helpdesk module behavior or integration.
 module/identity
GovOPlaN Identity module behavior or integration.
 module/identity-trust
GovOPlaN Identity Trust module behavior or integration.
 module/idm
GovOPlaN Idm module behavior or integration.
 module/ledger
GovOPlaN Ledger module behavior or integration.
 module/mail
GovOPlaN mail module behavior or integration.
 module/mandates
GovOPlaN Mandates, jurisdiction, responsibility, and authority behavior or integration.
 module/notifications
GovOPlaN Notifications module behavior or integration.
 module/ops
GovOPlaN Ops module behavior or integration.
 module/organizations
GovOPlaN Organizations module behavior or integration.
 module/parties
GovOPlaN procedure Parties, representation, and delivery-authority behavior or integration.
 module/payments
GovOPlaN Payments module behavior or integration.
 module/permits
GovOPlaN Permits module behavior or integration.
 module/policy
GovOPlaN Policy module behavior or integration.
 module/poll
GovOPlaN Poll module behavior or integration.
 module/portal
GovOPlaN Portal module behavior or integration.
 module/postbox
GovOPlaN Postbox module behavior or integration.
 module/projects
GovOPlaN Projects module behavior or integration.
 module/quick-access
GovOPlaN configurable task-local Quick Access behavior and integrations.
 module/records
GovOPlaN Records and eAkte lifecycle behavior or integration.
 module/reporting
GovOPlaN Reporting module behavior or integration.
 module/risk-compliance
GovOPlaN Risk Compliance module behavior or integration.
 module/scheduling
GovOPlaN Scheduling module behavior or integration.
 module/search
GovOPlaN Search module behavior or integration.
 module/services
GovOPlaN versioned institutional Services behavior or integration.
 module/tasks
GovOPlaN Tasks module behavior or integration.
 module/templates
GovOPlaN Templates module behavior or integration.
 module/tenancy
GovOPlaN Tenancy module behavior or integration.
 module/tickets
GovOPlaN Tickets module behavior or integration.
 module/views
GovOPlaN governed task views, interface projections, and workflow view integration.
 module/voting
GovOPlaN Voting module behavior or integration.
 module/wiki
GovOPlaN Wiki module behavior or integration.
 module/workflow
GovOPlaN Workflow module behavior or integration.
 module/workflow-engine
GovOPlaN Workflow Engine runtime, persistence, or integration.
 module/xoev
GovOPlaN Xoev module behavior or integration.
 module/xrechnung
GovOPlaN Xrechnung module behavior or integration.
 module/xta-osci
GovOPlaN Xta Osci module behavior or integration.
priority
p0
Immediate stop-the-line priority.
priority
p1
High priority for the next focused work window.
priority
p2
Normal planned priority.
priority
p3
Low priority or opportunistic cleanup.
source/backlog-import
Imported from markdown backlog, roadmap, plan, or TODO files.
 source/security-audit
Created from a structured security or code-quality audit report.
 source/todo-scan
Imported from inline TODO/FIXME/HACK markers by the Gitea TODO importer.
status
blocked
Cannot progress without a decision, dependency, credential, or external change.
status
in-progress
Currently being worked.
status
needs-info
Needs clarifying input before implementation can proceed safely.
status
ready
Ready for implementation.
status
triage
Needs review, ownership, priority, or acceptance criteria.
type
bug
A reproducible defect, regression, or incorrect behavior.
type
debt
Cleanup, refactoring, risk reduction, or deferred engineering work.
type
docs
Documentation, process, or developer workflow work.
type
feature
New user-visible behavior or platform capability.
type
task
Implementation, maintenance, migration, or operational work.
type
user-story
End-to-end user journey or real-world process story used to steer product slices.
No labels area/governance area/tenancy codex/ready module/organizations
priority
p1
status
ready
type
bug
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
govoplan-package-publisher zemion (Albrecht Degering)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: GovOPlaN/govoplan-organizations#4