District CompanionV3.2.3 PILOT · MULTI-CONSTITUTION
Connect Supabase
Edit config.js with your project URL and public publishable key. See the setup guide.
Member access
Sign in with your email. New accounts are held for membership approval.
Reset your password
Enter your account email and we’ll send a recovery link if an account is eligible.
Choose a new password
Enter a new password for your District Companion account.
Membership approval required
Your account is signed in, but has no approved Lodge / District membership. An authorised administrator must assign and approve your membership before you can see schedules.
Your approved meeting network
District Calendar
My Memberships
Your approved memberships appear in your combined calendar. Request another Lodge, Chapter, Conclave, Council, Preceptory or Priory here.
Platform administrator only
Member approvals & permissions
Only verified member accounts should receive Lodge access. Changes are logged.
Requests for additional memberships
Assign another membership
Awaiting first approval
Current memberships
Constitutions, Districts & Orders
Platform administrators only. Existing governing assignments cannot be changed through this form.
District management
Add a District under a Constitution, or remove an unused District. Districts with linked records cannot be removed.
Lodge & Appendant Body Management
Add or edit a Lodge, Chapter, Council, Preceptory or Priory. Removal is blocked if meetings, memberships or other records still depend on that body.
Craft Lodges
Appendant Bodies
Other Bodies
Create or edit a body
Member Activity & Audit History
Read-only audit history for Platform Administrators. Records are preserved after membership cleanup.
Member Invitations & Onboarding
Platform Administrators only. Create multiple invitations for the same email, one per body. Copy and send the invitation message manually; no automated email is sent.
Invitation tracking
My Invitations
Sign in using your verified invitation email. Accept each invitation; an administrator must still approve it.
This pilot uses secure Supabase sign-in and database-level meeting permissions. Push notifications, private documents and self-service access requests require administrator approval.
