TOME — THE COMMUNITY ENGINE

Run a membership organization the way it's actually built.

Divisions and ranks, events and attendance, approvals that need more than one signature, a currency your members earn, and a separate space for every team. The Community engine is what a 700-member organization runs on today.

Image pending — organization / command context (David's call)

  • 700+ members
  • 40+ permission grants
Why it exists

Most tools flatten an organization into a mailing list with a login.

A unit leader should see her own teams and no one else's. When someone is promoted, their access should change the moment the promotion does, and the record of why should outlive the login they used. Some decisions are too big for one person: removing a member, promoting a senior officer, or changing the rules everyone signed up under.

Off-the-shelf tools give you a handful of flat roles and a group chat. The organization ends up living in a dozen places, and the structure that holds it together lives in people's heads. The Community engine puts the structure in the software.

What's in it

The parts of an organization, on one identity model.

Org chart and ranks

An org chart you define in your own words: divisions, teams, squads, positions and ranks, with promotions, delegated authority and a record of conduct. More than forty permission grants follow the chart.

Events and campaigns

Events with attendance, plus campaigns and a document library.

Recruiting and recognition

Recruiting and recognition, so the way people join and the way they're honored live in the same system as everything else.

Approval flows

Approval flows for decisions that need them: a single approver, both sides agreeing, a quorum, or a fixed sequence of signatures.

Community currency

A community currency with wallets and transactions. Wallets are private by default, and a transaction can't be applied twice. This part is labelled Preview, so its API can still change between minor versions.

Accounts, memberships and projects

Accounts, memberships and projects, so each team or client organization gets its own space with its own members.

What it runs700+ members

A 700-member organization, today.

Vanguard, a Star Citizen milsim eight years in the making, moved off a dozen disconnected tools and onto this engine. Its full order of battle runs here, with hierarchical command, delegated authority and a training academy. Its governance needs a signature quorum before a ban, a senior promotion or a change to its governing documents takes effect. The Vanguard case file →

You can also walk a smaller organization on our demo store: its divisions, members and events, seeded and public. Walk the demo →

Capture pending — Vanguard order of battle / chain of command (David's shot list)