Using Qumuna for housing and tenant groups

By Qumuna Editorial Team · Reviewed by Qumuna Product Review

Housing and tenant groups can use Qumuna to separate building-wide notices, member discussion, meetings, documents, decisions, and smaller working groups while keeping access role-based.

Short answer: Qumuna can provide one structured home for a tenant union, housing co-operative, residents' association, or similar group. The useful pattern is to separate urgent notices, open discussion, events, polls, files, and local subgroups rather than copying every message into one chat.

Map the community before configuring it

List the people and groups who need different information: all residents, members only, elected leaders, moderators, committees, buildings, blocks, floors, or working groups. Decide which boundaries are about visibility and which are only useful labels. Avoid creating a separate space when a topic or event would be easier for members to follow.

A practical information pattern

Announcements: building access changes, meeting notices, service interruptions, or consultation deadlines.
Discussions: repairs, priorities, shared concerns, and proposal development.
Calendar: meetings, inspections, social events, and recurring sessions with RSVP.
Polls: preference checks, consultations, and decisions where the group's rules permit platform voting.
Files and handbook: current rules, meeting papers, guidance, forms, and agreed procedures.
Sub-communities and organisational units: spaces for buildings, floors, committees, or other defined groups when access should follow that structure.

Protect personal and sensitive information

Do not publish tenancy details, complaints, access needs, contact information, or casework to a broad group merely because the platform makes sharing easy. Decide which information belongs in a community space, which requires a direct leadership conversation, and which should remain in an appropriate case-management system.

Qumuna's current privacy practices are described in the privacy policy. Community administrators remain responsible for the content they upload, their invitation choices, local policies, and any additional legal duties that apply.

Make urgent communication realistic

An urgent announcement can distinguish an important update inside Qumuna, but no community app should be treated as a replacement for emergency services or a legally required safety system. Publish the channels members should use for emergencies, urgent repairs, safeguarding, and out-of-hours contact.

Plan moderation and continuity

Use named accounts and assign roles according to responsibility. Keep at least two trained administrators where the group's rules allow it, document how leadership changes are handled, and review permissions when committees or tenancies change. Put conduct and reporting guidance in the handbook so moderation does not depend on unwritten memory.

Related resources

Next step

Sketch your audiences and five most common workflows on one page. Then compare the proposed structure with the Qumuna feature overview and the current plans and limits before inviting members.