Admins can retire, remove or reinstate members. Anyone can bow out on their own, and any past member can ask their way back in. Every scorecard, handicap and Order of Merit standing stays exactly where it was.
Open any member to make them inactive or, when you need to, remove them outright. Making someone inactive is a soft change: they move to Past Members and simply stop counting toward your active roster.
The roster shows active members first, then a Past Members section below a clear divider. On the tribes tab, past tribes carry a Past member badge and sink to the bottom, with a Past Memberships filter to see just them. Duplicate placeholders from pre-onboarding fold into the real member automatically.
Members can resign from a tribe themselves, no admin needed, and become a past member. Admins can reactivate any past member the moment they return, right from the Past Members list.
A past member sees the tribe as a visitor again, not the full member view: the public profile with a clear Request to Rejoin. Tap the tribe from your list to open it. On open tribes you are reinstated on the spot; on private ones an admin approves, and the toast tells you the truth either way.
Kept in the loop
Being made inactive, removed or reactivated sends the member a notification and a push. When someone resigns, the tribe's admins are notified. Every message taps through to the tribe.
What stays intact
Making a member inactive or resigning only changes their status. Tournaments, scorecards, handicaps and Order of Merit standings are fully preserved, and past members keep every point they earned with the tribe.
Safe by design
All actions run through database functions that enforce Row Level Security, so authorization always prevails. The tribe owner can never be removed, and the last active admin cannot leave without appointing a successor first.
Shipped together on the SwingTribe PWA and Flutter app.