Public site vs private member home: what goes where
Decide what belongs on your public website and what belongs in a private member home, with examples for churches, charities, events, and volunteer teams.
The short answer
Use your public website to help visitors understand the group and take a first step. Use a private member home for invited people to coordinate events, share updates, and find instructions. Choose access by audience; a public event can accept RSVPs without exposing internal notes.
- Public pages explain who you are, when you meet, and how to get involved.
- Internal conversations and personal details belong in spaces restricted to the right people.
- Link public invitations to the appropriate form or event instead of duplicating every detail.
Real-world groups run two kinds of communication. Visitors need a clear public face. Members need a place to coordinate the week. Mixing those jobs on one feed creates noise for newcomers and gaps for the people who already belong.
This comparison is a placement guide: what belongs on the public site, what belongs in a private member home, and how to decide when something sits on the border.
The two jobs in one sentence
Public site: Help a stranger understand who you are and how to take a first step.
Private member home: Help people who already belong find updates, events, forms, and each other without hunting through chat history.
Churches and small charities feel this split every week. A visitor searching for service times should not land on last month's volunteer shift thread. A board member looking for the facilities checklist should not dig through a public blog.
What goes on the public website
Keep the public site short, current, and visitor-shaped.
Usually public
- Home, about, visit info, programs or ministries
- Public event listings (title, time, place, who it is for)
- Giving or donate links to tools you already use
- Contact paths and first-interest forms
- Sermons or news you want indexed and shareable
Public tone
Assume the reader does not know your acronyms. Lead with logistics and invitation. Skip internal nicknames for rooms and teams unless you define them.
Update rhythm
Someone should own a monthly pass: times, addresses, featured events, and dead links. Public trust dies when the homepage still advertises a Christmas event in March.
What goes in the private member home
The member home is for people you invite: members, volunteers, staff, board, small-group leaders.
Usually private
- Announcements that only matter to people who already show up
- Event RSVPs and headcounts
- Volunteer shifts and signup forms tied to known people
- Profiles and member posts
- Messaging between members and leaders
- Shared reference pages (wiki): how we check in kids, who locks up, brand assets, onboarding notes
Private tone
You can use first names, building shorthand, and "see you Thursday." Still write so a new member who joined last month can follow along.
Update rhythm
This area moves weekly. Treat posts and events like a bulletin you renew, not a brochure you redesign once a year.
Borderline items (and a simple rule)
Some content sits on the fence. Use this rule:
If a stranger finding it helps your mission, make it public. If only invited people should act on it, keep it private.
Examples:
| Item | Public | Private |
|---|---|---|
| Sunday service times | Yes | Optional reminder post |
| Potluck after service | Light listing | RSVP + dish signups |
| Prayer request form | Link on Contact if open to visitors | Restricted care-team space for sensitive pastoral details |
| Annual report PDF | Often public for donors | Draft versions stay private |
| Board meeting notes | Rarely | Yes, for board |
| Volunteer orientation | Teaser on Programs | Full schedule + forms for volunteers |
When you are unsure, publish a short public teaser and put the operational detail behind login. Visitors get the invitation. Members get the checklist.
Why chat apps fail as the "private home"
Group chats are fine for quick pings. They make a poor system of record.
Common failure modes for a church admin or charity coordinator:
- New people join mid-year and cannot scroll back to the "real" instructions
- Announcements bury each other; nobody knows which message is current
- Files live on someone's phone
- You cannot separate public marketing from member ops
- When a leader leaves, the chat history leaves with their account habits
A member home with posts, events, forms, messaging, and wiki pages gives you durable places for durable information. Chat can still exist for "running late" messages.
One product, two surfaces
Tools that only build a brochure site leave member ops in email and chat. Tools that only build a social feed leave visitors without a clear front door.
Guava is built around both surfaces: a public website builder and a private member home. Live pieces include forms, events with RSVP, profiles and posts, messaging, and wiki pages. Free includes a Guava address for up to 50 members. Plus ($29/mo) adds your domain, unlimited members, remove branding, and Mailchimp/Kit integrations.
You can keep the giving processor and email tool you already trust. The win is putting visitor pages and member coordination in one owned place.
A weekly workflow that respects the split
- Monday: Update public events and any time/place changes on the site.
- Midweek: Post member announcements and open RSVPs in the member home.
- Before the weekend: Check public visit/contact pages still match reality.
- After the gathering: Move leftover logistics into wiki pages or a follow-up post so next month's volunteers are not starting from zero.
That rhythm is boring on purpose. Boring systems get used.
Quick placement checklist
- Public nav has fewer than eight items a newcomer cares about
- Service or program times appear on Home or Visit without login
- Access to RSVPs and shift lists matches the intended audience
- Announcements that name people or pastoral details stay private
- At least one wiki (or shared doc hub) holds "how we do X"
- Chat is optional backup, not the only archive
Next step
Map last month's messages into two piles: visitor-facing and member-only. Put the first pile on your public pages. Put the second into a member home with posts, events, and forms. If you want that split in one product, start free at Guava.
Useful next steps
Guava Team
We build Guava: a website and private member home for groups that meet in real life.
