Skip to main content
Applications are for teams that want to read something about a person before they’re on the roster. Turn them on by setting Join policy to Application required under Settings. The Applications tab has two halves: the review queue, and the builder for the form that fills it.
!!-IMAGE-NEEDED-!! — The Applications tab showing pending applications above the Application form card.

​
Reviewing applications

Pending applications are listed with the applicant’s name, email, and their answers inline — you don’t have to click into each one. Each row has Approve and Reject. Approving puts them on the roster.
If someone applied as a coach or manager, the row is badged applying as coach right next to the Approve button. Approving that puts an adult on a youth roster as staff — the badge is there so it can’t happen by accident.
Applicants see their own status as Pending, Approved, or Rejected.

​
Building the form

Click into the Application form card to edit it.

​
The basics

​
Questions

Add as many as you need. Each question has a label, optional help text, a required flag, and a type: File questions let you restrict accepted file types and set a maximum number of files.
!!-IMAGE-NEEDED-!! — The question editor with a select question expanded, showing its options list.

​
Pages and content blocks

A form can be a single list of questions, or it can be split into pages — useful when you want to explain something before asking about it. Each page holds blocks, in any order:
  • Heading — a section title.
  • Paragraph — instructions, expectations, what the season looks like.
  • Image — a photo of the team, a course map.
  • Embed — an embedded video or external page.
  • Divider — a visual break.
  • Question — one of the questions from your question bank.
Questions live in a bank; you place each one on a page. A question can only sit on one page, and the builder shows you which questions aren’t placed anywhere yet so nothing goes missing.
!!-IMAGE-NEEDED-!! — The page builder with two pages, one holding a paragraph block, an image block, and two questions.
Save the form, then open your public apply page at time2.bike/team/[slug]/apply and walk it yourself. It’s the fastest way to catch a question that reads badly out of context.

​
What applicants see

The public application lives at time2.bike/team/[slug]/apply, reached from the Apply to join button on your team page. They pick a rider profile, choose what they’re applying as (if you accept staff), work through your pages with a Step 2 of 3 indicator, and review everything before submitting. Answers are snapshotted when they submit — editing a question later doesn’t rewrite what someone already answered.

​
Next

Roster & roles

What happens to someone once you approve them.