Creating Campaigns
A campaign is your survey, poll, or form on Logbook. Here's everything you need to know about creating one.
#Campaign Components
#Participants (who can open the campaign)
- Anyone: Questions are stored in plaintext. Anyone with the link can read them and respond. Best for community polls.
- With password: Questions are encrypted in your browser with a campaign key. The key is protected by a random password that travels in the share link (after the
#, so it never reaches a server). Only people with the password can open the campaign. - Address list: Questions are encrypted, and the key is released only to Sui addresses you put on the list. You can add or remove addresses after publishing.
#Answers visible to (who can read the responses)
- Everyone: Answers are public and counted on-chain in real time.
- Everyone with access: Everyone who can open the campaign sees all answers (password or address-list campaigns only).
- Voters only: Only people who responded (and you) can read the answers. Works for open campaigns too.
- Only me: Only you read all answers; each participant sees their own. Best for confidential feedback.
- After the end date: Nobody can read the answers until the campaign ends. Then everyone with access can. Best for secret ballots.
#Documents (optional)
Attach the text people are voting on: a proposal, a contract, a charter amendment, a design. Up to 5 files, 5 MB each.- The hash of each file becomes part of the campaign on the blockchain, in the same transaction that creates the campaign
- With the first response the documents freeze together with the questions: nobody, including you, can swap the file afterwards. Everyone responded about exactly this text
- Participants see the documents above the questions, and every download is checked against the on-chain hash first
- For private campaigns the file is encrypted for the people who can open the campaign, and the on-chain hash is salted, so outsiders cannot even test which document is being discussed
- Files are kept for a limited time (see Data Storage), but the hash is permanent: a copy downloaded today can be verified on the verification page years later, even when the file is no longer stored anywhere
#Title
A clear, descriptive name for your campaign. This is what participants will see first.#Description
Optional but recommended. Explain:- What you're asking about
- Why you're collecting this information
- How the results will be used
#End Date
When should the campaign stop accepting responses? After this date:- No new responses can be submitted
- Results become final and immutable
- The campaign is marked as "Ended"
#Questions
The core of your campaign. See the Question Types section for details.#Creating Your Campaign
#Step 1: Choose Who Can Participate and Who Sees the Answers
Two independent settings control privacy:
Participants decides who can read the questions and respond: anyone, people with the password, or a fixed list of Sui addresses. Anything other than "Anyone" encrypts the campaign content in your browser before it is published.
Answers visible to decides who can decrypt the responses: everyone (public, counted on-chain), everyone with access, voters only, only you, or nobody until the end date.
- Community poll: Anyone + Everyone
- Team survey by link: With password + Everyone with access
- Confidential feedback: Anyone (or With password) + Only me
- Secret ballot for a DAO: Address list + After the end date
- Members-only results: Anyone + Voters only
#Step 2: Basic Information
Fill in your campaign details:
- Title (required)
- Description (optional)
- End date (required)
#Step 3: Add Questions
Click "Add question" for each question you want to include. For each question:
- 1Enter the question text
- 2Choose the question type
- 3Add answer options (for choice questions)
- 4Toggle required/optional
#Step 4: Review
Before deploying, review your campaign:
- Check all questions are correct
- Verify answer options are complete
- Confirm the end date
#Step 5: Deploy
Click "Publish Campaign" to publish your campaign to the blockchain.
If you signed in with Google, Logbook pays the gas fee. If you use a wallet, you confirm the transaction in your wallet and pay a small gas fee (test SUI is free during beta).
#Drafts From a Link
The creation form can open pre-filled from a link, for example one composed by an AI assistant in a chat (the format is described under API & SDK). A yellow notice says the draft came from a link: review every field, then publish as usual. Nothing is created until you do. If you need to sign in first, the draft survives the sign-in.
#After Deployment
Once deployed, your campaign:
- Has a unique on-chain ID
- Can be shared via link or QR code
- Will accept responses until the end of the selected end date
- Shows live results
For an address-list campaign, the campaign page shows an "Address list" panel where you can add or remove addresses at any time.
#Editing Campaigns
Campaigns can be edited only if they have zero responses. Once someone has responded, the campaign becomes immutable to ensure participants can trust that the questions haven't changed after they responded.
To edit a campaign:
- 1Go to your campaign page
- 2Click the "Edit" button (only visible if you're the creator and there are no responses)
- 3Make your changes to title, description, questions, or end date
- 4Save changes
If your campaign already has responses, you'll need to create a new campaign instead.
#Deleting Campaigns
Campaigns can be deleted only if they have zero responses. This prevents loss of participant data.
To delete a campaign:
- 1Go to your campaign page
- 2Click the "Delete" button (only visible if you're the creator and there are no responses)
- 3Confirm the deletion