Ascend Documentation

Appearance

Publishing & Sharing ​

Take an event type from draft to live, and get the link in front of the right people.

Quick Start ​

  1. In the event-type designer, click Publish in the toolbar.
  2. Resolve any items shown in the readiness checklist (the Publish button is disabled until they pass).
  3. Click View to open the public booking page in a new tab.
  4. Click Sharing tab to copy the URL or grab the embed snippet.

The Draft / Published Snapshot Model ​

Every event type has two states:

  • Draft — what you see in the editor. Changes auto-save here.
  • Published snapshot — a frozen JSON copy of the event type that the public page reads.

Editing the draft never changes the published snapshot. The public page keeps showing the previous version until you publish again. This is the right behaviour for most use cases — you don't want a half-edited event type going live mid-edit.

Edits don't show until you Publish changes

After your first publish, the toolbar shows two buttons: Publish changes (re-freezes the latest draft) and Unpublish (drops back to draft, taking the public URL offline). Click Publish changes to push your edits live.

Publish Readiness Checklist ​

The Overview tab shows a checklist of everything that must be true before the event type can publish:

CheckWhat it requires
TitleNon-empty.
DurationGreater than 0.
At least one hostThe Hosts tab must have at least one named host or a non-empty pool.
AvailabilityAt least one weekly window or future override.
Calendar connected (warning)A connected calendar is recommended but not required — without one, Ascend can't detect conflicts with your other meetings.
Custom questionsOptional, but if you've added them, every required field must have a label.
PaymentsIf "Charge for this event type" is on, a price + currency are set, and Stripe is connected.

Anything in red is failing — clicks the row to jump to the offending tab. Anything yellow is a warning — publish still works.

Publish, Unpublish, Discard ​

ActionWhat happens
Publish (initial)Snapshot the current draft. Status → Published. Public URL → live.
Publish changesRe-snapshot with the latest draft edits. Public URL serves the new snapshot immediately.
UnpublishStatus → Draft. Public URL returns 404. Snapshot is kept (republishing is one click).
DiscardThrows away the current unpublished edits. Reverts the editor to the published snapshot.
CloseStatus → Closed. Like unpublish but explicit "we're done with this" — keeps it in history without cluttering the active list.

The Public URL ​

Every event type has a slug — an opaque 12-character code (e.g. B1AI7BXGdOQM). The public URL is:

https://your-team.ascend.app/b/{slug}

The slug is auto-generated and not derived from your title. This means:

  • It's not guessable — competitors can't enumerate /b/discovery-call, /b/sales-intro, etc.
  • It doesn't change when you rename the event type (existing links keep working).
  • Slug editing is planned for Phase 2.

The "Private" Toggle ​

On the Overview tab. When Private is on:

  • The event type is hidden from the team's /booking index page.
  • Direct-link bookings still work — the public URL is unchanged.

Use it for "secret" booking links you only share by email or via a routing form, without exposing them on a public list.

Embedding ​

To drop the booking page into your own website (so the booker stays on your domain):

  1. Sharing tab → Embed code section.
  2. Pick a width / height (defaults are 100% × 700px).
  3. Copy the iframe snippet.
  4. Paste into your site's HTML.

The iframe auto-resizes to its content — the booker doesn't see scrollbars on the embed.

html
<iframe
  src="https://your-team.ascend.app/b/B1AI7BXGdOQM?embed=1"
  width="100%"
  height="700"
  frameborder="0"
></iframe>

The ?embed=1 query strips the page chrome (header, host bio fold) so it sits cleanly inside your site's design.

Sharing the Designer (Internal) ​

The event-type designer itself supports share-link collaboration like Pages and Databases. Click Share in the top-right of the designer to invite teammates with view or edit access. Useful for getting marketing to review the copy without giving them admin on your team.

Every confirmation email includes two tokenised links:

  • /b/cancel/{token} — booker self-cancels (subject to your refund policy).
  • /b/reschedule/{token} — booker picks a new slot.

Tokens are single-use-style: cancelling the booking invalidates the cancel token; rescheduling issues a new token for the new booking.

The host can also cancel or reschedule from /calendar → click the booking → action buttons in the side sheet. No token needed for host actions.