Who gets a calendar

Status: placeholder. This guide will be written before launch.

Three signup postures cover almost every Pavillion instance: open signup, invite-only, and admin-provisioned. They aren't ranked from worse to better — they trade off curation effort against abuse exposure against growth pace, and the right call depends on what your instance is for.

Planned scope

• Open signup — anyone with an email can apply for a calendar. Lowest friction, highest abuse exposure. Fits public-good instances with active admin attention
• Invite-only — calendars come into existence by invitation from an existing owner or admin. Medium friction, much lower abuse exposure, slower growth. Fits most community-scale instances
• Admin-provisioned — admins create every calendar. Highest friction, near-zero abuse exposure, deliberate growth. Fits org-internal and curated-aggregator instances
• The configuration switch and what each posture looks like operationally
• The application-review path when you run invite-only or open-with-review: what to read in an application, what's a yes, what's a soft no, what's a hard no
• Switching postures later: from open to invite-only is graceful; the reverse takes some communication. The "we're tightening signup because" announcement is its own art
• The "what about bad actors who already have a calendar" question — that's moderation boundaries and removing a calendar territory, not signup