Designer Studio Profile
Studio identity, Matching Profile, qualifications, capacity, Credentials, team relationships, Assignments and network standing.
/admin/designer-network/:idFuture Spec 04 →Current-state summary
Atelier Maison has a substantial Designer Studio Profile with identity, Network Status, Matching Profile, capacity, person-level Designer Profile, Credentials, Assignments and reusable Activity, Notes, Files, Tasks and Communication modules. Performance is a placeholder. Activity and History show the same administrative-access events. The Team tab badge says two while the embedded Teammates grid initially reports zero, and the profile’s Log in to workspace action represents privileged cross-Workspace access without safe terminology or an exposed reason/expiry flow.
Interface inventory
Anatomy and verified behavior
Verification states separate observed behavior from requirements or assumptions.
| Element | Current behavior | Verification |
|---|---|---|
| Identity header | Studio initials, display and legal names, Toronto, update date, Active status and internal slug in the subtitle. | Verified live |
| Actions | Log in to workspace and Change status. | Verified; administrative access not initiated |
| Profile tabs | Overview, Team, Credentials, Assignments, Activity, Notes, Files, Tasks, Communication, Performance and History. | All tabs reviewed |
| Matching Profile | Primary Designer, address, Service Areas, specialties, styles, Project types, budget bands, languages and incomplete social/team/travel fields. | Verified live |
| Capacity and standing | Profile Completeness 100%, Available, next start Aug 31, Capacity 65%, one active Assignment and Demo Administrator Network owner. | Verified live |
| Designer Profiles | Amelia Martin is rendered as a person-level shared-user extension with biography. | Verified live |
| Status transition | Active may transition to Paused, Suspended or Offboarding with required reason and Activity impact preview. | Modal reviewed without confirming |
| Profile editor | Identity, contact, social, address, matching, capacity, primary Designer, visibility and person-level availability/languages/biography. | Full editor reviewed without saving |
User journeys
Current flows
Review Studio readiness
- Open Studio Profile
- Review Matching Profile, Capacity and Credentials
- Review Assignments and Activity
- Identify missing or stale requirements
Change Network Status
- Select Change Status
- Choose allowed transition
- Provide reason
- Review impact
- Confirm
- Write Activity and audit
Administrative Workspace access
- Request access
- Provide reason and support/incident reference
- Use recent authentication
- Start time-limited session with visible banner
- Exit and preserve audit
State model
Current and expected states
Profile and Matchmaking data are available.
Valid transitions appear with reason requirement.
Team badge shows 2 while embedded metrics show zero and table says Loading teammates….
Notes, Tasks, Communication and Performance have empty states.
One Professional Liability Insurance Credential is verified through Dec 31, 2026.
Product rules
Non-negotiable boundaries
- Designer Studio Profile and individual Designer Profile are distinct canonical records.
- Team data comes from Workspace Memberships; badge, metrics and grid use the same authorized query.
- Administrative Access Sessions require authority, reason, recent authentication, narrow scope, expiry, a persistent banner and immutable audit.
- Activity and History have distinct purposes and may not be identical aliases.
- Profile Completeness is explainable and does not itself grant eligibility.
- Network Status transitions execute a governed impact transaction.
Known current limitations · 7 mapped
What is missing, broken or unverified
Future Spec 04 owns closure →- Profile subtitle exposes an internal slug instead of the Studio ID.
- Team badge and embedded Teammate counts conflict.
- Assignments still says Leads & Assignments, Manage brokerage, Shared CRM lead and Open lead.
- Activity and History are duplicates.
- Performance has no snapshots.
- Shared platform connection IDs such as crm-account-am are implementation-facing.
- Administrative access safety controls are not visible.
Future alignment
Required evolution
- 01Adopt the Entity Profile architecture and canonical Studio ID.
- 02Resolve Membership-backed people counts.
- 03Replace legacy Assignment and brokerage language.
- 04Separate Activity from History.
- 05Harden and rename cross-Workspace access.
- 06Connect Projects, reporting and shared modules to canonical records rather than readiness placeholders.
Current baseline
Acceptance record
- All eleven Profile tabs and key Overview fields are inventoried.
- No status, profile or Workspace mutation occurred.
- Privileged access and data-count conflicts are release issues.
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