How do we start a new community on Qumuna?

By Qumuna Editorial Team · Reviewed by Qumuna Product Review

Start with the work members need to do, set clear roles and information spaces, pilot real tasks with a representative group, then launch with a simple communication plan and a review date.

Short answer: begin with a small, usable setup rather than trying to configure every feature at once. Agree on the community's purpose, who is responsible for each area, and where official information belongs. Pilot announcements, discussion, events, files, and a decision with a varied group of members before inviting everyone.

What should we decide before creating the space?

Write a short purpose statement and name the people responsible for administration, moderation, and member support. List the first three to five jobs the community must do reliably, such as sharing a notice, collecting feedback, running an event, publishing rules, or handing over a committee document. That list gives the setup a reason and prevents unused sections from confusing members.

How should we configure the first version?

Set up only the areas needed for those jobs. Give announcements, discussions, events, polls, files, and handbook material distinct purposes in plain language. Add named administrators and moderators rather than sharing an account, and check that smaller groups or sub-communities reflect real responsibilities. Review the current feature overview and live pricing page for available capabilities and plan limits.

What should be ready before a pilot?

Publish a short welcome, conduct expectations, a contact route for access problems, and the current rules or reference documents members will need. Prepare one realistic announcement, discussion, event, file, and poll. Keep personal information out of broadly visible material unless the audience and purpose are clear.

Who should join the pilot?

Invite people with different roles, devices, confidence levels, and accessibility needs. Include at least one person who did not help design the structure. Ask them to complete tasks without coaching: find a rule, respond to an event, follow a discussion, locate a file, and understand an announcement. Record where wording, navigation, notifications, or permissions cause uncertainty.

When should we launch to everyone?

Launch after the pilot's essential tasks work and the people who will administer and moderate the community know their responsibilities. Explain what the new space is for, where official notices and decisions will be published, how members can get help, and whether an older channel is being retired. Avoid duplicating every conversation across tools; it makes the source of truth unclear.

What should we review after launch?

Set a review date, such as four weeks after launch. Ask members whether they can find current information, understand where to post, and control notifications. Review unanswered questions, repeated support requests, and moderation work. Adjust the structure when evidence shows a problem, while keeping labels and expectations stable enough for guidance to remain useful.

Related resources

Next step

Write a one-page pilot plan with the purpose, five tasks, named administrators and moderators, and a review date. When the plan is ready, create a Qumuna community for the pilot rather than inviting the full membership immediately.