Skip to content

Organizer

Ghiță has organized seven hikes through Terranos this year. He has a mental shape for what works: pick the route, set the meeting point at a place that's easy to find without GPS, set capacity at 8 (anything bigger turns into a parade), require approval if it's a technical trip, save it as a template if he wants to run it again next year.

This page is for the people doing what Ghiță does.

Who can organize

Anyone with an account. There's no application, no pre-approval, no "organizer level". You tap Create activity and you're organizing that activity.

That said, your participants will look at your profile before they join. If you're brand new, expect smaller turnouts at first. The review average builds up over a few activities.

Creating an activity

From the home shell, tap Create activity. The form is split into sections so you can fill it in over multiple sittings — drafts save automatically.

Required fields:

  • Title — short, descriptive. "Bucegi via Babele, moderate, 1 day" beats "Mountain trip".
  • Date and time — start time at minimum. End time helps the participants plan their day.
  • Meeting point — pick a place name that's findable. The map picker accepts a tap, an address, or a long-press for exact coordinates.
  • Difficulty — 1–6, see Activity details for the canonical scale.
  • Capacity — maximum participants. Set it deliberately; "10 people on a ridge" is different from "10 people on a beginner walk".

Optional but useful:

  • Description — what's the trip about, what's the route, what should people expect. Markdown is allowed; line breaks become real line breaks.
  • Image — a photo of the area. Doesn't have to be from the exact spot, but should set the tone.
  • Approval required — flip on if you want to vet participants.
  • Minimum participants — the activity won't run if fewer than this number sign up by the deadline.
  • Decision deadline — when the minimum-participants check happens.
  • Costs — split into transport, rental/equipment, and other.
  • Equipment requirements — items mandatory or recommended for the trip. See Equipment.
  • Tags — searchable labels. See Search.

When you're ready, tap Publish. Until then it's a draft, visible only to you.

Multi-day activities

Toggle Multi-day in the form. The schedule section expands into per-day cards: each day gets its own meeting point, time, and (if you want) its own capacity.

Multi-day participants can join the whole trip or only specific days. Plan accordingly:

  • A 3-day Făgăraș with capacity 6 per day is a different beast from a 3-day Retezat where day 2 caps at 4 because of a technical section.
  • The transport and equipment boards behave per-day.

Templates

Ran something good and want to run it again? Tap Save as template on a finished activity. Templates live in Profile > Templates. To re-run, open the template and tap Use as new activity — it opens the create form pre-filled with the template's values, and you edit only what's different (date, capacity, etc.).

Editing the template after creating an activity from it doesn't affect the activity. The two are decoupled by design.

Managing participants

Open your activity and tap Manage participants (or open Events > Organizer > [your activity]).

For each request you can:

  • Approve — they become a participant. They get notified.
  • Reject — their request is closed. They get notified.
  • Wait — leave them pending. You'll come back to it.

You can also remove an already-approved participant if you have to (no-show, behavior issue, etc.). Removed participants are notified and can re-request only if you allow it.

Cancelling an activity

Cancel activity lives in the activity action menu. Confirming it:

  • Sets the activity to cancelled.
  • Notifies all participants and waitlisted users.
  • Releases all transport seats.
  • Closes the per-activity discussion thread to new posts (history remains).
  • Removes the activity from Discover (the page still resolves but shows a cancelled banner).

If you might run it on a different date, Reschedule is a better option than cancel — it edits the date in place and notifies participants. They can confirm or drop their participation based on the new date.

Marking the activity completed

After the activity ends, the page shows Mark completed. This:

  • Sets the activity status to completed.
  • Lets you confirm participation: who showed up (completed), who didn't (noShow).
  • Opens the reviews window for participants you marked completed.

This is also when the analytics tab on the activity page populates with final numbers.

Financial view

Organizer > Financial shows the cost breakdown for each activity you organized:

  • Total cost vs. participant share.
  • Per-pickup-point cost split for transport.
  • Pending vs. settled allocations (informational — Terranos doesn't process payments).
  • CSV export for your own records.

See Costs and financial summary for the full picture.

Analytics

Each activity you organize has an Analytics tab on its details page (visible only to you and admins). It shows:

  • View count over time.
  • Join rate (people who tapped Join / people who viewed).
  • Cancel rate (cancellations / approved participants).
  • Average rating once reviews start landing.
  • A bar chart of registrations over time, useful for understanding when interest peaks.

Don't read too much into a single activity. Patterns across several activities are more useful — for example, "evening posts get more engagement than morning posts for me".

When something looks off

  • Publish button is greyed out. A required field is empty. The form scrolls to the missing field on the first publish attempt.
  • A draft disappeared. Drafts auto-save on every change but can be lost if you uninstalled and reinstalled the app, since they live in local storage. There's no server-side draft until you publish.
  • A pending request you approved still shows pending. A sync glitch. Pull to refresh; if it persists, the request might have been cancelled by the participant before your approval landed.
  • Analytics numbers look stuck at zero. Analytics start populating after the activity has been viewed by signed-in users. A brand-new activity with no traffic yet shows zeros — that's correct.