For Leadership
Members of elected leadership see everything a member sees, plus the tools for running the tribe. These are gated to the leadership ring — a regular member signing in never sees them, and never receives their code.
The membership roll is the tribe's most important record, and orgware gives the recordkeeper full control of it:
- Look up any member and see their full record and their complete change history — every edit, who made it, and when.
- Maintain the record — status, member type, position, voting eligibility, key dates, and the recordkeeper fields: fee status and exemptions, the core-member flag (used for BIA reporting and constitutional compliance), second-chance status, and review flags.
- Convert an honorary member to a regular member — a single reviewed action that archives the old ID (so it can never be reused) and issues a fresh regular ID in one atomic step, carrying the person's identity and contact details over. There's a preview first, so you see exactly what will change before you commit.
- Manage member photos — upload or replace the photo on any member's record.
Every change to the roll is written to an audit log, and the roll lives in an access-controlled database that's backed up nightly (encrypted, off-site) and is never exposed to the public site or to non-leadership members.
Note: these roll capabilities are live today through the platform's API and tools. The dedicated in-portal roll book screen (
/members/tribal-roll) is being finalized — until it lands, the recordkeeper works the roll through the tools rather than a polished page.
Leadership sees the entire Tribal Record — every classification, including the leadership ring (banking, legal, membership, and other sensitive records) — and can hold durable API/MCP keys to work with the whole corpus. → The Tribal Record · API access
Leadership has a role-tiered view of the tribe's contacts and lists — admin, viewer, or counts-only. → Contact & the directory
One of orgware's promises is honest cost transparency — leadership should always be able to see what the platform costs to run. The console shows, in real time:
- Cloudflare usage — Workers requests, database reads/writes and storage, file storage and operations, and key-value usage, each metered against the free-plan limits, with a plain-language verdict (comfortable / watch / warning) and a nudge if the tribe is approaching a paid tier (~$5/month).
- Email — how many member emails have gone out this month against the free allowance, plus any bounced or suppressed addresses.
- Backup health — when the last successful backup ran (healthy if within the last day and a half).
The whole point: no surprises. The tribe can see it's running a full member platform for a few dollars a month, and knows in advance if that's about to change. (This panel is fully live once a read-only analytics token is set — see How it's built.)
A couple of leadership screens are still being built out and currently show a
"port in progress" placeholder: the in-portal roll book
(/members/tribal-roll), the contact directory page (/members/contacts),
and an engagement dashboard (/members/engagement). The capabilities behind
the roll book already work through the tools described above; the pages are being
brought into the portal.
Everything here is leadership-only because of who you are, resolved at sign-in from the leadership allowlist and your role — not because of a hidden link. A member who typed one of these URLs would simply be sent back to the front door.
Next: How it's built.