0001: Organization overview
A minimal organization entry point for the application foundation
- ID: PRD-0001
- Status: Accepted
- Decision maker: Trevor Gerhardt
- Scope: Concourse application, authentication destinations, and application database
- Product owner: Trevor Gerhardt
- Design owner: Trevor Gerhardt
- Engineering owner: Trevor Gerhardt
- Last reviewed: 2026-09-25
- Related issues or projects: N/A; the owner approved the implementation plan directly.
- Related designs: N/A; this change uses the existing organization layout.
- Related ADRs: Persistence ownership
- Related user documentation: Concourse application
Summary
Give each organization a minimal overview. Remove the unused demo feature and keep the organization foundation ready for future capabilities.
User problem and evidence
The repository owner confirmed that the demo feature was unused and requested its removal. Members still need a valid destination when they open an organization or complete authentication.
Goals and success measures
| Goal | Measure | Target |
|---|---|---|
| Keep organization access usable | Browser acceptance tests | All organization roles can open their overview |
| Remove the unused feature | Schema and route checks | No active demo table, actions, permissions, or interface |
| Preserve the foundation | Integration and acceptance tests | Access, invitations, SSO, audit, and administration checks pass |
Non-goals
- Add another product feature or placeholder data model.
- Preserve demo data or provide a redirect for its removed route.
- Change authentication ownership or permission rules for administration.
Users and use cases
Use case: Open an organization
- Actor: An organization member with any supported role.
- Need: Open the organization after selection or authentication.
- Goal: See the current organization and available navigation.
Requirements
PRD-0001-US-01: Open the organization overview
- Story status: Current
- Replaces: N/A; no earlier story described the demo.
- Replaced by: N/A
- User need: As an organization member, I want a valid entry page, so that I can open my organization.
- Requirement: Use
/organizations/[slug]as the organization entry point. - Done when:
- The overview shows the organization name and accessible Projects from PRD-0003-US-03.
- The Apps tab shows the application list from PRD-0002-US-03.
- Owners and administrators can open Members and SSO. Members and viewers cannot see those navigation links.
- Organization selection and SSO destinations use the overview.
- Unauthenticated visitors must sign in. Nonmembers cannot read the organization page.
- The removed demo route returns not found for an authenticated member.
- The active schema, seed data, permissions, actions, and interface contain no demo feature.
Implementation
The organization overview shows accessible Projects. The Apps tab shows assigned Applications. Sign-in, invitations, SSO, and impersonation use the same organization destination. Browser checks cover these routes. See the Concourse application README for the current interface.
Experience and content
The organization list opens the overview. Its layout shows the organization name, Projects, Apps, and role-controlled administration links. The overview uses the existing organization loading and access-error states. PRD-0002 defines the application list on the Apps tab. PRD-0003 defines the Project landing content.
Constraints and dependencies
Authentication continues to decide organization access. Persistence continues to own storage and audited writes. No Production database exists yet, so one baseline migration replaces the earlier migration history. The first Production deployment applies that baseline to a new, empty database. Unrelated source-database fixtures remain outside scope. Future features need their own requirements.
User documentation
- Audience: Organization members and repository developers.
- Behavior to explain: Open the overview and use the available administration links.
- Agreed terms: Organization, Projects, Apps, Members, SSO.
- Examples or screenshots needed: See the Project documentation requirements.
- Workspace README: Concourse application.
Revision history
- 2026-09-25 — PRD-0001-US-01: Remove the criterion about the demo-removal migration, because one baseline migration replaced the earlier migration history. Replace the delivery notes with a summary of the current implementation, and accept the implemented story. PR #168