Workspace Profile
A Workspace-owned organization profile for identity, operations, qualification, branding, integrations and visibility. Uses a settings-style section editor rather than the shared Entity record-tab profile.
/admin/settings/workspace-profileFuture Spec 04 →Current-state summary
Workspace Profile is a Workspace-owned settings experience rather than an Entity record-tab profile. It exposes identity, operations, qualification, branding, integrations and visibility through a dedicated section editor. The live record is private, setup incomplete, version 0 and typed platform admin, with Proper Gallery as its display name. The page promises an immutable snapshot on every save but shows no saved versions. Its settings-style design is intentionally different from Designer Studio, Provider and Client operational profiles.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Readiness header | Version 0, setup incomplete, private and platform admin. | Verified live; terminology correction required |
| Identity | Display/legal name, contact, website and structured address fields. | Verified live |
| Profile sections | Operations, qualification, branding, integrations and visibility are separate sections. | Verified live |
| Version history | Claims every save creates an immutable snapshot; none exist. | Claim visible; persistence unverified |
User journeys
Current flows
Complete Workspace Profile
- Open Profile
- Complete shared identity
- Complete Workspace-type and Category extensions
- Review visibility and branding
- Save draft or publish version
- Project authorized fields to directories and documents
State model
Current and expected states
Current readiness.
Current visibility.
Not evidenced.
Version 0 with no snapshots.
Product rules
Non-negotiable boundaries
- Workspace type uses canonical values such as Registry Administration, Designer Studio, Provider or Client.
- One shared profile is extended by Workspace type and Provider Category.
- Published versions are immutable.
- Visibility is field-aware and permission-scoped.
- Legacy Workspace branding is migrated, not copied forward.
- Workspace Profile intentionally uses the settings-profile design family; operational Entity Profiles continue to use shared record modules and tabs.
Known current limitations · 4 mapped
What is missing, broken or unverified
Future Spec 04 owns closure →- Legacy Proper Gallery name.
- platform admin is implementation language.
- No saved versions.
- Section completeness and public projection were not verified.
Future alignment
Required evolution
- 01Adopt Registry Administration terminology.
- 02Implement draft/publish/version behavior.
- 03Map approved Application fields through stable field keys.
- 04Reuse branding in proposals, presentations and notifications.
Current baseline
Acceptance record
- Workspace type is canonical.
- Version history matches actual persistence.
- Private fields never leak to public or cross-Workspace views.
- Profile mapping is stable across builder versions.
Reverse-spec completeness
Documentation coverage
The interface is still changing, so visual evidence and repository tracing remain intentionally incomplete.
Purpose and user outcome
DocumentedRoles and access
DocumentedRoutes and entry points
DocumentedPage and component anatomy
DocumentedFields and displayed data
DocumentedPrimary actions
DocumentedForms and validation
DocumentedStates and transitions
DocumentedEmpty, loading and error states
DocumentedResponsive behavior
PartialAccessibility behavior
PartialActivity and audit events
PartialData sources and persistence
DocumentedNotifications and automation
PartialKnown defects and limitations
DocumentedReusable component dependencies
DocumentedFuture-spec conflicts
PartialVisual and repository evidence
DeferredAcceptance of current baseline
Documented