Jordan LeeVolunteer lead · 3h
First summit for anyone? The Thursday volunteer call keeps going after it wraps. All welcome.
♥ 246 commentsView earlier comments
Sam OkaforJoined from Spring Summit First one for me. I’d love to join Thursday!
Where your community meets.
Everyone’s already here.
Spaces, a directory and an inbox on your own domain. Everyone who registered, enrolled or joined is already in, so nobody signs up twice.
Spaces, members and an inbox. Switched on when you’re ready.
Spaces
Conversations by topic, open to everyone or private to one group, each with its own hosts.
Members
A directory people choose to join, searchable by the fields you pick and they allow.
Inbox
Replies, connection requests and updates from everything else you run, in one place.
Let them walk in. Through the door they already used.
An event registration, a course enrolment, a membership or an invitation lets someone in and places them in a group named for it. Private spaces open by group.
- Choose which doors are open, one switch each
- Groups follow membership status on their own
- No list to import, no invitations to chase
Find each other. Showing only what they choose.
People opt in to the directory and pick what to share. Search by name, group or the fields you choose, and every edit updates the contact you already have.
- Opt-in listing, off until they turn it on
- A hidden field can’t be searched or shown
- Connect from a profile, block from the same menu
Give every topic a room. And every room a host.
Open a space for everyone or keep it to one group. Hosts pin what matters and hide what doesn’t, and reports come to one queue.
- Posts, comments, likes and images
- Hosts pin up to three posts and hide or restore
- Mute someone for 1, 7 or 30 days
Against a separate community tool. And the list it makes you keep.
A community tool starts empty and keeps its own list of people. Yours already exists: everyone who registered, enrolled or joined, in the account where you run all of it.
| A separate community tool | Mercleo Community | |
|---|---|---|
| Someone registers for your event | Exported and invited by hand | In the attendee space when they finish |
| A membership lapses | Removed from the community, eventually | Out of the members-only space on its own |
| Someone changes their job title | Updated in one tool, stale in the other | Changed on the contact you already email |
| Someone signs in | A second password for a second site | A one-time email code, on your domain |
- Also in Community
- Announcements
- Pinned posts
- Images in posts
- Private spaces
- Space hosts
- Moderation queue
- Reports
- Mutes
- Blocks
- Connections
- New this month
- Profile fields
- Access groups
- Event attendee directory
- Your own domain
- Email code sign-in
One set of people. And your community built on it.
Audience
Every profile edit lands on the contact behind it, the same person you email and report on.
Events
A registration lets them in, and each event can keep an attendee directory of its own.
Marketing
The people in your spaces are the people on your lists. Nothing to sync between the two.
Questions we get asked.
No. It’s part of the core on every plan. Plans change how much room you have, never whether you get it.
Never. Seats are for your team. Your community signs in with a one-time email code, with no password and no seat.
You choose the doors: an invitation, an event registration, a course enrolment, a membership or open sign-up. Each person lands in an access group named for the door they came through, and private spaces open by group.
Only what they choose. The directory is opt-in, a field someone hides can’t be searched or shown, and a block works both ways. You decide which profile fields exist; they decide which ones to share.
No. Community stays off until you switch it on, so a portal for tickets, courses or invoices stays exactly that.
No. It runs in the browser on any phone or computer, on your own domain, with your branding.