Skip to main content

PNM public apply page

The Public Application Page card under Org → PNM → Settings is where you set the URL applicants visit to apply, the welcome content they see when they arrive, and the thank-you message they see after submitting. This is the most visible piece of PNM configuration — the URL ends up on flyers, in Instagram captions, and in chapter outreach emails.

The apply URL​

Your org's public apply URL has the shape:

https://[your-app-domain]/apply/[your-org-slug]

The host portion is your GreekManage app domain (the same domain you use to log in). The path portion is /apply/ followed by your org's slug. There is no custom-domain support today — the apply page lives under your GreekManage host, not under a domain you control.

The slug is set on this card. The full URL is displayed read-only at the top of the card with a one-click Copy action so you can paste it into outreach materials without typing it.

PNM settings - Public Page card with copy button PNM settings - Public Page card with copy button

Setting the slug​

The slug is a short, URL-safe identifier — lowercase letters, numbers, and hyphens. Common picks: your chapter or org name in kebab-case (sigma-phi, alpha-chi-omega), an abbreviation (apo, dst), or the historical Greek-letter shorthand.

To set or change the slug:

  1. Open Org → PNM → Settings → Public Application Page.
  2. Edit the Slug field.
  3. Click Update.

The slug is validated server-side for uniqueness across the platform — two orgs cannot share a slug. If you pick a slug that's already taken, the field returns an error and the change is not saved. Try a different value.

The slug is the same slug used by other public surfaces in your org (any future public page that needs a stable per-org identifier reuses it). Changing it changes those URLs too, not just the apply URL.

Why changing the slug is a big deal​

Once your apply URL is in the wild, changing the slug breaks every link people have — printed flyers, outreach emails, social captions, and saved bookmarks all stop resolving. Reference letter invitations already in flight still work, since those use their own token-based URLs, but everything else breaks. Pick a durable slug and keep it. The least bad time to change is at the start of a recruitment cycle before you've publicized the URL; the worst time is mid-cycle. If you absolutely must rename mid-cycle, plan to repost the URL everywhere the same day.

Welcome markdown​

The Welcome / instructions Markdown field renders above the application form on the public page. Standard Markdown — headings, paragraphs, bold and italic, lists, links, blockquotes — renders correctly. Embedded HTML beyond the basics, images, and tables are not rendered and are treated as raw text.

A good welcome message answers, in three to five lines, who you are, what recruitment looks like at your org this cycle, what the applicant should expect after submitting, and where to ask questions if they run into trouble. Keep it short — applicants drop off long welcome blocks.

Thank-you markdown​

The Thank-you message Markdown field renders on the success screen after a successful submission. Same Markdown rules as the welcome message.

A good thank-you message:

  • Confirms that the submission succeeded (the applicant just clicked Submit, so this is reassuring)
  • Tells them what happens next ("A chapter officer will reach out within 5 business days")
  • If email verification is on, mentions the next step ("Check your email for a verification link")
  • If reference letters are required, mentions that referrers will receive emails shortly

The thank-you message is shown only on the success screen. The applicant's confirmation email uses a separate template; don't try to put email-only content in the thank-you markdown.

How a closed period renders​

When no period is currently active for your org — either because every period is in Draft, every period is in Closed, or the current time is outside the open/close window of every Active period — the public apply page renders a closed state instead of the form.

The closed state shows:

  • Your org name, logo, and primary color from your branding
  • The configured welcome Markdown
  • A closed message drawn from the most recently closed period's closed_message_markdown field (set when you configured the period)
  • No form, no submit button

If you've never created a period, or the most recent closed period has no closed message configured, the visitor sees a minimal "applications are not currently open" placeholder. Set the closed message field on each period as you close it (or in advance) to give applicants useful context — when the next period will open, who to contact, where to follow your org for updates.

How a not-yet-opened period renders​

A period in Active status whose open date is in the future is treated as not-yet-open: the public apply page renders the same closed state described above. The applicant cannot submit, even though there is an active period configured.

To go live, ensure your active period has an open date in the past (or no open date, which means "open whenever the period is active"). See PNM periods for the lifecycle.

Custom domain support​

There is no custom-domain support for the apply page today. The URL is always https://[your-app-domain]/apply/[your-org-slug]. If your org wants to publish a branded URL like apply.yourorg.org, the only path is a redirect at your DNS or web layer that points to the GreekManage URL — outside the platform.

This is on the planned list for a future release. There is no committed timeline.

What's on the page beyond your configuration​

Beyond the welcome Markdown and the form, the public apply page renders your org name and logo (from Branding), the chapter selector listing every active chapter in alphabetical order, attachment uploaders, reference letter referrer slots, consent sections, a Cloudflare Turnstile bot-detection challenge if your platform admin has configured one, and the submit button. None of these are individually configurable beyond what their respective settings cards expose. The order is fixed.

Brand and styling​

The apply page picks up your org's logo, primary color, and other branding from the org-level branding settings (Branding). There is no separate apply-page-only theme. If you want the apply page to look different from the in-product experience, change the org-level brand color — that's the only customization knob.

Last verified against v0.62.1 (2026-05-10).