Access and privacy
Public overview outside. Team workspace inside.
Launch Craft should be easy to understand from the outside without revealing the real work inside. The public website is intentionally limited. Approved staff sign in for detailed learning, source notes, and operating material.
Privacy promise
The public layer shares only the broad purpose. The private layer holds the real staff learning, source notes, and team-only workspace.
Approved staff only
Launch Craft is designed for known Multisystems users and invited team members.
Private workspace
Internal records, detailed lessons, and product-specific material are not published on the public website.
Reviewed sources
Public repositories and documents are treated as source material, then reviewed before becoming staff guidance.
Role awareness
Staff should see what matches their role, responsibility, and approved product access.
Launch checklist
Privacy rules the team can understand.
The site should make the boundary obvious: public pages are broad and safe; internal pages are specific and protected.
The public site explains purpose without exposing internal work.
Team members sign in before viewing detailed lessons or operating records.
Source material is handled as evidence, not automatic instruction.
Access can expand by role, review, and team approval.
Private workspace data should not be cached or indexed publicly.
Production domains and access settings should be reviewed before launch.