> ## Documentation Index
> Fetch the complete documentation index at: https://docs.playaos.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Customize your camp's branding and portal settings

> Configure your camp's display name, contact email, Givebutter URL, social links, custom domain, kitchen features, and CMS-managed content.

Your camp's branding settings control how PlayaOS presents itself to applicants and members — from your name in every email subject line, to the copy on your application wizard, to whether the kitchen and dietary features show up in the portal. Most changes take effect immediately across the entire portal.

<Note>
  Changes to your branding appear everywhere at once: the portal header, login page, all transactional emails, and member-facing pages. Review your changes before saving if you have active applicants or members in the portal.
</Note>

## Camp name and identity

Navigate to **Settings → Branding** in your portal admin.

**Camp display name** — Your full camp name as it appears in the portal header, page titles, and email headers (e.g., `BRC Pickleball Club`). Update this any time your official name changes.

**Short name** — A condensed version used in email subject lines and notification prefixes (e.g., `BRC Pickleball`). Keep it recognizable but brief.

**Camp type descriptor** — A short phrase used in meta titles and certain page headers to describe what kind of organization you are (e.g., `Burning Man Theme Camp`). This doesn't affect any functional behavior — it's display only.

## Contact and email addresses

**Contact email** — The reply-to address on outgoing emails. When a member replies to a notification, their message goes here. Use a monitored inbox your admin team actually checks.

**From email (reply-to)** — The sending address on all transactional emails from your portal. This should be an address associated with your camp's domain or one you control.

<Tip>
  If you're using a custom domain (Camp or Network plan), configure your from email to match that domain. A matching from address improves deliverability and looks more professional to applicants.
</Tip>

## Dues payment link

**Givebutter URL** — Paste your Givebutter campaign or fund URL here. This link powers the "Pay dues" button in the member portal. Members click through to your Givebutter page to complete payment.

If you haven't set up your Givebutter campaign yet, see [Payment integration](/setup/payment-integration) for step-by-step instructions. Leave this field blank until you're ready — the dues button won't appear in the portal without it.

## Social links

**Instagram handle** — Enter your camp's Instagram username without the `@` (e.g., `campwanderlust`). This populates social links in the portal footer and any pages that reference your social presence.

## Custom domain

<Info>
  Custom domain support is available on the **Camp** and **Network** plans. On the Free plan, your portal is only accessible at `yourslug.playaos.app`.
</Info>

If you want your portal to be reachable at a domain you own (e.g., `portal.yourcamp.com`), go to **Settings → Branding → Custom domain**:

1. Enter the domain or subdomain you want to use.
2. Follow the DNS configuration instructions shown — you'll need to add a CNAME record pointing your domain to PlayaOS.
3. Once DNS propagates (usually within a few minutes to an hour), your portal will be accessible at your custom domain.

Your camp subdomain at `yourslug.playaos.app` continues to work after you add a custom domain.

## Kitchen and meals features

If your camp runs a communal kitchen, PlayaOS includes dietary preference collection, daily headcounts, and meal-related shift types. If your camp doesn't offer meals, you can hide all of this to keep the portal focused.

Go to **Settings → Features** and toggle **Camp offers meals** on or off. When off:

* Dietary restriction fields are hidden from the application form
* Meal-related shift types are not shown
* The kitchen headcounts view is removed from the admin panel

You can flip this toggle at any time. Existing dietary data is retained — it just won't be visible while the feature is off.

## Important dates

Navigate to **Settings → Dates** to manage your camp's timeline — dues deadlines, ticket cutoffs, gate-open dates, burns, document deadlines, and any other milestone. Dates you add here power the dashboard **Next Up** card, the member [Important Dates](/members/important-dates) page, and the event-date constraints used by the [shift calendar](/admins/shifts-scheduling).

### Fields on each date

| Field                | Required       | Description                                                                                                               |
| -------------------- | -------------- | ------------------------------------------------------------------------------------------------------------------------- |
| Title                | Yes            | Short label shown on cards and badges (up to 100 characters)                                                              |
| Start date           | Yes            | The first day the date applies, in `YYYY-MM-DD` format                                                                    |
| End date             | No             | Optional last day of a multi-day window. When set, must be on or after the start date. Leave blank for a single-day date. |
| Category             | Yes            | One of `dues`, `documents`, `tickets`, `event`, `other`, or `system` — controls the color-coded badge and sort order      |
| Remind (days before) | No             | Comma-separated list of lead times (e.g. `7, 3, 1`) for future reminder notifications                                     |
| Description          | No             | Optional extra context shown under the date card (up to 500 characters)                                                   |
| Visible to members   | Yes (checkbox) | When checked, the date appears on the member Important Dates page. Uncheck to keep a date admin-only while you plan it.   |

### Date categories

| Category    | Typical use                                                                                                                                                        |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `dues`      | Payment-related deadlines such as early-bird tier cutoffs                                                                                                          |
| `documents` | Waivers, releases, and other signature deadlines                                                                                                                   |
| `tickets`   | Ticket sale, transfer, or exchange windows                                                                                                                         |
| `event`     | Gate open, burns, exodus — also used to constrain the shifts calendar                                                                                              |
| `other`     | Miscellaneous dates that don't fit another category                                                                                                                |
| `system`    | Automated dates generated by PlayaOS (for example, tier cutoffs derived from plan settings). Shown in a separate **System-managed Dates** table on the admin page. |

### Visibility toggle

Each date has an independent **Visible to members** switch:

* **On** — the date appears on the member Important Dates page and is eligible for the dashboard Next Up card.
* **Off** — the date is still tracked internally and shown on the admin Settings → Dates page, but members won't see it.

<Tip>
  Use the visibility toggle to stage dates ahead of a public announcement. Add the date now with visibility off, then flip it on when you're ready to tell members.
</Tip>

## CMS-managed content

PlayaOS uses [Storyblok](https://www.storyblok.com) to manage certain content blocks that camps commonly need to customize: the login page copy, your public landing page, the text shown on each step of the application wizard, and the base layout of outgoing emails.

To edit this content, you'll need access to your camp's Storyblok space. Contact your PlayaOS account administrator if you don't have access.

<Tabs>
  <Tab title="Login page">
    The login page copy — including the headline, subheading, and any camp-specific welcome text — is managed in Storyblok under the **Login** story. Changes publish immediately to your portal.
  </Tab>

  <Tab title="Application wizard">
    Each step of the application wizard has its own Storyblok story (Apply step 0 through Apply step 5, plus the status and signup pages). Edit the intro copy, instructional text, and acknowledgment language for each step here.
  </Tab>

  <Tab title="Email templates">
    Transactional email copy — body text, sign-off, footer links — is managed in Storyblok under **Email base** and individual email template stories. The from name and contact email still come from your branding settings, but the editorial content lives in Storyblok.
  </Tab>

  <Tab title="Landing page">
    Your camp's public landing page copy (title, subtitle, and feature bullets) is managed in Storyblok under the **Landing** story. This is what prospective applicants see before they start their application.
  </Tab>
</Tabs>

<Note>
  If a Storyblok story is empty or your Storyblok space isn't configured, PlayaOS falls back to your branding settings. Your portal will always display your camp name and contact info — it just won't show any custom editorial copy.
</Note>