Members & roles
Owners, admins, members, treasury signers, workgroup leads, invite links and visibility.
The Members page (community sidebar → Members) lists everyone in the community with their role, and lets admins manage roles, workgroup leads, visibility, the Discord exchange rate, the main spending token and invitations.
Roles
Every member has exactly one role:
| Role | Who | What they can do |
|---|---|---|
| Owner | The wallet that created the community. | Everything an admin can. There is one owner and the role cannot be reassigned from the app. |
| Admin | Promoted by an admin, or automatically any base signer of the community's primary treasury. | Manage members, visibility, workgroups, GitHub, treasuries and budgets. Starting a spend still needs them to be a signer of that treasury (or a workgroup lead, for payouts of their workgroups). |
| Member | Everyone else. | View shared community pages, be assigned to tasks and get paid. Admin-only settings remain restricted. Members cannot change boards, budgets or settings unless they are a workgroup lead. |
Two further responsibilities sit on top of the role:
- Treasury signer — a wallet listed in a treasury's signer set. Base signers of a treasury sign, reject, submit and delete that treasury's transactions, build payouts, payments and anchor transactions from it, reconcile its incoming refunds and mint under its policy. Base signers of the primary treasury are admins automatically and cannot be demoted while they remain one ("Primary treasury signers must remain admins"). Base signers of other treasuries keep their existing role (usually member) and only act for that wallet. A clawback treasury's recovery signers and a co-signer treasury's member co-signer (see Treasury templates) must already be members and are not made admins: recovery signers build and sign recovery payments from the lock date, the co-signer signs co-signed transactions, and both keep their role otherwise.
- Workgroup lead — assigned per workgroup. While new workgroups are not decided by vote, an admin assigns leads directly. While they are, adding or removing a lead is a proposal the other leads can object to, and an admin can still remove a lead immediately with a reason. Leads manage that workgroup's board and tasks, edit its budget row, and can build a payout when every selected task belongs to a workgroup they lead. Leads are otherwise ordinary members.
Who can do what
| Action | Member | Workgroup lead | Admin / owner | Base signer (of that treasury) |
|---|---|---|---|---|
| View shared community pages | yes | yes | yes | yes |
| Create / edit tasks on a board | — | their workgroups | yes | yes (if also admin) |
| Create workgroups, edit details, archive | — | — | yes (by proposal when workgroups are voted on) | yes (if also admin) |
| Edit budgets | — | their workgroups (workgroup budgets only) | yes | yes (if also admin) |
| Reset budgets | — | — | yes | yes (if also admin) |
| Make proposals, vote | as the governance settings allow | as the settings allow | as the settings allow | as the settings allow |
| Change governance settings, cancel a proposal | — | — | yes | yes (if also admin) |
| Build a payout | — | if all selected tasks are theirs | — | yes |
| Build a payment | — | — | — (recovery: recovery signers only) | yes |
| Build an anchor transaction, re-run the co-signer check | — | — | — | yes |
| Create / manage calls and attendance tasks | — | their workgroups | yes | yes (if also admin) |
| Open Integrations / Call platforms settings | — | — | yes | yes (if also admin) |
| Sign / reject / submit / delete a transaction | — | — | only if a signer on its spending path | on its spending path |
| Create a treasury, connect GitHub, manage members | — | — | yes | yes (if also admin) |
| Archive or restore a treasury | — | — | yes | yes (if also admin) |
| Mint tokens | — | — | — | yes |
| Reconcile incoming refunds | — | — | classify (Details) only | yes, for their treasury |
Community admin manages the community; it does not by itself let someone build a payout, payment, mint or anchor from a treasury they do not sign. The base-signer column is per treasury. A recovery signer or co-signer who is not an admin has the Member column's rights, plus signing on their own spending path (and, for recovery signers, building recovery payments). No signer of any group can be removed from the community.
Pages that need a role you do not have show "Members only." or "Admin access required." instead of their content.
Changing roles
Admins see buttons next to each member:
- Make admin on a member.
- Demote on an admin. Disabled for base signers of the primary treasury.
You cannot change your own role.
Workgroup leads
While new workgroups are not decided by vote, each member who is not an admin has a Lead of row that admins edit with a checkbox per workgroup. Tick a workgroup to make that member its lead; untick to remove them. Everyone else sees a lead's workgroups listed as badges.
While new workgroups are decided by vote, those checkboxes are badges for everyone. Workgroup leads at the top of the page lists each workgroup: an admin or a lead of that workgroup uses Change leads to propose who is added and removed. An admin's Remove on a badge takes that person off immediately and asks for a reason, which every member can read under Recent lead removals. An open proposal is linked from the same list.
Visibility
The Community card at the top of the page (admins only) sets the community's visibility:
- Public — listed on Discover; anyone signed in can join as a member.
- Private — members join through an invite link, are added by an admin below, or through GitHub assignments and linked Discord capture. Call check-in does not join a private community. See Joining a community.
Chosen when the community is created (private by default); change it here any time.
Discord exchange rate
Also in the Community card, admins choose which exchange rate the footer of Discord payout notifications shows:
- ADA (the default) in a fiat currency of your choice, USD unless changed;
- Another coin… — any coin listed on CoinGecko, by its id (the last part of its coingecko.com URL, for example
singularitynet); - None (date only).
Prices are fetched from CoinGecko when the message is posted. If the price cannot be fetched, the footer shows the date alone.
Main spending token
Also in the Community card, admins pick the token the community mainly budgets and spends: ADA (the default), any token the community has paid out, or one a treasury wallet currently holds. The Dashboard charts it first and lists it first in its tables; when no budget is set for the period in view, it is the only token charted.
Invite links
In the Community card, admins can Create invite link. Choose how long it lasts (7, 30 or 90 days, or never), an optional use limit, and an optional label for your own notes. The page shows the full URL once — copy it and share it (for example in Discord). Anyone who opens a valid link, signs in with a Cardano wallet on the community's network, and clicks Join becomes a member. After joining, the page points them at Profile & settings to set a handle and link Discord, GitHub or Google if they want; the invite never sets those for them.
Every link is listed with its status (Active, Expired, Used up or Revoked), uses and expiry. Revoke is available while a link is Active and stops it immediately. The raw token is not stored (only a hash), so you cannot re-copy an old URL from the app — create a new link if you lost it. A community may have up to 20 unrevoked invite links at once: expired and used-up links still count toward that cap until you revoke them. See Invite links.
Adding a member
In the same card, paste a wallet address (addr… on mainnet, addr_test… on preprod) and click Add member. The wallet becomes a member immediately, even if it has never signed in. When its owner signs in for the first time, the community is already there. Promote them with Make admin if needed, or list them as a base signer of the primary treasury when creating or re-pointing it. For onboarding many people at once, prefer an invite link.
Each member card shows the short address, "(you)" for yourself, the display handle or "no handle", the linked GitHub username if any, a signer badge for base signers (recovery signer or co-signer for those groups), and the role badge.
Leaving a community
There is no leave or remove-member button on this page yet. Ask a community admin or contact the operator through the privacy policy for administrative support. The removal API excludes the owner, treasury signers of any group (base, recovery or co-signer) and the admin making the request. Removing an eligible member also clears their workgroup lead assignments in that community; it does not erase task or payment history.