What problem does it solve? Designing least-privilege access in Weegloo requires knowing exactly which actions, filters, and settings each role type accepts — and mistakes like hard-coding user ids, misusing the self filter, or putting unsupported actions on a ServiceUserRole cause save-time rejections or silent permission gaps. ## Core Features & Use Cases - Permission map design: Defines the contentType, content, media, and script maps with Allow/Deny filter rules (contentType, createdBy, tag, self), including the action subset a ServiceUserRole accepts. - Settings axis guidance: Explains the flat SETTING_* list (Webhook, Locale, Scheduler, EmailAccount, and more) that gates Space configuration, plus the token-type restrictions that apply to it. - Ready-made recipes: Provides patterns for per-user private Content with createdBy: ":self", pinning Script Execute to one specific Script via the self Refer filter, and async external-API job ContentTypes. - Use Case: You want each member of an open sign-up product to read and edit only their own rows. Use this Skill to build a ServiceUserRole with a createdBy.sys.id: ":self" filter scoped to the right ContentType and wire it to ServiceLogin. ## Quick Start Create a Weegloo SpaceRole that lets each user read only the Content entries they created for a given ContentType.