What problem does it solve? Products built on a Weegloo Space often need their own end-user membership system, separate from the Weegloo platform accounts that own the Space. This Skill guides you through setting up ServiceLogin so end-users can sign up and sign in via OAuth providers, receive Bearer Tokens scoped to ACMA/ACDA/Upload, and get role-based permissions through ServiceUserRole and roleOverride. ## Core Features & Use Cases - End-user OAuth sign-up/sign-in: Configure ServiceLogin with Google, GitHub, Facebook, GitLab, LINE, Kakao, or Naver so anyone can become a ServiceUser of the Space. - Token scoping and permissions: Issue Bearer Tokens valid only for ACMA, ACDA, and Upload, with per-member permission resolution via ServiceLogin.sys.defaultRole and ServiceUser.roleOverride, including createdBy ":self" filters for own-data-only access. - App-store-compliant account deletion: Model member withdrawal as an in-app deletion-request ContentType fulfilled by an admin in the console, satisfying Apple and Google store requirements. - Use Case: You are building a members-only community app on Weegloo. Use this Skill to wire Google sign-in, assign a least-privilege default role so members only touch their own posts, and add an in-app account-deletion request flow. ## Quick Start Set up ServiceLogin for my Weegloo Space with Google sign-in and a default member role restricted to each user's own content.
