COURTS & COVENANT / OWNER HANDOFF

Your community.
You’re ready to lead.

This is your guide to setting up the group, making it your own, and handing it to the next leader. You run the group through Admin; members use their own accounts to join games and connect.

01 / Set up your owner account

Start here
  1. Open Account, create an account with your own email address, and verify the email. If you already have an account, sign in.
  2. If the group already exists, ask its current owner for an invitation. Accept it in Account → Join an invited group. The current owner can then use Admin → Transfer group ownership to make you the owner.
  3. If this is a new group, choose Account → I’m starting a new group. The account that creates it becomes its owner and admin. Start with one group; don’t create a replacement each time you sign in.
  4. Confirm your sidebar says Group owner. When you belong to multiple groups, choose the right group in the top bar before editing.

Nobody needs your password. Each person signs in separately. Keep your Cloudflare and Supabase hosting accounts with the technical maintainer; group ownership does not grant infrastructure access.

02 / Make the group yours

Identity & welcome

Open Admin → Edit site content. Set the group name, welcome line, home headline, home description, Scripture and reference, reflection prompt, owner help text, footer and accent color.

These settings apply to the selected invited group after sign-in. The public welcome screen keeps the Courts & Covenant identity.

Courts & first game

Open Courts → Add court. Enter the real name, address and court type. Then open Games & Events → Add game and set the title, date, time, duration, court, capacity, skill level, host and meeting notes.

Overlapping games on the same court are blocked. Capacity cannot be reduced below the current RSVP count.

03 / Invite the people

  1. Open Members → Invite a member and enter that person’s exact email.
  2. Copy the personal invitation code and send it to that person along with the community link. Invitations expire after seven days; create a fresh code when needed.
  3. They create or sign into their own account, verify their email, then paste the code into Account → Join an invited group.
  4. Ask them to open Members → Edit profile to save their name and skill level. Test with one member before inviting the whole group.
  5. For a trusted co-leader, the owner chooses Members → Make admin. Admins can edit all shared group content. Only the owner can assign or remove admin roles.

Invitation creation displays a code; it does not automatically send an email or message.

04 / What can I edit?

AreaOwner / adminMember
Group identity, welcome, Scripture, footer, colorEdit in Admin → Site contentRead group settings
Courts, games, announcements, matches, plansAdd, edit, removeRead; join or leave games
Shared prayers, reflections, follow-ups, messagesAdd, edit, remove all shared entriesAdd; edit or remove their own entries
Private prayers / reflections / follow-upsOnly their own private entriesOnly their own private entries
Member name and skill levelEdit any group profileEdit their own profile
Invitations and complete group backupCreate invitations; export accessible group dataAccept personal invitations
Admin roles and ownership transferOwner onlyNo access

Shared entries explicitly disclose that admins can edit them. An admin cannot read someone else’s private entry or change its visibility. Avoid confidential pastoral, medical or counseling details in group posts.

05 / Your first-session checklist

0 of 7 ready

Check these on your device as you complete the launch. The checklist stays in this browser; it is not shared with members.

06 / Run it week to week

Before each gathering

Check the schedule and capacity, update meeting notes, and post an announcement. Members click Refresh to load your changes. This is a shared workspace with manual refresh, not a live chat or push notification service.

Keep a backup

Use Admin → Export group backup before major changes and at handoff. It includes group settings, roster and accessible records. Downloaded backups contain personal information; store them securely. Automatic restore/import is not provided—ask the technical maintainer for recovery.

Hand it to the next owner

Invite the new owner as a member, have them accept, then choose Admin → Transfer group ownership. Select the existing member and confirm. They gain owner control; you remain an admin. Ask the new owner to verify their role in their own browser.

Previous demo data

The previous local demo remains available for exports on the same browser. Its data is not group data and does not synchronize. Export and review those records before asking a maintainer to migrate them.

If something gets stuck

I don’t see Admin

Check that you selected the correct group. The owner can grant admin access under Members. If starting a new group, the account that creates it is its owner.

An invitation is rejected

Sign in with the exact invited email. Confirm the email is verified and the code is complete. Ask an admin for a fresh code if it expired or was already accepted.

An edit says “changed—refresh first”

Another person saved a newer version. Copy your unsaved text, close the editor, click Refresh, then reopen the current entry and apply your edit.

My email or reset link never arrives

Check spam. Ask the technical maintainer to verify email delivery and allowed account redirects in the existing Supabase project. Don’t create a second hosting or database account to work around this.

Other people don’t see my change

Make sure you edited the shared workspace and selected the same group. Ask the other person to click Refresh. The old local demo saves only on its own browser.