Google Draw Collaborative Diagramming Workspace Architecture

Tech architecture infographic titled "Collaborative Diagramming Workspace Architecture" — SYSTEM ARCHITECTURE. Create an executive-deck-grade interface mockup for a tech / SaaS company, inspired by a collaborative diagram editor, shown as a photorealistic modern dashboard screen. Use a clean central workspace UI with labeled boxes connected by directional arrows. Include these components as clear boxes with icons, names, and one-line role descriptions in English: 1) User Browser — "Web Client" — "Runs the diagram editor UI and sends user actions over HTTPS"; 2) Main Canvas — "Diagram Canvas" — "Interactive workspace for creating and arranging shapes and connectors"; 3) Left Panel — "Shape Library" — "Provides reusable shapes, icons, and templates for diagram building"; 4) Collaboration Service — "Realtime Collaboration Layer" — "Synchronizes edits, cursors, and comments between active users"; 5) API Layer — "Application API" — "Handles document operations, sharing settings, exports, and project metadata"; 6) Auth Module — "User Permissions" — "Enforces authentication, roles, access scopes, and edit/view rights"; 7) Storage Layer — "Cloud Document Storage" — "Persists diagram files, version history, and metadata"; 8) Versioning Module — "Revision History" — "Tracks document changes and supports restore points"; 9) Export Engine — "Export Tools" — "Generates PNG, SVG, PDF, and shareable outputs"; 10) Sharing Module — "Sharing Workflow" — "Creates links, invitations, and permission-based collaboration access"; 11) Notification Layer — "Comments & Notifications" — "Delivers mentions, comments, and activity updates"; 12) Generic Cloud Edge — "Web Delivery Layer" — "Serves static assets and routes secure client requests". Show arrows with short English labels such as: "HTTPS UI request", "shape drag event", "canvas state update", "REST API call", "JWT token", "permission check", "document JSON", "version snapshot", "WebSocket sync", "comment event", "export job", "PNG/PDF/SVG file", "share link", "access policy", "metadata read/write". Ensure flow is technically accurate: Web Client connects to Web Delivery Layer over HTTPS; Web Client exchanges REST API calls with Application API; Web Client and Realtime Collaboration Layer use WebSocket sync for live collaboration; Application API validates JWT token with User Permissions; Application API reads/writes document JSON and metadata to Cloud Document Storage; Revision History stores version snapshots from API or collaboration commits; Sharing Workflow checks access policy through User Permissions and issues share links; Export Tools pulls diagram data from storage through API and returns PNG, SVG, or PDF output; Comments & Notifications receives comment events and collaboration activity. Add a numbered legend 1-7 in English: 1. User opens the editor in the browser over HTTPS. 2. The canvas loads shapes, templates, and existing document JSON. 3. User actions are sent to the API and reflected on the canvas. 4. Realtime collaboration broadcasts edits through WebSocket sync to other viewers. 5. Permissions and sharing rules are validated before access is granted. 6. Diagram changes are saved to cloud storage with revision history snapshots. 7. The finished diagram is exported or published through a share link. Visual style: modern dashboard, ultra-clean UI composition, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout, photorealistic screen presentation, executive presentation polish. Color palette: tech blue and cyan with white, soft gray, subtle glass panels, crisp contrast, gentle shadows, premium SaaS mood, precise spacing, neat grid alignment. Use generic branding only, inspired by collaborative cloud diagramming but with no trademarked interface details. All text rendered cleanly in English, no spelling errors, no gibberish characters, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real-company logos. Use generic icons for departments / tools / vendors. Org-chart titles stay neutral (no real person names). Process timings / costs / volumes are illustrative example values.