Pod Agreements

Last updated: 2026-07-17

What agreements are

Pods can ask members to sign an accountability agreement before taking up a role — a written commitment (a code of conduct, a stewardship pledge, role expectations) that you sign with your wallet. It's how pods make expectations explicit and mutual: everyone in the role has put their name to the same words.

Signatures are cryptographic but free — you sign a message with your wallet; it's not a blockchain transaction and costs no gas.

Signing an agreement (members)

1. Open the pod's page. If the pod has agreements, a Pod Agreements section lists them — each card shows the agreement's name, which role requires it ("Required for: …"), and your status: a green "You signed" or a red "Not signed".
2. Click Sign on an unsigned agreement (or View to just read it).
3. A dialog shows the full agreement text. Read it — this is the commitment you're making.
4. Click Sign and approve the signature in your wallet. Free, instant.
5. Your status flips to "You signed," and your name joins the agreement's signature list.

What happens if you don't sign

Unsigned required agreements block the features of the role that requires them. If you hold a role with an unsigned agreement, permission-gated features (managing members, treasury, surveys, and so on) will refuse access with the message "You must sign required agreements before accessing this feature." Signing immediately unblocks you.

Who can see signatures

Signatures are visible to the pod: each agreement lists who has signed and when, with names linking to member profiles. That visibility is the point — an agreement is a commitment made to each other, not a checkbox.

Creating agreements (pod leaders)

Agreements are attached to roles, as an eligibility requirement:

1. Open your pod's Manage page and edit the role that should carry the agreement (role setup → eligibility criteria).
2. Add a criterion of type agreement — give it a name and the full agreement text (the text is exactly what members will read and sign, so write it carefully).
3. Save. Members holding or applying for that role will now see the agreement on the pod page and must sign before using the role's gated features.

Notes for leaders:

• Keep agreements short and concrete — a page of clear expectations beats ten pages of legalese nobody reads.
• The signature list on the pod page doubles as your record of who has committed.
• One signature per member per agreement; there's currently no re-signing flow, so if you materially change an agreement's text, treat it as a new agreement.