Panel 01 · Owner control
Account owner access and oversight
- Approve launch milestones and implementation direction.
- Review delivery status across web, app, and AI workstreams.
- Control internal operational settings tied to your PRIM workspace.
Control room
PRIM Admin Dashboard
Owner control layer for PRIM operations, AI build oversight, website direction, and internal-use privileges.
Admin owner: Clydejames Lynn Scott Jr / CJSCOTT
Admin controls
Owner command grid for PRIM operations
Use these six control areas to manage launch assets, routing decisions, and internal governance without leaving your admin workflow.
Admin privileges
Owner-level PRIM access, clearly scoped for internal control
Structured dashboard permissions for operating your launch system, with clear boundaries on usage and billing scope.
Panel 02 · Internal-use privileges
No-fee owner usage inside PRIM admin experience
- Owner actions performed in this admin environment carry no internal usage fee.
- Applies to internal dashboard operations only, not public platform billing logic.
- Keeps administrative execution efficient while preserving clear commercial boundaries.
Panel 03 · Boundaries
Operational scope for custom builds and AI support
- Custom builds are scoped, approved, and tracked through dashboard-defined deliverables.
- Website capability changes follow project scope, QA flow, and deployment controls.
- AI build support is guided and configured per approved path, without implying account-level billing overrides.
Admin usage notes
Practical answers for owner operations
Use these notes as operating guidance for PRIM delivery and owner-side visibility. They clarify access, request flow, and control boundaries in plain language.
Who is this dashboard intended for?
This view is for the business owner and approved internal operators managing launch progress, requests, and implementation checkpoints with PRIM.
How is owner access represented inside PRIM?
Owner access is shown as a governance role in the workflow, focused on visibility, approvals, and direction rather than deep platform permission rewriting.
How should no-fee owner usage be understood?
No-fee usage is an internal PRIM operating designation for owner collaboration; it does not represent account-level billing overrides or external provider fee-permission changes.
How are AI build requests handled from this admin flow?
AI requests are captured for scoping and routed into the selected path: PRIM on-site AI experience, premium custom agent build, or guided build-your-own planning with Tom.
How do website and custom build controls fit this experience?
The dashboard centralizes intake, scope confirmation, and launch priorities for websites and custom builds while final technical execution is delivered through PRIM workflows.