What problem does it solve? Building admin UIs or automation against Weegloo requires authenticating a Weegloo platform account (Space owner or invited member), but the platform has two separate identity systems and two token mechanisms, making it easy to pick the wrong login model or mishandle token exchange. ## Core Features & Use Cases - Two authentication mechanisms: Use a Personal Access Token (PAT) for server-side, CI, and script access, or the Weegloo Console FE login popup (origin-checked postMessage to sessionStorage) for browser apps including static sites on Weegloo WebHosting. - Token validation and Space gating: Validate tokens with CMA GET /v1/me and enforce Space membership via /v1/me/space-memberships, reading the nested item.sys.space.sys.id path. - Use Case: You are building a custom admin dashboard deployed as a static site on Weegloo WebHosting. This Skill walks you through opening the console login popup, receiving the access token via postMessage, storing it in sessionStorage, and gating the UI to members of your specific Space. ## Quick Start Implement Weegloo User login for my browser-based admin UI using the console login popup and validate the token against my Space membership.
