Module reference

A module is a promise that a plan can switch on and a community type can support. Nothing here is sold twice: the treasury on the free plan is the treasury on the professional plan, and a module that is off is absent rather than half-present.

The basics, always on

Before any module: dashboard, calendar, announcements, inbox, notifications, search, settings and the audit log. These are not switchable and not billed — the floor every community stands on, including the free plan.

The dashboard is ordered by community type rather than by role: a scheme opens on who is late and by how much, a stokvel on this cycle's contributions and whose turn is next.

Members

The directory and the record of who belongs: invitations, roles, join requests and the move-in/move-out workflow. Nobody leaves the record by being deleted — a membership is deactivated, so a former resident's statements and votes survive.

Who uses it: everyone reads the directory; moderators, treasurers, protection leads and admins invite; only admins change roles or process moves.

Householdshousing only

A household lists the people who live in a unit — name, relationship, date of birth — without giving each of them an account. The head of the household maintains it; an admin can edit any.

Who uses it: every member (their own household), admins (all).

Chat & announcements

Channels, group conversations and direct messages in real time, with mentions, unread badges and an inbox. Announcement rooms are one-way and support acknowledgements.

Who uses it: everyone; moderators create channels, admins create announcement channels.

Notices & reminders

Bulletins the committee sends to a chosen audience — everyone, owners, people in arrears, one levy's payers, one unit's owners, or a role — over in-app, email and SMS, with quiet hours respected.

Who uses it: treasurer, moderator, admin.

SMS notificationspaid channel

The delivery path that lets notices and critical notifications reach people who are not looking at the app. Not a separate inbox: what a member receives is still their own notification, by text.

Who uses it: anyone the app notifies, once the channel is connected.

Treasury & dues

The community's money on a double-entry ledger: treasury and budget wallets, levy and contribution schedules, statements, arrears, expenses and approvals. Renamed Stokvel funds in a stokvel community.

Who uses it: everyone reads; the treasurer works in it.

Stokvels

A rotating savings group: an ordered roster, one recipient per cycle, a pot and a payout history. In a stokvel community this is the main surface rather than a sidebar entry.

Who uses it: everyone reads; the treasurer runs the rotation.

Proposals & voting

Proposals with five voting methods, three ways of deciding who counts, meetings with notice, register, quorum and minutes, and a versioned rulebook.

Who uses it: everyone votes; moderators and admins manage; the chair runs meetings.

Document library

Files with per-file visibility — all members, or admins only — and a per-community storage quota. Distinct from governing documents, which carry versions and an acceptance gate.

Who uses it: everyone reads; admins upload and set visibility.

Safety & securityhousing only

Panic alerts, incidents, the patrol roster, the patrol clock and patrol payroll. The panic button lives on the safety page and needs nothing but a two-second hold.

Who uses it: everyone raises alerts; the protection lead runs incidents, patrols and payroll.

Gate & visitorshousing only

Pre-authorised visitor passes as a six-character code plus a QR, and the guardhouse board a guard works all day. Every check-in, check-out and denial is logged with a time.

Who uses it: residents create passes; gate staff and protection leads work the board.

Projects

Community projects with milestones, a four-column task board, volunteers and a budget that can be funded from the treasury. Starting one is proposed; approval is an admin act.

Who uses it: anyone except gate proposes and volunteers; moderators manage; admins approve.

Parcels, assets & compliancehousing only

The physical community: the parcel register with owners and statements, the asset register with maintenance dates, reserve-fund planning, rule notices, design approvals and a compliance checklist.

Who uses it: everyone reads notices and approvals; admins maintain the registers.

Residential rentalhousing only

Rental properties, leases, monthly rent invoices, tariffs, meter readings and fault triage — for a community that also lets out units.

Who uses it: property managers and admins run it; tenants use My rental.

Marketplacehousing only

Listings, orders with a ten-step lifecycle, reviews, and a procurement flow where the committee asks for bids. Money moves between buyer and vendor; tribe.one records the order rather than holding funds.

Who uses it: everyone buys and sells; moderators curate; the treasurer posts procurement.

Community placeshousing only

The directory of what is nearby and who to call — schools, clinics, plumbers, the police station. Marking a place as an emergency contact puts it on the safety page.

Who uses it: everyone reads; moderators maintain; admins delete.

Analytics

Engagement, money and safety on one page, phrased in the unit your community type is measured in, with exports for a committee pack.

Who uses it: moderators, treasurers, protection leads, property managers and admins.

What is not a module

Platform administration is not sold to communities and cannot be switched on: the console that runs tribe.one itself is separate and invisible to tenants. Moderation of flagged content lives there too — a report is triaged by the operator, not by a neighbour with extra powers.

Two behaviours that surprise people: work orders have no module gate — they are always available, because a broken gate is not a feature to upsell. And announcements are read-only for committees; a committee that wants to broadcast uses notices or the community channel.

Portfolio console (Enterprise only)

One read-only console across the communities a group runs: money billed, collected and outstanding per community, member counts, open work orders and each community’s own metric. It is granted on the Enterprise plan and never appears on a community’s own bill.

An organisation role grants nothing inside a community — no broadcasts, no role changes, no settings. Community work stays with that community’s committee. Read the portfolio guide.