Sharing & collaboration

Every plan starts private. Share this plan on the issue page has Make this plan public, which publishes a read-only version at its own link and gives you Copy link.

Make private again takes it back down. The link is kept, so re-publishing later restores the same URL rather than breaking every copy of it people already have.

Once public, you get light counters: how many times the page has been Seen, how many times it has been Shared, and — for a petition — how many Signatures it has. Those are visible to you, not to visitors.

Only the plan: the summary and the list of steps. Deliberately not shared:

• Your drafts — every letter and script stays private.
• Your address and the representatives matched to it.
• Your research brief and your chat.
• Outcome notes and anything you recorded about what happened.

Anyone with the link can read it — there is no sign-in. The link is the only thing guarding it, so treat it as public the moment you send it to one person. Voci keeps these pages out of search engines, but that is not the same as secret.

A signed-in visitor to a public plan can copy it into their own account. They get their own editable version — same summary, same steps — and everything from there is theirs: their drafts, their representatives, their progress. Nothing flows back to you.

This is the fastest way to bring people in. Someone facing the same zoning vote does not need to describe it from scratch; they take your plan and aim it at their own council member. Cloning counts against their monthly project allowance like any other new plan.

Sharing a link is one thing; working on an issue together is another. Expand People on this issue and enter an email address, then Invite.

• If they already use Voci, they get access immediately and the plan appears under Shared with you on their dashboard.
• If they don't, the invite is held under that email and they get a link. It is claimed the first time they sign in with that address — so they have to sign up with the address you invited.

Invites show as pending until claimed, and Remove revokes access or cancels an unclaimed invite. Twenty invites a day.

Both can

Read the plan, run and read research, chat with the research agent, generate and edit drafts, send letters, and mark steps complete.

Only the owner can

Invite and remove people, publish or unpublish the plan, invite people to sign its petition, and delete the issue.

There is one owner — whoever created the issue — and ownership does not transfer. AI work a collaborator does spends from their own monthly allowance, not the owner's.

When a plan contains a petition step and the plan is public, the public page gets a signing button. Signing requires a Voci account — that is what keeps a signature count meaning something — and each account can sign a given petition once.

The count is shown on the public page and in your share panel. People can unsign.

Ask people to sign in the share panel invites specific people by email. Voci users also get the request as a card on their dashboard with Sign and Dismiss; everyone gets a link to the petition itself.

You will see how many people you have invited. You will not see who declined.

The same person cannot be invited to the same petition twice, and invites are capped at twenty a day. Per-action limits has the rest.