Skip to main content

How to Set Up Dapple: A Step-by-Step Onboarding Guide

Get your Dapple organisation from sign-up to a live submission form: check your details, set up payments, invite your team, build your form, set up stages, test and publish.

Written by Oz Osbaldeston

Welcome to Dapple. When you sign up, Dapple creates your organisation, a team and some sample projects with ready-made forms. This guide takes you from there to your first live submission form, in the order we recommend. It takes around 30 minutes for your first project.

Dapple helps you:

  • Keep every submission in one organised place, instead of inboxes and scattered files

  • Move submissions through clear stages, from received to selected

  • Send submissions to reviewers or judges in review rounds

  • Take entry fees securely through Stripe

What do you need before you start?

  • Your organisation's logo and brand colour

  • The email addresses of any team members you want to invite

  • The questions you want creators to answer. A rough list, or an old form, is enough: Dapple can build a first draft from a description

  • Your business details for Stripe, but only if you'll charge entry fees

Quick summary of the steps

Step 1: Check your organisation details

You added your organisation name, logo, use case and country when you signed up. To check or change them:

  1. Click your organisation name at the top of the sidebar, then click Settings.

  2. On the Settings tab, open General.

  3. Update the Name, Logo, Colour, Industry and Country as needed.

Creators see your name and logo on your forms and pages. Your country is used for compliance. See How to set up your organisation's general settings.

Step 2: Set up payments (only if you charge fees)

Skip this step if your call is free to enter. If you charge entry fees, you need a Stripe account connected to Dapple before you can publish a form with a payment field.

  1. Go to Settings → Settings tab → Payments.

  2. Click Set up Stripe account. Stripe opens in a new window.

  3. Follow Stripe's steps to add your business and bank details.

  4. Back in Dapple, choose your currency and check your tax settings.

Already use Stripe? Dapple creates a new Stripe account for your payments, but you can reuse your existing details. Sign in with the same email you use for Stripe and select your existing account, so you don't need to upload your documents again. Stripe may still ask for extra information.

Card payments, Apple Pay and Google Pay are all available at checkout. For full details, see How to connect a Stripe account.

Step 3: Invite your team

  1. Go to Settings → Users, then click Add User.

  2. Enter their email address.

  3. Choose their Organisation Role (see the table below).

  4. Under Teams Membership, choose which teams they belong to.

  5. Leave Send invite email ticked, then click Add User.

Role

What they can do

Use it for

Administrator

Sees and manages every team and all organisation settings

People who run your programme

User

Has dashboard access, but only sees submissions in the teams they belong to

Staff who work on specific programmes

Reviewer Only

Reviews the submissions you assign to them. No admin access

External judges and reviewers

You don't need a separate reviewer account to review submissions yourself. Admins and team members can review from their own account under My Reviews. For more on roles, see How to add a user.

Step 4: Create your first project

A project holds one submission form and everything that comes in through it, such as an award, a grant round or an open call.

The quickest way to start is to edit one of the sample projects Dapple created for you. Open Projects in the sidebar and pick the one closest to what you're running.

To start a new one instead:

  1. On the Dashboard, click New → New Project.

  2. Enter a Project Name and choose the Team it belongs to.

  3. Choose a starting point: the Template tab, or Existing project to copy one you've already set up.

  4. Click Create from template (or Copy and create).

Step 5: Build your submission form

Open your project and click the Form Builder tab.

  • Starting from an empty form? Describe what the form is for and click Start generation. Dapple drafts the fields for you to edit. Or add elements one at a time to start from scratch.

  • Add fields from the Elements panel: text, file uploads, multiple choice, payment and more. See Form field reference.

  • Split long forms into steps, and use conditional logic to show or require fields only when they're relevant.

  • Add your guidelines and terms: see how to add submission guidelines and terms and conditions.

  • Match your brand with Change Theme (colours and background image) and Change Header (header image). See How to add a header image.

Use Preview option to see the form as creators will. When you're happy, click Publish New Version, review the list of changes, then click Save New Version.

Good to know: your edits aren't seen by creators until you publish a new version. Publishing doesn't open the form either: that's controlled by the project's visibility (Step 9).

Step 6: Set up stages

Stages are the steps a submission moves through, such as Received → Longlist → Shortlist → Selected.

  1. In your project, click the Workflow & Reviews tab.

  2. Click Add Stage to add a stage, or edit an existing one.

  3. For each stage, set an Internal stage name for your team and a Display name for creators, which is what creators see as their submission status.

  4. Use the arrows to put the stages in order.

Each stage can also have its own automations (for example, sending an email when a submission arrives), review rounds and a public gallery. You can add these now or later. See What are stages in Dapple?.

Step 7: Create your listing page

A page brings all your open projects together in one place: a single link you can share anywhere that stays up to date.

Go to Settings → Pages and click Create New Page. See What are pages in Dapple? and How to set up pages.

Step 8: Test the submission flow

Before you open to the public, submit a test entry yourself.

  1. Set the project's visibility to Private (Step 9 shows where). Draft forms can't be opened, even with the link.

  2. Copy the submission form link from Share.

  3. Open the link in a private or incognito browser window and submit as if you were a creator.

  4. Check that file uploads work, the payment step appears (if you charge fees) and the confirmation email arrives.

  5. Here's a pre-launch checklist to make sure everything has been done before going live.

Step 9: Publish

Two settings control whether creators can submit. Change them in the project's Settings tab, or from the bar at the top of the project.

Setting

Options

What it means

Visibility

Draft

Not available to creators

Private

Open to anyone with the link

Public

Open to everyone and discoverable via search engines

Availability

Always

Accepting submissions at any time

Between Dates

Accepting submissions within a date range you set

Closed

Not accepting submissions

To go live, set visibility to Public (or Private to share the link yourself) and choose your availability. See Set your submission forms live.

Step 10: Set up review rounds (can be done later)

If reviewers or judges will score submissions, add a review round to the stage where reviewing happens.

  1. In the Workflow & Reviews tab, click Add review round on the stage.

  2. Work through the steps: Name & stage, Reviewers, Guidance, Deadlines, Scoring and Notifications.

Once your round has been created, you can then assign reviewers to submissions straight from the submissions list. See How to create a review round.

Best practices

  • Start from a sample project or template rather than a blank one. It's faster to delete fields than to build them

  • Keep your form short. Only ask for what reviewers need to make a decision

  • Always run a test submission before you go public, especially if you charge fees

  • Set up stages before submissions arrive, so nothing piles up in one column

Where to go next

Did this answer your question?