日本語 | English
Session Concierge

User guide

Hosting: preparation

In this chapter: Hosting at a glance・Starting now (instant)・Creating a session (planned)・Form fields explained・Session status

01

Hosting at a glance

There are two styles. Instant for ease, planned when you want to announce it properly.

InstantPlanned
When to useStart on the spot and gather people via QRDecide the date and venue and announce it in advance
Membership neededRegistered users and upPremium
Entry pointMenu "⚡ Start now"Menu "▦ Create session"
Appears in list?No (only people who know the QR/ID)Yes
Advance recruitingNoneYes (applications & waitlist)
Running board on the dayBoth use the same jam board / monitor

This chapter first covers Start now (instant), then creating a planned session and, in turn, the form fields, statuses, song stages, running the session, monitor, and ending that come up there.

↑ Back to top
02

Starting now (instant)

The easiest way: start on the spot and gather people via QR (registered users and up).

  1. Open "⚡ Start now" in the menu (on the left on PC).
  2. Three things to enter: session name (pre-filled with "Jam session"), venue (optional), and the parts (leaving them as they are is fine). Type two or more characters in Venue and suggestions from registered venues appear (with their addresses). If yours isn't there, free text is fine.
  3. Press "Start" and the jam board opens right away. Put it up on the venue monitor to gather people.
One host can have only one instant session at a time. If you press "Start" while you already have one live, no new session is created — you're taken back to the live one (this keeps participants from being split across two identical sessions). To finish it, end it from "End" on the jam board.
Please host on a PC or tablet. The join QR code appears in the jam board's right panel only when the screen is wide (roughly 900px or more). An iPad in landscape shows it on any model (portrait only on the 12.9-inch / 13-inch).
The join ID is shown large in the same right panel as the QR (use it when telling people verbally). Instant sessions don't appear in any list, so you can't look the ID up from Home or the management hub — announce it from the wide screen too.
Parts are set up for you (the hint reads "Parts to set up on the board. You can start as is."). Add one with "Add part" and remove one with the ✕ ("Remove this part") on its chip (the last one can't be removed).
The per-song part lineup for the day is built separately when requesting songs, so you don't need to settle it here.
Only people who know the QR or join ID can enter an instant session (it doesn't appear in the list). It ends automatically 12 hours after the last action (no end-time entry needed).
↑ Back to top
03

Creating a session (planned)

Creating requires Premium. The menu's "▦ Create session" becomes your management hub.

Structure of the management hub

Open "Create session" and your sessions are gathered by status.

  • Create new: Create a new session from scratch (Premium only. If you're not Premium, it becomes unpressable and a notice appears above it).
  • Drafts: Edit saved drafts and take them through to publishing (shown only when you have drafts).
  • Sessions you created: Sessions that are public, live, and so on. The button on the right is "Edit".
  • Past sessions: Finished and canceled sessions. The button on the right is "Copy & create", which makes a new session from the same content (handy for regular events).
  • Co-hosts: Sessions where you've been appointed co-host (shown only when you have any).
Tapping anywhere on a card opens that session's details (use this to see participants, songs, and comments). Pressing "Edit" or "Copy & create" on the right does that action instead.
A published session with no event date shows a warning on its card prompting you to set one (only the host sees it). Sessions without a date drop out when people filter by "Date" on Home, and sit at the end of the list. Set the date from Edit so participants can find you.
This management hub handles planned sessions only. Instant sessions are one-off, so they don't appear in the history.

From creation to publishing

  1. Press "Create new".
  2. Enter each field (the next chapter, "Form fields explained", covers them one by one).
  3. To stop partway, use "Save draft". You can resume later from "Drafts" in the management hub.
  4. When you're ready, press "Publish". Here you choose "Pre-announcement" or "Recruiting" and the announcement begins.
Once a session has been published, its edit screen's buttons change to "Cancel" and "Update". Updating won't roll back progress such as the number of spots or the ongoing state.
↑ Back to top
04

Form fields explained

The creation form's fields, explained in the order they actually appear from the top. ★ marks required fields (on screen they are marked with a * after the label; only Session name, Venue, Event date, Start, End, and Parts to recruit carry it).

FieldMeaning / how to fill it in
Session nameThe session's name. Shown in the list and announcements.
DescriptionA description of the session. A line that conveys the vibe, like "Beginners welcome" or "Blues only", is helpful.
VenueEnter the venue name (free entry). If you run the same session repeatedly, keep the wording consistent so it groups together in the venue ranking.
Type two or more characters of the venue name and suggestions from registered venues appear with their addresses. Picking one fills in the venue name and sets the region automatically from its address (editing the name by hand drops the link to that registered venue).
RegionChoose a prefecture. The helper text under the field reads "Used for area filtering on Home". Set it so participants can find you (default is Tokyo).
Event date, start, endThey sit on one row. All three are required when publishing (the end time is used to judge auto-ending).
They can be left blank when saving a draft.
Parts to recruitRecruit per part. One row per part, with the numbers in this order: Part / Capacity / ② Initial / ③ Join / ④ Free (see "Numbers for parts wanted"). Add more with "+ Add part", remove a row with the ✕ at its end.
Prepared songsYou can prepare songs to be played in advance (see "Prepared songs" below).
Status on publishChoose Pre-announcement or Recruiting. Pre-announcement = not yet accepting applications, just putting the announcement out first. Recruiting = accepting applications the moment it's published.
"Draft" doesn't appear here. Drafts are handled with the "Save draft" button. When you edit an already-published session, this field and "Song request stage" below are hidden (so that progress isn't rolled back).
Start recruiting automaticallyA checkbox that appears only when you choose "Pre-announcement". Tick it and a date/time box appears right beside it; the session switches to "Recruiting" automatically at that moment.
There is no field called "Recruiting start time". The date/time you set here is the same one as the "Date/time" of ① Members only in the "Song request stage" table below.
Song request stageChoose which song stage to start from when publishing: Members only / Initial song requests / Join requests / Fully open — four cards on wide screens, a dropdown on narrow ones. While the publish status is "Pre-announcement" this field can't be chosen — it shows "Not accepted during pre-announcement. You can choose once published as Recruiting." Just below it sit the three rows "Enabled / Auto advance / Date/time" (see "Song request stages & flow" for details).
Recruitment deadlineThe date and time when member recruitment closes automatically (it sits between "Song request stage" and "Cancellation deadline"). Tap the box and you pick a date, then a time. The on-screen helper reads "Member recruitment closes automatically at this time. Leave it empty to keep recruiting until the start time."
While unset it shows a faint "No date/time set". Once a time is in, an ✕ ("Clear the recruitment deadline") appears at the right, so you can empty it again at any time. It can also be edited after the session is published (you can add or drop just the deadline later). Once recruitment is closed, new applications go to the waitlist. This setting is independent of the song stages.
Cancellation deadlineThe deadline for participants to cancel. Pick one of four: Until start time (the default) / Until 12 hours before / Until 24 hours before / Until 48 hours before. You can't enter an arbitrary number of hours.
Show participant list publiclyA switch for whether participants can see the list of each other. On (public) by default. Turn it off and the participant list on the session details is shown only to the host and co-hosts (hosts always see it, labelled "Private (hosts only)").
Linked sessionsAppears only on the edit screen (when creating, neither session has a number yet). This is where you tie editions of a recurring event together (see "Grouping recurring sessions" below).
Make this session privateLink-only access. When turned on, the session does not appear on Home or in search results, and a "Private" badge is shown on the details screen. The session URL (e.g. …/sessions/12345678) is shown to the host and co-hosts for every session, and only people who receive it can open a private one. Applications and the session flow work as usual.
Fee, tax incl., notesThey sit on one row: the fee (yen only for now), the "Tax incl." checkbox (on by default), and supplementary notes. If free, leave the fee blank and it shows "Free" (notes also appear in the list's "Fee notes" column).

Numbers for parts wanted (people count and song count)

A single part row lines up numbers with different meanings. They're easy to mix up, so here's a breakdown. The headers read, from the left, Part / Capacity / ② Initial / ③ Join / ④ Free, and the ②③④ numbers correspond to the stages of the "Song request stage" (the parts table on the session details has different columns: Part / Openings / Request limit).
On narrow screens (phones and the like), the units after each number ("people" / "songs") are dropped and only the digits are shown. Check the table headers to see which number is which.

NumberMeaning
CapacityThe capacity for advance applications (default 5 people per part). Separate from the number of slots on the jam board during the session (on the day, part slots are created per song).
② InitialThe number of songs a person on that part can put forward during "Initial song requests". To prevent an over-emphasis on vocal numbers, Vocal is lower (default 2 songs) and the rest are higher (default 5 songs).
③ Join / ④ FreeThe upper limit on songs one person can join (cumulative). Settable separately for the Join and Fully-open stages. Both can be left blank, and blank means unlimited. Only the defaults differ: ③ Join starts at the same number as ② Initial, and ④ Free starts blank (unlimited).

Prepared songs

The host can register songs to be played on the day in advance.

  • Add by entering the song title and artist name (both show suggestions from two characters on; picking a song title fills in the artist too). The part lineup is the same as the parts wanted above.
  • The host can add or delete anytime, regardless of the session's status or the song stage.
  • Once registered, a song's title and artist can't be changed (changing them would throw off the ranking tally). To fix them, delete and re-add.
  • This field has no "Reference URL". To attach one, add the song from "Add song" on the session details or "+ Request a song" on the jam board instead (→ Reference URLs).
↑ Back to top
05

Session status

A session moves through the following states from creation to ending.

Draft Announced Recruiting Live Finished

※ You can move to "Canceled" from any stage.

StatusMeaningTrigger to advance
DraftJust saved. Not visible to anyone yet."Publish" → Announced / Recruiting
AnnouncedJust the announcement is public. Not yet accepting applications.Auto-switches to "Recruiting" at the date/time set under "Start recruiting automatically" (can be turned off)
RecruitingAccepting applications to join.Auto-switches to "Live" at the start time
LiveThe day itself. The jam board is available.The host presses "End" / auto-ends 24 hours after the end time
FinishedAfter the session. View-only, records are kept.Within 24 hours, the host can revert it with "Revert to ongoing"
CanceledCalled off. Enter a reason and all participants are notified. It stays in the list.
State changes are basically automatic at the times you set, but the host can also advance them manually by watching how the day goes (next chapter, "Running the session").
↑ Back to top

← Previous: Help and glossary ・ Back to contents ・ Next: Hosting: running the session →

Open the app