Skip to main content

Create a Garden

An operator preparing garden setup materials beside maps and planting plans
Operator chapter

Set garden details, seed the first team, then deploy.

What this helps you do​

Deploy a brand-new garden in the Green Goods admin so your community can start submitting work against it. This is a one-time setup — you will not redo it once the garden is live.

Creating a garden is a deployer-level action. If you are already an operator inside an existing garden, you probably don't need this page. Jump straight to Make an Assessment to set the reporting frame, or Approve Work if the garden already has one.

Admin route

The current admin create route is /garden/create. Use that route when you need to open the form directly.

Before you start​

Have these ready so you don't bounce around mid-form:

  • Deployer access in Green Goods admin. If you hit a permissions error on /garden/create, ask the team to add you as a deployer.
  • A name and a short description of the garden.
  • A location (bioregion, city, or community).
  • A banner image (optional but recommended).
  • An ENS subdomain idea — the form suggests one from the name, but you can edit it.
  • A domain selection — Solar, Agro, Education, or Waste. Domains decide which actions gardeners can submit against later.
  • A rough list of the first operators and gardeners you want on board. These addresses are included in the deploy transaction, and you can add or fix members later from Garden Members.
  • A funded wallet on the target chain for the deployment transaction.
tip

You need to be online to deploy — the form will block submission if you lose connectivity.

Step-by-step flow​

Step 1: Open the Create Garden form​

  1. In admin, open Gardens in the left sidebar, then click Create (or go directly to /garden/create).
  2. If you hit a 404 or a permissions warning, you don't have deployer access yet. Stop here and ask the team.

The form opens on Garden details. Fill the required fields, pick the garden's domains, then click Continue. Step 2 plans the initial team. Step 3 reviews everything before you sign the deploy transaction.

Admin create garden form showing garden details and domain selection

Step 2: Fill in Garden details​

  1. Enter the Garden name. The ENS subdomain field auto-suggests from the name — edit it if you want a cleaner handle.
  2. Enter the location.
  3. Add a description. Two or three lines is plenty.
  4. Attach a banner image if you have one.
  5. Select the domains this garden will run. Pick only what you actually plan to use — adding a domain later is easier than explaining unused ones.
  6. Click Continue.

Step 3: Plan the initial team​

  1. Add the wallet addresses of the operators you want to seed the garden with.
  2. Add the gardeners who will be submitting work from day one.
  3. You can leave either address list empty and add members later from Garden Members. If you include addresses, the deploy transaction passes them to the contract and the contract attempts to seed their roles during deployment.
  4. The current create form does not expose a joining-policy selector in this step. Treat new gardens as invite-only unless your admin build explicitly shows Open joining enabled in review.
  5. Click Continue.

Step 4: Review and deploy​

  1. Read back the summary: name, slug, description, Open joining value, domains, and planned team.
  2. If anything is off, click back into the earlier step and fix it — don't edit by memory.
  3. When everything is right, click Deploy garden and approve the transaction in your wallet.
  4. Wait for the transaction to confirm. The wizard stays on this step until it does.

How to know it worked​

  • You are redirected back to the garden list at /garden.
  • A success toast appears: "Garden created — Your garden has been deployed successfully."
  • If you seeded members at step 3, you see a reminder to verify those roles in Garden Members after indexing catches up.
  • The new garden appears in the garden list.
  • If you open it in the client app, the banner, location, and description all render as expected.

If something goes wrong​

  • 404 on /garden/create. You are not a deployer, or the route is not available in the current admin build. Contact the platform admin instead of working around it.
  • "You're offline" toast on Deploy. The form blocks deployment when the network is down. Reconnect and retry — the form keeps your progress.
  • Transaction cancelled. You cancelled the signature in your wallet. Click Retry deployment when you are ready.
  • Transaction failed. Check the inline error card — it shows the raw wallet message when one is available. Common causes are insufficient gas funds and a wrong chain. Fix the cause and click Retry deployment.
  • Name or ENS collision. Pick a different garden name or edit the ENS subdomain before retrying.
  • "Cannot deploy yet." The form isn't ready for submission. Go back through the earlier steps and look for fields marked as required that are still empty.

After a successful deploy, finish setup by:

  • Verifying seeded members in Garden Members, then adding any missing operators or gardeners.
  • Confirming that metadata and banner render in both admin and the client app before sharing the garden link with your community.

Behind the scenes​

The deploy transaction creates the garden account on-chain, registers it in the Green Goods registry, seeds it with the domains you chose, and passes the initial gardener/operator lists to the contract. The contract attempts those role grants during deployment on a best-effort basis, so verify Garden Members afterward in case a grant failed or the indexer has not caught up yet.

Next step​

Next page

Set the assessment frame

Before the review queue fills up, define the baseline, domain, outcomes, and reporting window that later approvals should support.

Make an Assessment