# Assigning dues
Source: https://docs.rowhouse.co/dues/assigning-dues
Assign dues to members with amount, due date, and optional group
Assign dues to one or more members so they owe an amount and can pay via their [pay link](/dues/pay-link).
## Assign dues
1. Go to **Finance** → **Dues** and click **Assign dues** (or **New assignment**).
2. **Select members**: Choose one or more members (or a [group](/groups/overview) if the UI supports it).
3. **Amount**: Enter the amount (e.g. 50 for \$50). Amount is usually in dollars; the app may store in cents internally.
4. **Description** (optional): e.g. "Fall 2025 dues" or "Event fee".
5. **Due date** (optional): When the dues are due. Used for display and overdue reminders (if enabled).
6. **Dues group / option** (optional): If you use [dues groups](/dues/dues-groups), select a group and optionally an option (tier). The amount can be set from the option or overridden.
7. Submit. Assignments are created; each member gets a unique [pay link](/dues/pay-link).
For many members at once, select multiple members in one go or use a group. You can assign the same amount and description to all of them.
## After assigning
* Each assignment appears in the Dues list with status **unpaid** until the member pays. Share the **pay link** with each member (by email or copy link).
* You can [waive](/dues/waiving-and-cancelling) or cancel an assignment if needed. You can also [edit due date](/dues/due-dates) or description on the assignment if the UI allows.
## Amount and currency
* Amount is typically in **dollars** (e.g. 50 = \$50). Currency is usually USD unless your org uses another. Processing fees may apply; see [Processing fees](/finance/processing-fees).
# Due dates
Source: https://docs.rowhouse.co/dues/due-dates
Set and use due dates for dues assignments
You can set an optional **due date** on each dues assignment. Use it for display, reminders, and filtering (e.g. overdue).
## Set a due date
* When [assigning dues](/dues/assigning-dues), enter a **Due date** (e.g. September 15, 2025). The assignment stores it and may show it on the pay page and in the Dues list.
* You can often edit the due date later by opening the assignment and changing the date field.
## How due dates are used
* **Display**: The member may see "Due by \[date]" on their pay page. The Dues list may show due date per row.
* **Overdue**: The app may mark assignments as **overdue** when the due date has passed and status is still unpaid. You can filter or sort by overdue to follow up.
* **Reminders**: If your plan supports dues reminders, they may be sent based on due date (e.g. a few days before or after). Check Reminders or Email settings for dues.
Due date does not automatically block payment after the date. Members can still pay after the due date unless you cancel or waive the assignment.
## Change or remove due date
* Edit the assignment and set a new due date or clear it. Saving updates the record. Reminders (if any) may use the new date on the next run.
# Dues groups
Source: https://docs.rowhouse.co/dues/dues-groups
Create dues groups with options and block content for the pay page
A **dues group** (type "dues") is a named set of dues options and optional block-based content. You use it when [assigning dues](/dues/assigning-dues) so members see a clear label and the right amount (and a custom pay page if you add content).
## What is a dues group?
* **Name** and **slug**: e.g. "Fall 2025 Dues", slug `fall-2025-dues`. The slug is used in URLs (e.g. pay page or store).
* **Type**: "dues" (for dues; "merch" is for [merch](/merch/overview)).
* **Default amount**: Optional default (e.g. \$50) used when you assign without picking an option.
* **Options**: [Dues group options](/dues/assigning-dues) (e.g. "Standard - $50", "Early bird - $40"). When assigning, you can pick an option so the member gets that amount.
* **Content**: Optional block-based (Puck) content shown on the pay or info page for this group.
## Create a dues group
1. Go to **Finance** → **Dues** (or **Dues groups**) and click **Create dues group** (or **New group**).
2. Enter **name** and **slug** (lowercase, letters, numbers, hyphens). Slug must be unique per org.
3. Set **type** to **dues**.
4. Optionally set **default amount** and add **options** (label + amount per option).
5. Optionally add **content** (blocks) for the pay page. Save.
Use one dues group per "campaign" (e.g. semester or year) so you can filter and report by group. Options can represent tiers (e.g. early bird vs standard).
## When assigning dues
* When you [assign dues](/dues/assigning-dues), you can optionally select a **dues group** and an **option**. The member's assignment is linked to that group/option and the amount comes from the option (or default). The member may see the group name and content on their pay page.
## Edit or delete
* **Edit**: Change name, slug, default amount, options, or content. Existing assignments keep their amount; new assignments use the updated data.
* **Delete**: Deleting a dues group may unlink it from assignments (assignments keep their amount but no longer reference the group). Check the app before deleting; you may not be able to delete if assignments exist.
# Ledger
Source: https://docs.rowhouse.co/dues/ledger
View ledger entries for dues payments and balance
The **ledger** records financial activity: dues payments, event payments, merch sales, and sometimes payouts. You can use it to see balance over time and audit what was paid and when.
## Where to find the ledger
* **Finance** → **Transactions** or **Ledger** (or **Dues** with a ledger view). The exact location may vary; look for a list of transactions or ledger entries with date, description, amount, and balance.
## What appears in the ledger
* **Dues payments**: When a member pays a dues assignment, a ledger entry is created (amount, member, assignment reference, date). Your org's **balance** (or Stripe balance) increases by the amount minus fees.
* **Event and merch**: Payments from events and [merch](/merch/overview) may also create ledger entries so you see a unified view of money in.
* **Payouts**: When you receive a [payout](/finance/payouts) to your bank, an entry may show money out (or a reduction in balance). See [Finance overview](/finance/overview).
Ledger detail (per-assignment, per-event, balance calculation) depends on your app. Use it to reconcile with Stripe or your bank and to answer "who paid what when."
## Filter and export
* Filter by date range, type (dues vs event vs merch), or member. Export to CSV if the UI allows for your own records or accounting.
# Dues overview
Source: https://docs.rowhouse.co/dues/overview
Assign dues, track payments, and manage the ledger
**Dues** (Inflow) let you assign amounts to members, send pay links, and track who has paid. You can use **dues groups** for recurring dues (e.g. semester dues) with options and custom content.
## What you can do
* **Assign dues**: Choose members and assign an amount (and optional due date, description). Optionally link to a [dues group](/dues/dues-groups) and option (e.g. tier).
* **Pay link**: Each assignment has a **pay link** you share with the member. They enter payment details and pay; status updates to paid.
* **Ledger**: View a [ledger](/dues/ledger) of dues payments and balance.
* **Waive or cancel**: [Waive](/dues/waiving-and-cancelling) or cancel an assignment when needed.
* **Dues groups**: Create [dues groups](/dues/dues-groups) (e.g. "Fall 2025 dues") with options (tiers) and block-based content for the pay page.
## Dues dashboard
* Open **Finance** → **Dues** in the sidebar to see assignments: member, amount, status (unpaid/paid), due date. Filter and export as needed. Create new assignments or open existing ones to copy the pay link or waive.
Dues (and Finance section) may require a **paid plan**. See [Plan limits](/guides/plan-limits) and [Subscription](/settings/subscription).
## Related
* [Dues groups](/dues/dues-groups) and [Assigning dues](/dues/assigning-dues)
* [Pay link](/dues/pay-link), [Due dates](/dues/due-dates), [Waiving and cancelling](/dues/waiving-and-cancelling), [Ledger](/dues/ledger)
* [Troubleshooting](/dues/troubleshooting)
# Pay link
Source: https://docs.rowhouse.co/dues/pay-link
Share the dues pay link so members can pay online
Each dues assignment has a **pay link**: a unique URL the member opens to enter payment details and complete payment. After they pay, the assignment status becomes **paid**.
## Get the pay link
1. Go to **Finance** → **Dues** and open the assignment (or find it in the list).
2. Copy the **pay link** (e.g. **Copy link** or a URL like `rowhouse.co/dues/[duesId]/pay`). The link is unique per assignment and usually does not expire.
3. Share it with the member by email, text, or your preferred channel.
Send the link in an [email](/emails/overview) or include it in a template (e.g. "Pay your dues: ") so each member gets their own link. Do not post the same link publicly if each link is tied to one assignment.
## What the member sees
* They open the link and see the **amount**, **description**, and (if set) **due date** and [dues group](/dues/dues-groups) content.
* They may need to enter **name**, **email**, **phone** (for first-time or guest payers). If they are already a member, their info may be pre-filled or updated on payment.
* They enter **card** details (Stripe). After success, they see a **success** page and the assignment is marked **paid** in your Dues list. You can see the payment in [Transactions](/finance/transactions).
## Success page
* After payment, the member is redirected to a **success** URL (e.g. `rowhouse.co/dues/[duesId]/success`). You can mention this in your email so they know payment went through.
## If the link does not work
* Confirm the assignment still exists and was not deleted or cancelled. See [Troubleshooting](/dues/troubleshooting). If the member already paid, the link may show "already paid" or similar.
# Dues troubleshooting
Source: https://docs.rowhouse.co/dues/troubleshooting
Fix pay link, payment not reflecting, and duplicate charges
Common issues with dues assignments and payments.
## Pay link broken or not loading
* **Assignment exists**: Confirm the assignment was not [cancelled](/dues/waiving-and-cancelling) or deleted. If it was, create a new assignment and share the new pay link.
* **Already paid**: If the member already paid, the link may show "already paid" or redirect to success. Check the Dues list; if status is **paid**, no further action is needed.
* **URL**: Ensure you copied the full link (e.g. `https://rowhouse.co/dues/[id]/pay`). Missing protocol or truncated URL can cause errors. Have the member try again in a different browser or device.
* **Stripe**: Payments require [Stripe Connect](/getting-started/stripe-connect) to be complete. If Connect is incomplete, pay links may fail. Complete onboarding and try again.
## Payment not reflecting (still shows unpaid)
* **Wait**: After the member pays, status can take a few seconds to update. Refresh the Dues list or open the assignment again.
* **Webhook**: Rowhouse updates status when Stripe sends a successful payment webhook. If Stripe had an outage or the webhook failed, status might be delayed. Check **Finance** → **Transactions** to see if the payment appears there; if it does, the assignment may sync later or support can fix the status.
* **Wrong assignment**: Confirm the member used the link for *this* assignment. If they paid a different assignment or an event, that payment will not mark this dues assignment as paid.
## Duplicate charges
* **Member paid twice**: If the member clicked Pay twice or used the link twice, they might have been charged twice. Check **Transactions** for two payments for the same amount and same member around the same time. Refunds must be done in Stripe (or your process); then you can [waive](/dues/waiving-and-cancelling) or cancel one of the assignments so records match.
* **Duplicate assignments**: If you accidentally created two assignments for the same member and same dues, waive or cancel one and share only one pay link going forward.
## Member cannot pay (card declined, error)
* **Card**: The member should try a different card or contact their bank. Rowhouse does not control card declines.
* **Amount**: Ensure the amount is correct and in the expected currency. Very small or zero amounts may be rejected by Stripe.
* **Browser**: Try another browser or device; clear cache and disable extensions that might block Stripe.
## Plan and access
* **Dues section locked**: Finance/Dues may require a **paid plan**. See [Subscription](/settings/subscription) and [Plan limits](/guides/plan-limits). Upgrade to unlock.
* **No pay link**: Only admins (or users with permission) can see and copy pay links. If you are a member, ask an admin to send you the link.
# Waiving and cancelling dues
Source: https://docs.rowhouse.co/dues/waiving-and-cancelling
Waive, cancel, or adjust a dues assignment
You can **waive** (set to no payment required), **cancel** (void the assignment), or in some cases **adjust** the amount or details of a dues assignment.
## Waive
* **Waive** means the member is not required to pay. The assignment may be marked "waived" or "paid (waived)" so it no longer shows as unpaid. Use for scholarships, comps, or one-off exceptions.
* How to waive: Open the assignment in **Finance** → **Dues** and use **Waive** (or edit and set status/amount to waived). Save. The member will not see a balance due; the pay link may show "waived" or similar.
## Cancel
* **Cancel** means the assignment is voided. The member no longer owes it. Use when the assignment was created by mistake or the member is no longer expected to pay (e.g. left the org). Cancelling does not refund a payment already made; it only stops future payment.
* How to cancel: Open the assignment and use **Cancel** (or delete). Confirm. The assignment may be hidden or shown as cancelled in the list.
If the member already paid and you cancel, you may need to handle a refund separately (e.g. via Stripe or your process). Cancelling in Rowhouse does not automatically refund.
## Adjust amount or details
* Some UIs let you **edit** the assignment: change amount, due date, or description. Use this to correct errors before the member pays. After they pay, changing the amount does not change what they paid; contact support if you need to refund and reassign.
## Bulk waive or cancel
* If the app supports it, select multiple assignments and use **Waive** or **Cancel** in bulk. Otherwise, waive or cancel one by one.
# Campaigns (sent history)
Source: https://docs.rowhouse.co/emails/campaigns
View sent emails, status, and open tracking
**Campaigns** (or **Sent** / **Sent emails**) is the history of emails you have sent. You can see which draft was used, who received it, delivery status, and (if enabled) who opened it.
## View campaigns
1. Go to **Emails** → **Campaigns** (or **Sent**).
2. You see a list of sends: draft name, send date, recipient count, and optionally status (e.g. sent, failed, pending).
3. Click a send to see **per-recipient** details: email address, status (sent/failed/pending), and if [open tracking](/emails/tracking) is on, whether they opened the email.
Use this to confirm delivery after a large send and to follow up with anyone who failed (e.g. invalid email) or did not open.
## Statuses
* **Sent**: Delivered to the provider (e.g. Resend); the recipient's server accepted it. It may still land in spam.
* **Failed**: Bounce, invalid address, or provider error. Fix the member's email in [Members](/members/edit-and-remove) and resend if needed.
* **Pending**: Queued or in progress (for background sends). Check again later.
## Open tracking
* If your plan and settings support it, **opens** are recorded when the recipient loads images or tracking pixels in the email. See [Tracking](/emails/tracking). Opens appear per recipient in the campaign detail view.
## Resend to failed recipients
* If the UI offers **Resend to failed**, you can resend the same draft only to recipients who had status **failed** after fixing their email addresses. Otherwise, create a new draft or send and select those members manually.
# Email drafts
Source: https://docs.rowhouse.co/emails/drafts
Create a draft from a template and customize before sending
A **draft** is an email ready to send. You create it from a [template](/emails/templates), optionally edit the content, set **custom variables**, then choose [recipients](/emails/recipients) and [send](/emails/sending).
## Create a draft
1. Go to **Emails** → **Drafts** and click **Create draft** (or **New draft**).
2. Select a **template**. The draft is pre-filled with that template's subject and body.
3. Give the draft a **name** (e.g. "March newsletter send").
4. Optionally **edit** the subject or body (changes apply only to this draft, not the template).
5. Set **custom variables** (if the template uses them): e.g. `event_date` = "March 15", `link_url` = "https\://...". These override the placeholders when sending. See [Variables](/emails/variables).
6. Save. The draft is ready to [send](/emails/sending).
Use custom variables for one-off values (e.g. event date, specific link) so you do not edit the template every time.
## Edit a draft
* Open the draft from **Drafts**, change subject, body, or custom variables, and save. Until you send, you can keep editing. After sending, the draft remains for history; you can duplicate it to create a new draft from the same content if the UI allows.
## Send from a draft
* Open the draft and click **Send** (or **Send email**). Then choose [recipients](/emails/recipients) (e.g. a [group](/groups/using-groups-in-emails), all members, or a custom list) and confirm. See [Sending](/emails/sending).
# Emails overview
Source: https://docs.rowhouse.co/emails/overview
Templates, drafts, sending, and campaigns
The **Emails** section lets you create reusable **templates**, build **drafts** (with custom variables), **send** to members or groups, and review **campaigns** (sent history) and open tracking.
## Main areas
* **Emails** (hub): Overview and quick send.
* **Templates**: Reusable designs (Puck editor or MJML) and subject lines with [variables](/emails/variables) (e.g. `{{name}}`, `{{email}}`).
* **Drafts**: Create a draft from a template, edit content and [custom variables](/emails/variables), then [send](/emails/sending) to [recipients](/emails/recipients) (list, group, or all members).
* **Campaigns**: View [sent history](/emails/campaigns) (who received what, status, and [open tracking](/emails/tracking)).
## Typical flow
1. Create a [template](/emails/templates) (design + subject + variables).
2. Create a [draft](/emails/drafts) from that template and set custom variables if needed.
3. Choose [recipients](/emails/recipients) (e.g. a group or all members).
4. [Send](/emails/sending). Emails are sent (often in the background for large lists).
5. Check [campaigns](/emails/campaigns) for delivery and [opens](/emails/tracking).
Emails may be a **paid plan** feature. If you do not see Templates or Send, check your [subscription](/settings/subscription) and [plan limits](/guides/plan-limits).
## Related
* [Variables](/emails/variables) and [Recipients](/emails/recipients)
* [Troubleshooting](/emails/troubleshooting)
# Choosing recipients
Source: https://docs.rowhouse.co/emails/recipients
Send to a group, all members, or a custom list
When you [send](/emails/sending) an email, you choose **who receives it**: by group, all members, or (if supported) a custom list.
## Send to a group
* Select **Send to group** and pick one or more [groups](/groups/using-groups-in-emails). Every member **currently in** that group (with an email address) receives the email.
* Use this for recurring audiences (e.g. Board, Class of 2026). Members in multiple selected groups are only sent once.
## Send to all members
* Select **All members** (or "Everyone"). Every member in the organization who has an **email** address receives the email.
* Use for org-wide announcements. Consider filtering in Members first to confirm the list is what you expect (e.g. no test accounts).
## Send to a custom list
* If the UI supports it, you can **select individual members** (e.g. search and add by name or email) instead of a group. Use when the audience is ad hoc and not already in a group.
* You can sometimes **exclude** members (e.g. "All except Board") depending on the app.
## Who actually receives the email?
* Only members with a valid **email** address. Members without email are skipped (and may be noted in the send summary).
* Duplicates are avoided: if someone is in two selected groups, they get one email.
Recipient count is shown before you confirm send. If the number looks wrong, change the group or list and try again.
See [Sending](/emails/sending) and [Troubleshooting](/emails/troubleshooting).
# Sending emails
Source: https://docs.rowhouse.co/emails/sending
Send from a draft to members or groups
Send an email by choosing a [draft](/emails/drafts) (or template), selecting [recipients](/emails/recipients), and confirming send. Large sends may run in the background.
## Send from a draft
1. Go to **Emails** → **Drafts** and open the draft you want to send (or use **Send** from the draft editor).
2. Click **Send** (or **Send email**).
3. Choose **recipients**:
* **By group**: Select one or more [groups](/groups/using-groups-in-emails).
* **All members**: Send to everyone in the organization (with an email address).
* **Custom list**: Select individual members (if the UI supports it).
4. Review the recipient count and any warning (e.g. missing emails). Confirm **Send**.
5. The send may complete immediately or run in the background (workflow). You will see a success message and can check [Campaigns](/emails/campaigns) for status.
Double-check recipients before sending. You cannot recall an email after it is sent.
## Send limits and rate
* Your plan may limit how many emails you can send per month or per day. See [Plan limits](/guides/plan-limits). If you hit a limit, the send may fail or queue; upgrade or wait and try again.
* Large sends (e.g. hundreds or thousands) are often processed in the background. Each recipient gets an individual email with [variables](/emails/variables) replaced.
## After sending
* **Campaigns**: View [sent history](/emails/campaigns) to see who received the email and delivery status (sent, failed).
* **Opens**: If [open tracking](/emails/tracking) is enabled, you can see who opened the email.
See [Troubleshooting](/emails/troubleshooting) if emails do not send or recipients report not receiving.
# Email templates
Source: https://docs.rowhouse.co/emails/templates
Create and edit reusable email templates with the Puck or MJML editor
**Templates** are reusable email designs. You set a **subject** and **body** (with [variables](/emails/variables)) and reuse them in [drafts](/emails/drafts) for sending.
## Create a template
1. Go to **Emails** → **Templates** and click **Create template** (or **New template**).
2. Enter a **name** (for your reference, e.g. "Monthly newsletter").
3. Set the **subject** line. Use variables like `{{name}}` or `{{email}}` so each recipient gets a personalized subject. See [Variables](/emails/variables).
4. Build the **body**:
* **Puck editor**: Drag-and-drop blocks (text, images, buttons) and style them. Same concept as the [website page editor](/website/page-editor).
* **MJML**: If your app supports it, you can write or paste MJML; it is converted to HTML for sending.
5. Save. The template appears in the Templates list and can be used to create [drafts](/emails/drafts).
Keep the subject short and clear. Test with a small recipient list first to ensure variables and links work.
## Edit a template
* Open the template from **Templates**, change subject or body, and save. Existing [drafts](/emails/drafts) that were created from this template may keep their own copy of content until you update the draft; new drafts will use the updated template.
## Variables in templates
* Use `{{name}}`, `{{email}}`, and custom variables (e.g. `{{event_date}}`) in both **subject** and **body**. They are replaced per recipient when sending. See [Variables](/emails/variables).
# Open tracking
Source: https://docs.rowhouse.co/emails/tracking
See who opened your emails
**Open tracking** records when a recipient opens an email (e.g. by loading a tracking pixel). You can see opens per recipient in [Campaigns](/emails/campaigns).
## How it works
* When you send an email, Rowhouse (via the email provider, e.g. Resend) may add a small tracking pixel or link to the email.
* When the recipient's email client loads images or that link, an **open** is recorded and tied to that recipient in the campaign.
* Opens are shown in the campaign detail view (per-recipient) and sometimes in a summary (e.g. "45% opened").
Open tracking is not 100% accurate: some clients block images, and some opens are counted multiple times (e.g. multiple opens by the same person). Use it as a rough engagement signal.
## Privacy and compliance
* Tracking is common for marketing and operational emails. Ensure your use complies with your policies and applicable law (e.g. consent, privacy notice). Rowhouse does not control how you use the data; you are responsible for compliance.
## If opens are not showing
* **Plan**: Open tracking may be a paid feature. Check [Plan limits](/guides/plan-limits) and [Subscription](/settings/subscription).
* **Provider**: Tracking depends on the email provider (e.g. Resend webhooks). If the provider does not support or deliver open events, Rowhouse cannot display them.
* **Recipient client**: Some email clients block images by default, so the open is never recorded. This is expected for a portion of recipients.
# Emails troubleshooting
Source: https://docs.rowhouse.co/emails/troubleshooting
Fix sending failures, wrong recipients, and variable issues
Common issues with templates, drafts, and sending.
## Emails not sending
* **Plan**: Emails (templates, send) may require a **paid plan**. See [Subscription](/settings/subscription) and [Plan limits](/guides/plan-limits). Upgrade if needed.
* **Recipients**: Ensure you selected at least one [recipient](/emails/recipients) (group, all members, or list) and that those members have **email addresses**. Members without email are skipped.
* **Workflow/background**: Large sends run in the background. Wait a few minutes and check [Campaigns](/emails/campaigns) for status. If the workflow failed, you may see an error in the app or support can help.
* **Provider**: Sending uses an email provider (e.g. Resend). If the provider is down or rejecting (e.g. invalid API key), sends will fail. Check status pages or app/support for provider errors.
## Wrong recipient or missing recipient
* **Wrong group**: Confirm you selected the correct [group](/groups/using-groups-in-emails). Check the recipient count before sending; if it looks wrong, change the selection.
* **Missing member**: Ensure the member is in the **group** (or in "All members") and has an **email** address. Edit the member in [Members](/members/edit-and-remove) and add them to the group or fix their email, then resend.
* **Duplicate**: If someone is in multiple groups you selected, they receive the email once. No duplicate sends per recipient.
## Variables not replacing / showing as literal text
* **Spelling**: Variable names are case-sensitive. Use exactly `{{name}}` and `{{email}}` (lowercase). Custom variables must match the name you set in the [draft](/emails/drafts) (e.g. `{{event_date}}`).
* **Custom variables**: For custom variables, you must **set values** in the draft before sending. If a variable is left blank or misspelled in the template, it may appear as `{{variable_name}}` in the sent email.
* **Spaces**: Do not put spaces inside the braces: use `{{name}}` not `{{ name }}`.
## Draft or template not found
* **Draft**: Ensure the draft was **saved**. Open **Drafts** and confirm it is in the list. If you are in a different **organization** (club switcher), you will not see another org's drafts.
* **Template**: Same as above for **Templates**. Only admins can create and edit templates; if you are a member, you may not see the Templates section.
## Campaign / open tracking
* **Sent status**: Check [Campaigns](/emails/campaigns) for per-recipient status (sent, failed, pending). **Failed** usually means invalid email or bounce; fix the email and resend to that person if needed.
* **Opens**: [Open tracking](/emails/tracking) depends on your plan and the email provider. Some clients block images, so not every open is recorded.
# Email variables
Source: https://docs.rowhouse.co/emails/variables
Use {{name}}, {{email}}, and custom variables in templates and drafts
**Variables** in templates and drafts are placeholders that get **replaced per recipient** when you send (e.g. `{{name}}` becomes "Jane"). Use them in the subject and body for personalization.
## Built-in variables
* **`{{name}}`**: Recipient's name (from their member record). Use in subject or body: "Hi , ..."
* **`{{email}}`**: Recipient's email address. Use when you need to show or link to their email.
These are filled automatically from the member's profile when you send to members or groups.
## Custom variables (drafts)
* In a [draft](/emails/drafts), you can define **custom variables** (e.g. `event_date`, `link_url`, `message`).
* In the template **subject** and **body**, use the same name in double curly braces: `{{event_date}}`, `{{link_url}}`.
* When sending, you set the values for that draft (e.g. `event_date` = "March 15, 2026"). Every recipient gets the same value for custom variables; only `{{name}}` and `{{email}}` vary per recipient.
Use custom variables for one-off content (event date, registration link) so you do not need a new template for each send.
## Syntax
* Use **double curly braces**: `{{variable_name}}`. Names are usually letters, numbers, and underscores.
* If a variable is not set or misspelled, it may appear as literal `{{variable_name}}` in the sent email. Check your draft's variable list and template spelling.
## Where variables work
* **Subject line**: Full support (e.g. "Reminder for ").
* **Body**: Full support in text and in links (e.g. `href="https://example.com?email={{email}}"`).
* **Per-recipient**: Only `{{name}}` and `{{email}}` are different per recipient; custom variables are the same for everyone in that send.
See [Troubleshooting](/emails/troubleshooting) if variables do not replace or show as literal text.
# Attendance
Source: https://docs.rowhouse.co/events/attendance
Mark who attended using the attendance link
After an event, you can **mark attendance** so you know who showed up (attended) vs who did not (no-show). Attendance is recorded per event invitee.
## How attendance works
* Each event can have an **attendance link** (a unique URL with a token) that only admins or authorized users open.
* Opening the link shows the list of **invitees** (or RSVP "going"). You mark each person as **Attended**, **No-show**, or leave as **Pending**.
* Optionally, **attendance geolock** can require the device to be at a certain location to submit (if enabled for your plan).
## Get the attendance link
1. Open the **event** and go to **Attendance** (or **Mark attendance**).
2. Copy or open the **attendance link**. Share it only with people who should record attendance (e.g. yourself or other admins).
3. Open the link and mark each invitee as **Attended** or **No-show**, then save.
Use the attendance link on the day of the event (e.g. on your phone) so you can mark people as they arrive or at the end.
## Attendance statuses
* **Pending**: Not yet marked.
* **Attended**: Present at the event.
* **No-show**: Did not attend (e.g. RSVP'd but did not show).
* **Cancelled**: Invite or participation cancelled (if the app supports it).
## Geolock (if enabled)
* If **attendance geolock** is on, the person submitting attendance may need to be at the event location (or within a radius). This helps prevent marking attendance from elsewhere. If you are at the venue and geolock blocks you, check device location permissions and try again or contact support.
See [Troubleshooting](/events/troubleshooting) for attendance not saving or link not working.
# Calendars
Source: https://docs.rowhouse.co/events/calendars
Organize events with calendars and default invitees
**Calendars** let you group events (e.g. "Social events", "Meetings") and optionally define a set of **calendar members** who are default invitees for events on that calendar.
## What is a calendar?
A **calendar** belongs to your organization and has:
* **Name** (e.g. "Social events")
* Optional **description**
* **Calendar members**: members who are automatically considered invitees for events assigned to this calendar (depending on app behavior)
* **Events**: events can be assigned to one calendar
## Create a calendar
1. Go to **Events** (or **Calendars** if listed separately) and open calendar settings or the calendar list.
2. Click **Create calendar** (or **Add calendar**).
3. Enter **name** and optional **description**, then save.
4. Add **calendar members** so they are the default invitees for events on this calendar (if the app supports it).
## Assign events to a calendar
* When [creating](/events/create-event) or editing an event, select a **Calendar** from the dropdown. The event is then grouped under that calendar and may automatically include the calendar's members as invitees (depending on implementation).
## iCal feed
* You can expose an [iCal feed](/events/ical) per calendar or per org so members can subscribe in Google Calendar, Apple Calendar, etc.
Exact behavior (e.g. whether calendar members are auto-invited to new events on that calendar) may vary. Check the event invite step after assigning a calendar to confirm who is invited.
# Create event
Source: https://docs.rowhouse.co/events/create-event
Create an event with title, date, location, and optional payment
Create an event so you can invite members, track RSVPs, and optionally collect payment.
## Create a new event
1. Go to **Events** in the sidebar and click **Create event** (or **New event**).
2. Fill in:
* **Title**: e.g. "Fall Kickoff Meeting"
* **Description**: optional details (agenda, what to bring)
* **Start date and time** (and optionally **End time**)
* **Location**: address or place name
* **Amount** (optional): leave blank for a free event, or enter a number (e.g. 10 for \$10) for a paid event. Currency is usually USD unless set at org level.
* **Calendar** (optional): assign to a [calendar](/events/calendars) if you use them
3. Save or **Create**. The event appears in the Events list and you can [invite members](/events/invite-members) next.
For paid events, set the amount before sending invites so members see the correct price when they open the pay link.
## Free vs paid
* **Free**: Leave **Amount** blank or zero. Invitees only RSVP; no payment step.
* **Paid**: Set **Amount** (in dollars or cents depending on the UI). When you assign invitees, they can pay via the event pay link. You can [waive](/events/event-payments) for specific people.
## After creating
* [Invite members](/events/invite-members) (individually or by [group](/groups/using-groups-for-events)).
* Share the [public event page](/events/public-event-page) or add to an [iCal feed](/events/ical).
* Set up [reminders](/events/reminders) if your plan supports them.
# Event payments
Source: https://docs.rowhouse.co/events/event-payments
Paid events: assign amount, waive, and member pay link
For **paid events**, you set an amount (and optionally per-invitee amounts), and invitees pay via a secure link. You can **waive** the fee for specific people.
## Set the event amount
* When [creating the event](/events/create-event), set **Amount** (e.g. \$10). This is the default charge per invitee. Currency is usually USD unless your org uses another.
## Per-invitee amount and waive
* When you [add invitees](/events/invite-members), you can often:
* **Use default amount**: Each invitee sees the event amount.
* **Custom amount**: Override for one person (e.g. \$5 for a guest).
* **Waive**: Set amount to \$0 for that invitee so they do not need to pay (e.g. speaker, volunteer).
* Waived invitees can still RSVP and are marked as paid/waived in the event.
## How invitees pay
1. They receive the **event invite email** and click the link.
2. They see event details and, if they have a balance, a **Pay** button or payment step.
3. They enter payment details (card) on the secure payment page (Stripe). After success, they are marked **paid** and their RSVP is confirmed.
4. Payment page: typically `rowhouse.co/events/[eventId]/pay` (or similar). Do not share this URL broadly; invitees get it via their personal invite link.
Processing fees may apply (see [Processing fees](/finance/processing-fees)). The member pays the event amount plus any fee; your org receives the event amount minus fees and Stripe's share.
## View payment status
* In the event's **Invitees** list, you see who has **Paid**, who is **Waived**, and who is **Unpaid**. You can resend the pay link or waive from there (if the UI allows).
See [Troubleshooting](/events/troubleshooting) for payment failed or pay link broken.
# iCal feed
Source: https://docs.rowhouse.co/events/ical
Subscribe to events in Google Calendar or Apple Calendar
Rowhouse can provide an **iCal feed** (ICS) so members or the public can subscribe to your organization's events in Google Calendar, Apple Calendar, Outlook, or other calendar apps.
## How to get the feed URL
* From **Events** or **Calendars**, or from your org's public page, look for **iCal feed**, **Subscribe to calendar**, or **Calendar feed**.
* The URL may be per **calendar** (e.g. only "Social events") or for **all events** in the org. It often looks like: `rowhouse.co/api/calendar/[org]/[tag]` or similar (your org slug and optional calendar tag).
* Copy the feed URL. Do not share private tokens publicly if the URL contains a secret.
## Subscribe in a calendar app
**Google Calendar:**
1. Open Google Calendar on the web, go to **Other calendars** → **Add by URL**.
2. Paste the iCal feed URL and click **Add**. Events appear and update when the feed is refreshed.
**Apple Calendar:**
1. In Calendar, go to **File** → **New Calendar Subscription** (or **Add Account** for a URL).
2. Paste the feed URL and set refresh interval. Save.
**Outlook / other:**
* Use the app's option to **Add calendar** or **Subscribe from URL** and paste the feed URL.
Calendar apps refresh the feed periodically (e.g. every few hours). New or updated events may take a while to appear.
## What appears in the feed
* Events that are **public** or that the feed is allowed to expose (depending on configuration). Start time, end time, title, and sometimes location and description are included.
* Past events may remain in the feed for history; your calendar app may hide them depending on its settings.
# Invite members to events
Source: https://docs.rowhouse.co/events/invite-members
Assign invitees and send event invite emails
After you [create an event](/events/create-event), invite members so they receive an email and can RSVP (and pay if the event has a fee).
## Add invitees
1. Open the event and go to the **Invite** or **Invitees** section.
2. Add members:
* **By group**: Select one or more [groups](/groups/using-groups-for-events). Everyone in the group gets an invite.
* **Individually**: Search or select members and add them.
3. For **paid events**, you can set or waive the **amount** per invitee. See [Event payments](/events/event-payments).
## Send invites
1. After adding invitees, click **Send invites** (or **Send**).
2. Rowhouse sends an email to each invitee with:
* Event details (title, date, location)
* A link to **RSVP** (and pay if applicable)
3. Invitees appear in the event with status **pending** until they RSVP. You can track [RSVP](/events/rsvp) and [attendance](/events/attendance) on the event page.
Send invites soon after creating the event so members have time to respond. You can send reminders later. See [Reminders](/events/reminders).
## Add or remove invitees later
* **Add**: Add more members or groups and click **Send invites** again. New invitees receive the email; existing ones are not re-sent unless you use "Resend" (if available).
* **Remove**: Remove a member from the invitee list. They will no longer see the event in their invite flow; any existing RSVP or payment may remain in history for your records.
If you use [calendars](/events/calendars) with calendar members, assigning the event to a calendar may auto-add those members as invitees. Check the invitee list and send invites when ready.
# Events overview
Source: https://docs.rowhouse.co/events/overview
Create events, manage invites, RSVPs, attendance, and payments
**Events** let you schedule and run events (meetings, fundraisers, socials) and optionally collect payment. You can invite members, track RSVPs, mark attendance, and send reminders.
## What you can do
* **Create events**: Title, description, date/time, location, and optional payment amount.
* **Invite members**: Assign invitees (individually or by [group](/groups/using-groups-for-events)) and send invite emails.
* **RSVP**: Members respond via magic link or email; you see going / not going / maybe.
* **Attendance**: Use an attendance link to mark who showed up (attended vs no-show).
* **Payments**: For paid events, assign amounts per invitee, waive if needed, and members pay via a pay link.
* **Reminders**: Automated reminders before the event (if enabled).
* **Public page**: Share a public event page and iCal feed.
## Events list and calendar
* Open **Events** in the sidebar to see the list (and calendar view if available). Create a new event or open an existing one to edit, send invites, or view RSVPs and attendance.
## Event types
* **Free event**: No payment; invitees only RSVP.
* **Paid event**: Set an amount; invitees can pay via the event pay link. You can waive or adjust per person. See [Event payments](/events/event-payments).
## Related docs
* [Create event](/events/create-event)
* [Calendars](/events/calendars)
* [Invite members](/events/invite-members)
* [RSVP](/events/rsvp) and [Attendance](/events/attendance)
* [Event payments](/events/event-payments) and [Reminders](/events/reminders)
* [Troubleshooting](/events/troubleshooting)
# Public event page
Source: https://docs.rowhouse.co/events/public-event-page
Share a public link to your event
Each event can have a **public page** that you can share so people can view event details, and in some cases RSVP or pay, without being logged in (depending on configuration).
## Get the public event link
1. Open the **event** in the Events list.
2. Find **View public page** or **Share** (or copy the **event URL**). The URL is typically something like `rowhouse.co/events/[eventId]` (or with your org slug).
3. Share this link by email, social, or your website.
Use the public page for open events (e.g. fundraisers, mixers) where you want anyone with the link to see details. For invite-only events, rely on the [invite emails](/events/invite-members) so only invitees get the personal RSVP/pay link.
## What the public page shows
* **Event title**, **date/time**, **location**, **description**
* Optionally a **Register** or **RSVP** button (which may create an invite or lead to the pay flow for paid events)
* Optionally an **Add to calendar** (iCal) link. See [iCal](/events/ical).
Behavior (e.g. whether strangers can RSVP or only view) depends on your app and event settings.
## Event discovery
* Some setups list **upcoming events** on your org's public site or a club page. That list may link to these public event pages. See [Website](/website/overview) and your pages for how events are displayed.
# Event reminders
Source: https://docs.rowhouse.co/events/reminders
Automated reminders before events
Rowhouse can send **automated reminders** before an event so invitees who have not yet RSVP'd (or paid) get a nudge.
## How reminders work
* Reminders are sent by the system on a schedule (e.g. 24 hours before, or as configured for your plan).
* Recipients are typically event **invitees** who have not completed the action (e.g. have not RSVP'd or have not paid for a paid event).
* The reminder email includes event details and the same RSVP/pay link as the original invite.
Reminder timing and availability depend on your plan and app configuration. If you do not see reminder settings, they may be automatic or only on paid plans.
## Configuring reminders
* If your event or org settings include **Reminders** (e.g. "Send reminder X hours before"), enable it and set the time. Otherwise reminders may run on a default schedule (e.g. one day before).
* Reminders are usually sent only to invitees who are still **pending** (have not RSVP'd or paid). Those who already responded typically do not get a reminder.
## After the event
* Reminders stop once the event has passed. No reminder is sent after the event time.
For invite delivery issues, see [Troubleshooting](/events/troubleshooting).
# RSVP
Source: https://docs.rowhouse.co/events/rsvp
How invitees respond: going, not going, maybe
Event invitees can **RSVP** (respond) via the link in their invite email. You see their status in the event (pending, going, not going, maybe).
## How invitees RSVP
1. The member receives an **event invite email** with a link (magic link or event page).
2. They open the link and see event details and RSVP options: **Going**, **Not going**, **Maybe** (or similar).
3. They submit their response. Their status updates in the event's invite list.
If the event has a **payment**, they may need to complete payment (or be waived) before their RSVP is confirmed. See [Event payments](/events/event-payments).
## Reply by email (if supported)
* Some setups allow invitees to **reply by email** (e.g. "YES" or "GOING") to record their RSVP. Inbound replies are processed and update the invite. If this does not work, use the link in the email instead.
## Viewing RSVPs
* Open the **event** and go to the **Invitees** or **RSVP** section. You will see each invitee and their status: **Pending**, **Going**, **Not going**, **Maybe**.
* Use this list to plan capacity, follow up with non-responders, or [mark attendance](/events/attendance) after the event.
## Magic link and expiry
* The RSVP link is unique per invitee and may be token-based. If a member says the link does not work, send a **new invite** or use "Resend invite" (if available) so they receive a fresh link.
* Links may expire after a long time; for old events, consider creating a new event or resending.
See [Troubleshooting](/events/troubleshooting) for invite not received, link expired, or RSVP not saving.
# Events troubleshooting
Source: https://docs.rowhouse.co/events/troubleshooting
Fix invite delivery, payment, RSVP, and attendance issues
Common issues with events, invites, RSVP, and payments.
## Invites not received
* **Check spam/promotions** for the invite email. Ask the invitee to add the sender to contacts.
* **Confirm email address**: In **Members**, ensure the member has the correct email. Edit if needed and **resend** the invite (if the UI allows).
* **Send invites**: After adding invitees, you must click **Send invites**. If you only added them but did not send, they will not receive an email.
* **Bulk send**: Large invite lists may be sent in the background. Wait a few minutes and check **Campaigns** or send status; if some failed, resend to failed recipients.
## RSVP link expired or not working
* Links can expire or be single-use in some setups. Use **Resend invite** (if available) to send a fresh link to that invitee.
* Ensure the invitee is opening the link from the **same email address** they were invited with. Some links are tied to the invitee record.
* If the event is in the past, RSVP may be closed. Create a new event or mark the current one as cancelled if appropriate.
## Payment failed or pay link broken
* **Member**: Have them try again (card declined, network error). Use a different card or browser. Ensure they are using the link from their **invite email**, not a generic event page.
* **You**: Confirm the event has an **amount** set and the org has completed [Stripe Connect](/getting-started/stripe-connect). Check **Finance** → **Transactions** for the event to see if a payment was attempted and failed (with reason).
* **Waive**: If they should not pay, [waive](/events/event-payments) their invite so they can RSVP without paying.
## Attendance not saving
* **Save**: After marking attendance, click **Save** or **Submit**. If you leave the page without saving, changes are lost.
* **Link**: Use the **attendance link** from the event (Attendance section). Do not use the public event page or RSVP link for marking attendance.
* **Geolock**: If [attendance geolock](/events/attendance) is on and you are not at the venue, enable device location and try again or turn off geolock for that event if you have permission.
## Event not showing / wrong list
* **Calendar**: If you use [calendars](/events/calendars), filter by calendar or "All" to see the event.
* **Past events**: Switch the list to **Upcoming** vs **Past** (if the UI has that filter).
* **Org**: Confirm you are in the correct **organization** (club switcher). Events are per org.
## Duplicate or missing invitees
* **Duplicate**: Remove the duplicate from the invitee list. If they already paid, contact support before deleting; you may need to refund or keep one record.
* **Missing**: Re-add the member (or group) and **Send invites** again so they receive the email.
# Platform cards (balance cards)
Source: https://docs.rowhouse.co/finance/balance-cards
Coming soon: balance cards for members
**Platform cards** (or **balance cards**) are a planned feature that let you issue cards or balance accounts for members (e.g. for use at events or for reimbursements). This feature may be **coming soon** and not yet available for all plans.
## What to expect (when available)
* **Balance cards**: Cards or balance accounts tied to a member, funded by your org (or by the member). Use cases may include event spending, reimbursements, or controlled spending.
* **Where**: If enabled, you will see **Platform Cards** (or **Balance cards**) under **Finance** in the sidebar. Setup and usage will be documented when the feature is released.
## If you do not see it
* The feature may be in beta or not yet launched. Check [Plan limits](/guides/plan-limits) and release notes, or contact support to ask about availability and roadmap.
# Finance overview
Source: https://docs.rowhouse.co/finance/overview
Transactions, dues, merch, payouts, and balance
The **Finance** section gives you a single place for money in and out: **transactions** (dues, events, merch), **payouts** to your bank, and (if available) **balance** or **platform cards**.
## Main areas
* **Transactions**: List of payments (dues, events, merch) and sometimes refunds or adjustments. Filter by type, date, member. See [Transactions](/finance/transactions).
* **Dues**: [Assign](/dues/assigning-dues) and track dues, [pay links](/dues/pay-link), and [ledger](/dues/ledger). See [Dues overview](/dues/overview).
* **Merch**: [Merch groups](/merch/overview) and storefront; orders appear in Transactions. See [Merch overview](/merch/overview).
* **Payouts**: When Stripe sends money to your bank. View payout history and status. See [Payouts](/finance/payouts).
* **Platform cards** (if available): Balance cards for members; may be coming soon. See [Balance cards](/finance/balance-cards).
* **Processing fees**: [Fees](/finance/processing-fees) by plan (e.g. free 10%+30c, pro 8%+30c, premium 5%+30c).
## Requirements
* **Stripe Connect**: You must complete [Stripe Connect](/getting-started/stripe-connect) and (for payouts) [bank details](/getting-started/bank-details) to accept payments and receive payouts.
* **Plan**: Most Finance features (dues, merch, transactions, payouts) require a **paid plan**. See [Plan limits](/guides/plan-limits) and [Subscription](/settings/subscription).
## Related
* [Transactions](/finance/transactions), [Payouts](/finance/payouts), [Processing fees](/finance/processing-fees)
* [Troubleshooting](/finance/troubleshooting)
# Payouts
Source: https://docs.rowhouse.co/finance/payouts
When and how you receive money in your bank account
**Payouts** are transfers from Stripe to your connected **bank account**. After customers pay (dues, events, merch), Stripe holds the funds and then sends them to you on a schedule (e.g. rolling or weekly).
## Where to find it
* **Finance** → **Payouts** in the sidebar. You see a list of payouts: date, amount, status (pending, paid, failed), and optional Stripe batch ID or link.
## Payout schedule
* **Stripe controls the schedule**, not Rowhouse. Common patterns: **rolling** (e.g. 2 business days after the charge) or **weekly** (e.g. every Wednesday). Check your [Stripe Dashboard](https://dashboard.stripe.com) for your exact schedule and bank account.
* **First payout**: New connected accounts may have a longer first payout (e.g. 7–14 days) while Stripe verifies. After that, payouts follow the normal schedule.
## Statuses
* **Pending**: Payout has been initiated but not yet sent to your bank.
* **Paid** (or **In transit**): Sent to your bank; allow 1–3 business days for the bank to post it.
* **Failed**: Stripe could not complete the payout (e.g. invalid bank details). Update your [bank account](/getting-started/bank-details) and contact Stripe if needed.
## Instant payouts (if enabled)
* Some accounts can enable **instant payouts**: funds are sent to your bank within minutes (for a fee). See [Instant payouts](/settings/instant-payouts) if your org has this option. Otherwise, standard schedule applies.
## Disputes and refunds
* **Disputes** and **refunds** are handled in Stripe. They reduce your balance and may affect upcoming payouts. Rowhouse may show a transaction as refunded; for full details use the Stripe Dashboard.
# Processing fees
Source: https://docs.rowhouse.co/finance/processing-fees
Fees by plan for dues, events, and merch
Rowhouse applies **processing fees** on payments (dues, events, merch). The fee depends on your **subscription plan**. The member or customer typically pays the fee (added to the amount) or it is deducted from your share; exact behavior may vary by product.
## Fee structure (typical)
* **Free**: e.g. 10% + 30c per transaction (or similar).
* **Pro**: e.g. 8% + 30c per transaction.
* **Premium**: e.g. 5% + 30c per transaction.
Exact percentages and fixed amounts are defined in the app (e.g. `getEventProcessingFeeCents` or pricing logic). Check your [Subscription](/settings/subscription) page or [Plan limits](/guides/plan-limits) for the current fees for your plan.
## Who pays the fee?
* Often the **payer** (member or customer) is charged the base amount **plus** the processing fee so your org receives the full base amount. Example: $50 dues + fee → member pays $50 + fee; you receive \$50 (minus Stripe's own fees, which may be included in the percentage).
* In some setups the fee is deducted from your side. Your **Transactions** or **Payouts** view may show net amounts; check the UI or support for your case.
## Stripe fees
* Stripe also charges their own fees (e.g. 2.9% + 30c in the US). The Rowhouse processing fee may be on top of that or may be all-in. Read your plan and Stripe dashboard to understand total cost.
## Reducing fees
* **Upgrade plan**: Higher tiers (e.g. Pro, Premium) usually have lower processing fees. See [Subscription](/settings/subscription) to upgrade.
# Transactions
Source: https://docs.rowhouse.co/finance/transactions
View and filter payment history
**Transactions** lists all payments (and sometimes refunds) for your organization: dues, events, and merch. Use it to see who paid what and when.
## Where to find it
* **Finance** → **Transactions** in the sidebar. You see a table or list: date, member (or customer), amount, type (dues/event/merch), and optional reference (assignment, event, order).
## Filter and search
* **Date range**: Filter by date so you can reconcile a specific period.
* **Type**: Filter by **dues**, **event**, or **merch** (if the UI supports it).
* **Member**: Search or filter by member name or email to see one person's payments.
* **Source**: Some views let you filter by assignment, event, or merch group.
## What each transaction shows
* **Amount**: What was paid (usually the amount you set; fees may be shown separately depending on the app).
* **Member/Customer**: Who paid (name, email, or guest).
* **Type**: Dues, event payment, or merch order.
* **Reference**: Link to the dues assignment, event, or order so you can open the source record.
* **Status**: Succeeded (and sometimes failed or refunded).
* **Date**: When the payment was completed.
Transactions reflect what Rowhouse has received from Stripe. For disputes or refunds done in Stripe, the list may update when webhooks are processed; check Stripe Dashboard for the full picture.
## Export
* If the UI offers **Export** (e.g. CSV), use it for accounting or reconciliation. Export after applying filters so you get only the range you need.
# Finance troubleshooting
Source: https://docs.rowhouse.co/finance/troubleshooting
Payout delayed, missing transaction, fee questions
Common issues with transactions, payouts, and fees.
## Payout delayed
* **Schedule**: Payouts follow Stripe's schedule (e.g. 2 business days or weekly). Check your [Stripe Dashboard](https://dashboard.stripe.com) for the exact payout date and status.
* **First payout**: New accounts often have a longer first payout (e.g. 7–14 days). After that, payouts follow the normal schedule.
* **Bank**: Ensure your [bank details](/getting-started/bank-details) are correct. Wrong routing or account number can delay or block payouts. Update in Stripe or via Rowhouse and wait for the next cycle.
* **Failed**: If a payout shows **failed**, fix the bank account and contact Stripe. The funds may be retried or returned to your Stripe balance; Stripe support can confirm.
## Missing transaction
* **Wait**: After a payment, the transaction can take a few seconds to appear. Refresh **Finance** → **Transactions** and expand the date range.
* **Webhook**: Rowhouse records transactions when Stripe sends success webhooks. If Stripe had an outage or the webhook failed, the transaction might sync later. If the charge appears in your Stripe Dashboard but not in Rowhouse, contact support.
* **Filter**: Ensure you are not filtering by type or date in a way that hides the transaction. Try "All" and a wide date range.
* **Org**: Confirm you are in the correct **organization** (club switcher). Transactions are per org.
## Fee questions
* **Amount charged**: The amount the member paid may include the [processing fee](/finance/processing-fees) (base + fee). Your org typically receives the base amount; the fee covers Rowhouse and/or Stripe. See [Processing fees](/finance/processing-fees).
* **Plan**: Your fee rate depends on your [subscription](/settings/subscription) plan. Upgrade to a higher plan to reduce the fee percentage.
* **Refunds**: Refunds are usually for the amount the customer paid. Fees may or may not be refunded; check Stripe and your plan terms.
## Finance section locked
* **Plan**: Finance (Transactions, Dues, Merch, Payouts) usually requires a **paid plan**. See [Subscription](/settings/subscription) and [Plan limits](/guides/plan-limits). Upgrade to unlock.
* **Stripe**: You must complete [Stripe Connect](/getting-started/stripe-connect) to accept payments. Until Connect is complete, payment features are disabled or limited.
# Bank details
Source: https://docs.rowhouse.co/getting-started/bank-details
Add a bank account to receive payouts
To receive payouts from dues, events, and merch sales, your organization must have a **bank account** connected through Stripe.
## When to add bank details
* During [onboarding](/getting-started/onboarding), Stripe often asks for a bank account as part of Connect setup.
* If you skipped it or need to change it, you can add or update bank details from Rowhouse or from your [Stripe Dashboard](https://dashboard.stripe.com).
## Add bank account (via Rowhouse)
1. Go to **Settings** (or **Subscription** / **Stripe**) in the sidebar (admin only).
2. Find **Stripe** or **Payments** and open **Add bank account** (or the link Stripe provides).
3. You may be taken to Stripe to enter:
* **Account type** (checking/savings)
* **Routing number** and **account number**
* **Account holder name**
4. Save. Stripe will verify the account; payouts will use this account once verification succeeds.
Double-check routing and account numbers. Incorrect details can delay or block payouts.
## Payout schedule
* Payout timing is set by Stripe (e.g. rolling 2-day or weekly). Rowhouse does not control the schedule.
* You can see payout status and history in **Finance** → **Payouts** in Rowhouse, and in your Stripe Dashboard.
See [Payouts](/finance/payouts) for viewing and troubleshooting payouts.
# Create an organization
Source: https://docs.rowhouse.co/getting-started/create-organization
Set up a new club, chapter, or team on Rowhouse
Create your organization (club) so you can add members, collect dues, and run events.
## Create the organization
1. Sign in to Rowhouse and click **Create Club** (from the club switcher in the sidebar or the onboarding flow).
2. Enter your **organization name** (e.g. "Economics Club").
3. Choose a **slug**: the URL-friendly identifier (e.g. `economics-club`). Your org's public URLs will use this (e.g. `rowhouse.co/economics-club`).
4. Submit. You'll be taken to onboarding.
The slug cannot be changed easily later. Use something short, lowercase, and without spaces (e.g. `my-club`).
## Onboarding steps
After creating the org, complete onboarding so you can accept payments and receive payouts:
1. **Stripe Connect**: Link your Stripe account so Rowhouse can process payments on your behalf. See [Stripe Connect](/getting-started/stripe-connect).
2. **Bank details**: Add a bank account for payouts. See [Bank details](/getting-started/bank-details).
3. **Profile** (if prompted): Add or confirm your name and contact info.
See [Onboarding](/getting-started/onboarding) for an overview of the full flow.
## First steps after creation
* **Add members**: Go to **Members** and add people manually or [import via CSV](/members/csv-upload).
* **Set up dues or events**: Use **Dues** or **Events** to start collecting payments. See [Quickstart](/quickstart#step-4-set-up-your-first-dues-or-event).
* **Invite other admins**: Add members with the **admin** role so they can manage the org. See [Roles and permissions](/members/roles-and-permissions).
Share a join code or invite link so others can join your organization.
# Join an organization
Source: https://docs.rowhouse.co/getting-started/join-organization
Join a club or chapter via invite link or join code
You can join an existing Rowhouse organization in two ways: **invite link** or **join code**.
## Join via invite link
1. An admin sends you an **invite link** (e.g. `rowhouse.co/clubs/invite?token=...` or `rowhouse.co/clubs/join` with context).
2. Open the link in your browser.
3. If you're not signed in, sign in (or sign up) with the email the admin used for the invite.
4. Accept the invite. You'll be added as a member and can switch to that organization in the sidebar.
Use the same email address the admin used when inviting you, or the invite may not match your account.
## Join via join code
1. Sign in to Rowhouse.
2. Open the **club switcher** in the sidebar (top of the sidebar) and click **Join Club**.
3. Enter the **join code** your admin shared (e.g. a short alphanumeric code).
4. Submit. You'll be added to that organization.
Join codes are set by admins in [Club settings](/settings/club-settings). If the code doesn't work, ask an admin to confirm it and your email.
## After joining
* Your **role** is usually **member** by default. Admins can change it to **admin** if you need to manage the org. See [Roles and permissions](/members/roles-and-permissions).
* Switch between organizations using the **club switcher** in the sidebar. See [Switching clubs](/getting-started/switching-clubs).
If you don't see the organization or the invite fails, see [Troubleshooting](/getting-started/troubleshooting).
# Log in
Source: https://docs.rowhouse.co/getting-started/log-in
Sign in to Rowhouse and manage your session
Sign in to access your organizations, members, events, and payments.
## Log in with email
1. Go to [Rowhouse](https://rowhouse.co) and click **Log in**.
2. Enter the **email** and **password** you used to sign up.
3. Click **Log in**.
## Log in with Google
1. On the login page, click **Continue with Google**.
2. Select your Google account. You must use the same Google account you used when signing up for Rowhouse.
## Forgot password
1. On the login page, click **Forgot password?** (or similar).
2. Enter your email and submit. We'll send a reset link.
3. Use the link to set a new password, then log in with your email and the new password.
Password reset links expire after a short time. Request a new one if the link doesn't work.
## Session and sign out
* You stay signed in until you sign out or your session expires.
* To sign out: open the **user menu** in the sidebar (your avatar at the bottom), then click **Sign out**.
If you can't log in or don't see your organization, see [Troubleshooting](/getting-started/troubleshooting).
# Onboarding
Source: https://docs.rowhouse.co/getting-started/onboarding
Overview of organization onboarding: Stripe, bank, and profile
After you [create an organization](/getting-started/create-organization), onboarding walks you through payments and payouts so your club can accept money and receive it in your bank account.
## Onboarding steps (overview)
1. **Stripe Connect**\
Connect your Stripe account so Rowhouse can process dues, event payments, and merch sales on your behalf. You'll complete Stripe's flow (business type, representative, EIN, bank, etc.). See [Stripe Connect](/getting-started/stripe-connect).
2. **Bank details**\
Add or confirm the bank account where you want to receive payouts. See [Bank details](/getting-started/bank-details).
3. **Profile** (if shown)\
Confirm or add your name and contact information for the account.
You can often complete Stripe and bank in one flow. If you skip a step, you can return from **Settings** or the dashboard when you're ready to accept payments.
## Why Stripe Connect?
Rowhouse uses **Stripe Connect** so that:
* Payments go to your organization's Stripe account (you're the connected account).
* You receive payouts to your bank on the schedule Stripe defines (e.g. rolling or weekly).
* Rowhouse never holds your funds; Stripe handles compliance and payouts.
See [Stripe Connect](/getting-started/stripe-connect) for details and troubleshooting.
## If onboarding is incomplete
* **Dues, events, and merch**: You can still set up dues groups, events, and merch. Members won't be able to complete payment until Stripe Connect (and bank, if required) is complete.
* **Payouts**: You must complete Stripe onboarding and add a bank account to receive payouts. See [Payouts](/finance/payouts).
Stuck? See [Troubleshooting](/getting-started/troubleshooting) for common onboarding issues.
# Sign up
Source: https://docs.rowhouse.co/getting-started/sign-up
Create a Rowhouse account with email or Google
Create a Rowhouse account to manage or join organizations (clubs, chapters, teams).
## Sign up with email
1. Go to [Rowhouse](https://rowhouse.co) and click **Sign up** (or **Get started**).
2. Enter your **email address** and **password**.
3. Click **Sign up**.
4. Check your inbox and click the **verification link** we send. You must verify your email before you can use all features.
If you don't see the verification email, check spam and promotions. Add our sender to your contacts to avoid future delivery issues.
## Sign up with Google
1. On the sign-up or login page, click **Continue with Google**.
2. Choose your Google account and approve access.
3. You're signed in; no separate email verification is required.
Using Google is faster and avoids managing another password. You can still be invited to or create multiple organizations.
## After sign-up
* **Create an organization**: Use [Create an organization](/getting-started/create-organization) to set up your club or chapter.
* **Join an organization**: If you have an invite link or join code, see [Join an organization](/getting-started/join-organization).
If you already have an account, see [Log in](/getting-started/log-in).
# Stripe Connect
Source: https://docs.rowhouse.co/getting-started/stripe-connect
Connect your Stripe account to accept and receive payments
Rowhouse uses **Stripe Connect** so your organization can accept payments (dues, events, merch) and receive payouts to your bank account.
## Why connect Stripe?
* **Accept payments**: Members pay via secure Stripe-hosted flows; you see transactions in Rowhouse and in your Stripe dashboard.
* **Receive payouts**: Funds are sent to your connected bank account on Stripe's schedule (e.g. rolling or weekly).
* **Compliance**: Stripe handles identity and tax requirements; you complete their onboarding once.
## Connect your account
1. During [onboarding](/getting-started/onboarding), or from **Settings** (or **Subscription**), click to **connect Stripe** or **complete Stripe setup**.
2. You're redirected to Stripe's onboarding. Complete the steps they show, which typically include:
* **Business type** (individual, company, etc.)
* **Legal name** and **representative** details
* **EIN** or tax ID if required
* **Bank account** for payouts (or you may add this in [Bank details](/getting-started/bank-details) in Rowhouse)
3. After finishing, you're returned to Rowhouse. Your org is then able to accept payments and receive payouts.
Use the same legal and bank details you want for tax and payout purposes. Changing them later may require going through Stripe again.
## Representative, EIN, and business type
Stripe asks for:
* **Representative**: The person responsible for the connected account (often the org leader).
* **EIN / Tax ID**: Required for many business types in the US.
* **Business type**: Affects what information Stripe collects and how they report.
These are Stripe requirements; Rowhouse does not store your EIN or full bank details. For issues with the Stripe form, see [Stripe Connect documentation](https://stripe.com/docs/connect).
## Re-onboard or disconnect
* **Re-onboard**: If Stripe asks for more information (e.g. after a pause), use the same **connect** or **complete setup** entry point in Rowhouse to open Stripe again.
* **Disconnect**: If your org needs to disconnect Stripe (e.g. closing the club), use **Settings** or **Subscription** and look for **Stripe** or **Payments**; disconnect only if you no longer need to accept payments. See [Settings - Stripe Connect](/settings/stripe-connect).
Keep your Stripe dashboard bookmarked so you can view payouts, disputes, and tax documents there.
# Switching clubs
Source: https://docs.rowhouse.co/getting-started/switching-clubs
Use the club switcher to work with multiple organizations
If you belong to more than one organization (club, chapter, or team), use the **club switcher** to change which one you're viewing and managing.
## Where to find the club switcher
* At the **top of the sidebar**, below the Rowhouse logo, you'll see the current organization's name and logo (or initials).
* Click that area to open the switcher dropdown.
## What the switcher shows
* **Current org**: Name and your role (e.g. Admin, Member).
* **Other orgs**: A list of all organizations you're a member of. Click one to switch.
* **Create Club**: Opens the flow to [create a new organization](/getting-started/create-organization).
* **Join Club**: Opens the flow to [join an organization](/getting-started/join-organization) with a join code.
## After switching
* The sidebar, dashboard, and all data (members, events, dues, etc.) update to the selected organization.
* Your **role** (admin vs member) is per organization. You might be an admin in one club and a member in another.
Bookmark or pin the dashboard URL for each org if you switch often. The URL may include the org context.
If you don't see an organization you expect, see [Troubleshooting](/getting-started/troubleshooting).
# Troubleshooting
Source: https://docs.rowhouse.co/getting-started/troubleshooting
Fix common sign-up, login, and onboarding issues
Common issues when signing up, logging in, or onboarding your organization.
## Sign-up and login
### I didn't receive the verification email
* Check **spam** and **promotions** (or other tabs).
* Add the sender to your contacts and request the verification email again from the sign-up flow.
* Ensure you entered the correct email address.
### I can't log in with Google
* Use the **same Google account** you used when you first signed up for Rowhouse.
* If you signed up with email and later try Google, Rowhouse may treat that as a different account. Use **Log in with email** and your password, or use the same Google account everywhere.
### I forgot my password
* On the login page, use **Forgot password?** and enter your email. Use the reset link from the email to set a new password. Links expire; request a new one if needed.
### I don't see my organization after logging in
* Use the **club switcher** at the top of the sidebar. Your org might be in the list; select it.
* If you were invited, ensure you accepted the invite and used the same email the admin invited.
* If you just created the org, refresh the page or log out and back in. If it still doesn't appear, try creating again or contact support.
## Onboarding and Stripe
### Onboarding is stuck or Stripe won't complete
* Finish **all required fields** in Stripe's screens (business type, representative, EIN if required, bank account).
* Use a supported browser and disable ad blockers or extensions that might block Stripe.
* If Stripe shows an error, follow their message (e.g. fix invalid routing number). Then return to Rowhouse and try connecting again.
### I need to add or change my bank account
* Go to **Settings** (or **Subscription** / **Stripe**) and use **Add bank account** or the link to Stripe. You can also add or update bank details in your [Stripe Dashboard](https://dashboard.stripe.com).
### Payments aren't working / "Connect Stripe" still showing
* Complete [Stripe Connect](/getting-started/stripe-connect) and any steps Stripe asks for (identity, bank). Until Connect is complete, members cannot pay.
* If you've already completed Stripe, refresh the page or log out and back in. If the dashboard still shows incomplete, try re-opening the Stripe connection from Settings.
## Join code and invites
### Join code doesn't work
* Confirm the code with an **admin** (no extra spaces, correct characters). Admins can see or reset the join code in [Club settings](/settings/join-code-and-invite).
* Ensure you're signed in with the email the admin expects, if applicable.
### I was invited but don't see the organization
* Check that you **accepted the invite** (e.g. clicked the button in the invite email or page).
* Open the **club switcher** and look for the org in the list.
* Ensure you're logged in with the account that received the invite.
## Still stuck?
* Check other guides: [Members troubleshooting](/members/troubleshooting), [Dues troubleshooting](/dues/troubleshooting), [Settings troubleshooting](/settings/troubleshooting).
* Use the **Support** or **Contact** link in the app or docs footer, or email support with your email and org name (and whether you're admin or member).
# User preferences
Source: https://docs.rowhouse.co/getting-started/user-preferences
Profile, theme, and account preferences
User preferences apply to **your account** across all organizations you belong to (unlike [Club settings](/settings/overview), which are per organization).
## Open user preferences
1. Click your **avatar** or **name** at the bottom of the sidebar.
2. In the menu, click **User Preferences** (or **Preferences**). You'll be taken to the preferences page.
## What you can change
* **Name and email**: Update the name and email associated with your account. Email may require verification.
* **Profile picture**: Upload or change your avatar. This appears in the sidebar and may be shown to other admins in the same org.
* **Theme**: Switch between **light** and **dark** mode. The choice is saved for your browser/device.
Theme is stored in your browser (e.g. localStorage). If you use another device or clear data, you may need to set it again.
## Dark mode
* In the same user menu (avatar at bottom of sidebar), you can toggle **Dark mode** / **Light mode** without opening the full preferences page.
* This affects only the Rowhouse dashboard UI, not your org's public pages (those use your website/theme settings).
For organization-level settings (name, logo, join code, subscription), see [Settings](/settings/overview).
# Assign members to groups
Source: https://docs.rowhouse.co/groups/assign-members
Add and remove members from groups
Add members to a group so you can send them emails or invite them to events as a set. You can also remove members from a group.
## Add members to a group
1. Go to **Groups** and open the group (or click **Edit** / **Manage members**).
2. Click **Add members** (or **Assign members**). You may see a list or search of all org members.
3. Select one or more members and confirm. They are added to the group and will appear when you use this group for [emails](/groups/using-groups-in-emails) or [event invitees](/groups/using-groups-for-events).
**Alternative (from Members):**
* Open **Members**, select one or more members, then use an action like **Add to group** and choose the group. Behavior may vary by UI.
You can add the same member to multiple groups. They will receive emails or invites for each group you use.
## Remove members from a group
1. Go to **Groups** and open the group.
2. Find the member in the group's member list and click **Remove** (or the X), or open the member and remove the group assignment.
3. The member is no longer in that group. They remain in the organization and in any other groups.
Removing a member from a group does not remove them from the organization or delete their data. It only removes that group label.
## See who is in a group
* In **Groups**, open the group and view its member list.
* In **Members**, use the [filter by group](/members/filters-and-search) to show only members in that group.
# Create groups
Source: https://docs.rowhouse.co/groups/create-groups
Create, edit, and delete groups
Create groups to organize your members (e.g. Board, Class of 2026) and use them for emails and events.
## Create a group
1. Go to **Groups** in the sidebar.
2. Click **Create group** (or **Add group**).
3. Enter:
* **Name**: e.g. "Board", "Class of 2026" (required).
* **Description**: optional short description.
* **Color**: optional; used in the UI to distinguish groups.
4. Save. The group appears in the list and can be used when [assigning members](/groups/assign-members), [sending emails](/groups/using-groups-in-emails), or [inviting to events](/groups/using-groups-for-events).
Use clear, consistent names so everyone knows what the group is for (e.g. "2025-2026 Board" instead of "Board" if you have multiple years).
## Edit a group
1. Go to **Groups** and click the group (or **Edit**).
2. Change **name**, **description**, or **color**.
3. Save. Member assignments are unchanged; only the group metadata updates.
## Delete a group
1. Go to **Groups** and open the group.
2. Find **Delete group** (often in a menu or at the bottom).
3. Confirm. The group is removed. **Members are not removed from the organization**; they simply no longer belong to this group. Any past emails or event invites sent to the group are unchanged in history.
Deleting a group cannot be undone. If you might need it again, consider leaving it and removing members instead, or renaming it (e.g. "Board - Archive").
## Next steps
* [Assign members](/groups/assign-members) to the group.
* [Send emails to the group](/groups/using-groups-in-emails) or [use the group for event invitees](/groups/using-groups-for-events).
# Groups overview
Source: https://docs.rowhouse.co/groups/overview
Organize members with groups (tags) for emails and events
**Groups** let you label and organize members (e.g. Board, Class of 2026, Committee) and use those groups when sending emails or managing event invitees.
## What is a group?
A **group** is a named set of members in your organization. Each group has:
* **Name** (e.g. "Board", "Class of 2026")
* Optional **description**
* Optional **color** (for display in the UI)
* **Members**: you add or remove members from the group
Groups are like tags or labels: one member can be in multiple groups.
## Why use groups?
* **Emails**: Send [emails to a group](/groups/using-groups-in-emails) instead of selecting members one by one or sending to everyone.
* **Events**: When [inviting to events](/groups/using-groups-for-events), you can select a group so everyone in that group gets an invite.
* **Members list**: [Filter members](/members/filters-and-search) by group to see who is in Board, who is in Class of 2026, etc.
## Where to manage groups
* Open **Groups** in the sidebar to see all groups, create new ones, and assign members.
* When sending an email or inviting to an event, you can pick one or more groups as recipients or invitees.
See [Create groups](/groups/create-groups) and [Assign members](/groups/assign-members). If a group is missing or a member is not in the right group, see [Groups troubleshooting](/groups/troubleshooting).
# Groups troubleshooting
Source: https://docs.rowhouse.co/groups/troubleshooting
Fix missing groups, wrong members, and dropdown issues
Common issues when using groups.
## Member not in group / Group missing in dropdown
### I added a member to a group but they do not appear
* **Refresh** the group's member list or the Members page (filter by that group). Sync can be delayed briefly.
* Confirm you added the **correct member** (same name/email) and the **correct group**. Open the group and check the member list.
* If you added from the Members page, confirm you clicked **Save** or **Add to group** after selecting the group.
### The group does not appear in the email or event invite dropdown
* Ensure the group **exists** and was **saved**. Go to **Groups** and confirm it is in the list.
* Ensure you have permission to send emails or manage events (you must be an **admin**). Refresh the page and try again.
* If you have many groups, scroll the dropdown or use search if the UI supports it.
## Wrong recipients or invitees
### Someone received an email (or event invite) but they are not in the group
* They might be in **another group** you selected, or you may have also selected **All members** or added individuals. Check the recipient list or send summary before sending.
* If you recently **removed** them from the group, the send may have run before the removal. Check when the email was sent vs when you edited the group.
### Someone in the group did not receive the email (or invite)
* Confirm they have a valid **email** address in their member record. Members without email are skipped.
* Check **Campaigns** or sent history to see if the email was marked **sent** or **failed** for that recipient. See [Emails troubleshooting](/emails/troubleshooting).
* For event invites: confirm you **sent invites** after adding the group, and that the member was in the group at the time of send.
## Create and delete
### I cannot create a group
* You must be an **admin** to create or edit groups. See [Roles and permissions](/members/roles-and-permissions).
* If the **Create group** button is missing, refresh and ensure you are in the correct organization (club switcher).
### I deleted a group by mistake
* Deletion is permanent. Recreate the group with the same name and [re-assign members](/groups/assign-members) manually. Past emails or event invites that used the old group are unchanged in history.
# Using groups for events
Source: https://docs.rowhouse.co/groups/using-groups-for-events
Invite a group to an event
When creating or managing an event, you can **invite a group** so every member in that group gets an event invite, instead of selecting members one by one.
## Invite a group to an event
1. Go to **Events** and create an event or open an existing one.
2. In the **Invite** or **Invitees** section, choose **Invite by group** (or add a group to the invite list).
3. Select one or more [groups](/groups/overview). Rowhouse creates an [event invite](/events/invite-members) for each member in the group(s).
4. Send invites (e.g. **Send invites** button). Members in the group receive the invite email and can [RSVP](/events/rsvp) and, if the event has a fee, [pay](/events/event-payments).
Inviting a group adds everyone in the group at the time you send. If you add new members to the group later, they will not automatically get this event invite; you would need to send invites to them separately or add them to the event.
## Combine group and individual invitees
* You can often invite one or more groups **and** add or remove individual members. Use this to include the "Board" group plus a few extra people who are not in that group.
* Members in multiple selected groups still receive only one invite per event (no duplicate invites).
See [Invite members](/events/invite-members) for full details on event invites. If a group does not appear when inviting, see [Groups troubleshooting](/groups/troubleshooting).
# Using groups in emails
Source: https://docs.rowhouse.co/groups/using-groups-in-emails
Send emails to a group of members
When sending an email from Rowhouse, you can choose **recipients by group** so everyone in that group receives the email without selecting members one by one.
## Send to a group
1. Go to **Emails** and create or open a [draft](/emails/drafts), or use **Send** with a template.
2. In the **Recipients** (or **To**) section, choose **Send to group** (or similar).
3. Select one or more [groups](/groups/overview). Rowhouse resolves the group(s) to the list of members who belong to them.
4. Optionally add or exclude individual members if the UI allows.
5. Send the email. Every member in the selected group(s) receives it (subject to having a valid email address).
Use groups for recurring audiences (e.g. "Board" for leadership updates, "Class of 2026" for class-specific announcements) so you do not have to re-select people each time.
## Who receives the email?
* All **members** currently in the selected group(s) who have an **email** address.
* Members in multiple selected groups receive the email once (no duplicate sends per member).
* If a member has no email, they are skipped (and may be noted in the send summary if the app shows it).
See [Recipients](/emails/recipients) for more ways to choose who gets an email (e.g. all members, custom list). If a group is missing from the dropdown, see [Groups troubleshooting](/groups/troubleshooting).
# Best practices
Source: https://docs.rowhouse.co/guides/best-practices
Naming, groups, dues groups, and when to use what
Recommendations for using Rowhouse effectively.
## Naming and slugs
* **Club slug**: Use a short, lowercase slug (e.g. `econ-club`) when creating your org. Avoid spaces and special characters; it appears in URLs and cannot be changed easily.
* **Page and group slugs**: Same idea for [website pages](/website/slugs-and-urls) and [dues/merch groups](/dues/dues-groups): lowercase, hyphens, no spaces. Use consistent names (e.g. `fall-2025-dues`) so links and filters stay predictable.
* **Member names**: Use consistent first/last or full name so search and filters work well. Correct typos after [CSV import](/members/csv-upload) if needed.
## Groups
* **Create groups for recurring audiences**: e.g. "Board", "Class of 2026", "Committee chairs". Use them for [emails](/groups/using-groups-in-emails) and [event invitees](/groups/using-groups-for-events) so you do not re-select the same people every time.
* **Keep groups up to date**: When roles or membership change, [add or remove](/groups/assign-members) people from groups so future emails and invites go to the right set.
* **Avoid too many tiny groups**: A few well-named groups are easier to manage than many overlapping ones. Use [custom columns](/members/custom-columns) and [filters](/members/filters-and-search) for one-off or complex segments.
## Dues groups vs one-off assignments
* **Use a dues group** when you have a named "campaign" (e.g. "Fall 2025 dues") with one or more tiers (options) and optional content on the pay page. Assign members to the group/option so reporting and pay pages are consistent.
* **Use one-off assignments** when the amount or context is ad hoc (e.g. a single event fee, a one-time fine). You can still add a description and due date without creating a dues group.
* **Same member, multiple assignments**: A member can have multiple dues assignments (e.g. dues + event fee). Each has its own pay link; share the right link for each obligation.
## Emails
* **Templates first**: Build [templates](/emails/templates) for recurring messages (newsletter, reminders). Use [drafts](/emails/drafts) and [variables](/emails/variables) for one-off content (event date, link) so you do not edit the template every time.
* **Test with a small list**: Before sending to a large group, send to yourself or a test group to confirm subject, body, and variables.
* **Recipients**: Double-check [recipients](/emails/recipients) (group vs all members) and the count before sending. You cannot recall an email.
## Events
* **Invite in good time**: Send [event invites](/events/invite-members) early so members have time to RSVP and pay. Use [reminders](/events/reminders) if available.
* **Mark attendance**: Use the [attendance link](/events/attendance) after the event so you have a record of who showed up. Helpful for engagement and follow-up.
* **Paid events**: Set the amount and [waive](/events/event-payments) where appropriate (e.g. speakers, volunteers) before or right after sending invites.
## Website and store
* **Publish when ready**: Keep pages [draft](/website/publishing) until content and links are correct. Then publish and share the URL.
* **Merch variants**: Define [options](/merch/products-and-variants) for every size/color combination you sell so the [storefront](/merch/storefront) shows the right price and availability. Use clear labels (e.g. "M / Blue") for customers.
## Security and access
* **Limit admins**: Only give the **admin** role to people who need to manage the org. Use [member](/members/roles-and-permissions) for everyone else.
* **Join code**: Do not post the [join code](/settings/join-code-and-invite) publicly if you want to control who joins. Share the [invite link](/settings/join-code-and-invite) only with intended audiences.
* **Stripe and bank**: Complete [Stripe Connect](/getting-started/stripe-connect) and [bank details](/getting-started/bank-details) with the correct legal and bank information. Keep payouts and tax details up to date in Stripe.
# Common issues
Source: https://docs.rowhouse.co/guides/common-issues
Cross-feature fixes: member cannot pay, email not received, event not showing
Quick pointers for issues that span multiple features.
## Member cannot pay (dues or event)
* **Pay link**: Ensure they use the **link from their invite or dues email**, not a generic event or org page. Each assignment has its own pay link.
* **Stripe**: Your org must have [Stripe Connect](/getting-started/stripe-connect) complete. If Connect is incomplete, all pay links will fail.
* **Card**: They should try another card or contact their bank. Rowhouse does not control card declines.
* **Already paid**: If the assignment is already marked paid, the link may show "already paid". Check [Dues](/dues/overview) or the event's invite list for status.
See [Dues troubleshooting](/dues/troubleshooting) and [Events troubleshooting](/events/troubleshooting).
## Email not received
* **Spam**: Ask the recipient to check spam and promotions and to add the sender to contacts.
* **Address**: Confirm the member's **email** in [Members](/members/edit-and-remove) is correct. Resend the email or pay link after fixing.
* **Send**: For bulk emails, ensure you clicked **Send** and chose [recipients](/emails/recipients). Check [Campaigns](/emails/campaigns) for status (sent vs failed).
* **Plan**: Emails may require a [paid plan](/guides/plan-limits). Upgrade if the Emails section is locked.
See [Emails troubleshooting](/emails/troubleshooting).
## Event not showing or wrong list
* **Org**: Confirm you are in the correct **organization** (club switcher). Events are per org.
* **Calendar**: If you use [calendars](/events/calendars), filter by calendar or "All" to see the event.
* **Past vs upcoming**: Switch the list to **Upcoming** or **Past** (if the UI has that filter).
* **Public page**: For the **public** event page to show, the event must exist and (if applicable) be published. Share the correct URL from the event's "View public page" or share link.
See [Events troubleshooting](/events/troubleshooting).
## Cannot access a feature (locked)
* **Plan**: Many features (emails, website, dues, merch, analytics) require a [paid plan](/guides/plan-limits). Upgrade in [Subscription](/settings/subscription).
* **Role**: Only **admins** can access Settings, Subscription, and some other areas. See [Roles and permissions](/members/roles-and-permissions). Ask an admin to promote you or to perform the action.
* **Stripe**: Payment-related features (dues, events with payment, merch) require [Stripe Connect](/getting-started/stripe-connect) to be complete.
## Payment or payout delayed
* **Transaction**: Payments usually appear in [Transactions](/finance/transactions) within seconds. If not, refresh and check [Finance troubleshooting](/finance/troubleshooting).
* **Payout**: [Payouts](/finance/payouts) follow Stripe's schedule (e.g. 2 business days or weekly). First payouts can take longer. See [Payouts](/finance/payouts) and [Finance troubleshooting](/finance/troubleshooting).
## More help
* Use the **Support** or **Contact** link in the app or docs footer.
* Check the **troubleshooting** page for each feature: [Getting started](/getting-started/troubleshooting), [Members](/members/troubleshooting), [Events](/events/troubleshooting), [Emails](/emails/troubleshooting), [Dues](/dues/troubleshooting), [Website](/website/troubleshooting), [Finance](/finance/troubleshooting), [Settings](/settings/troubleshooting).
# Glossary
Source: https://docs.rowhouse.co/guides/glossary
Definitions for club, membership, dues group, ledger, and more
Definitions of terms used in Rowhouse docs and product.
**Admin**\
A member with the **admin** role. Admins can manage the organization: members, groups, events, emails, website, dues, merch, settings, and subscription. Only admins see Settings and Subscription in the sidebar.
**Assignment (dues)**\
A single dues obligation: one member, one amount, optional due date and description. Each assignment has a status (unpaid/paid) and a unique **pay link**.
**Calendar**\
A named group of events (e.g. "Social events"). Events can be assigned to a calendar. Calendar members may be default invitees for events on that calendar.
**Club**\
Your **organization** in Rowhouse (e.g. a club, chapter, or team). The club has a name, slug, logo, members, events, dues, and settings. Used interchangeably with "organization" in the docs.
**Draft (email)**\
An email prepared for sending, built from a **template** with optional custom variables. You choose recipients and send from the draft.
**Dues group**\
A named set of dues (or merch) with optional **options** (tiers/variants) and block-based content. Type "dues" for dues; type "merch" for the store. Used when assigning dues or selling products so the pay/store page can show the right amount and content.
**Event invite**\
A record linking one **member** to one **event**: RSVP status, attendance, and (for paid events) payment status and amount. Invitees receive an email with a link to RSVP and pay.
**Group**\
A label or tag for members (e.g. "Board", "Class of 2026"). Members can belong to multiple groups. Groups are used to send emails or invite to events by group.
**Ledger**\
A record of financial activity: payments (dues, events, merch) and sometimes payouts. Used for balance and audit.
**Member / membership**\
One person's association with one **club**. A member has name, email, phone, role (admin or member), optional profile picture and custom column values, and can belong to **groups**.
**Merch group**\
A **dues group** with type "merch": defines a product with custom properties (e.g. size, color) and **options** (variants with prices). Powers the **storefront** and cart/checkout.
**Option (dues group)**\
A selectable tier or variant in a dues group: label and amount. For dues, options are tiers (e.g. "Standard $50"). For merch, options are product variants (e.g. "M / Blue" at $25).
**Organization**\
Same as **club**: the entity you create or join (name, slug, members, events, dues, settings).
**Pay link**\
The unique URL for a dues (or event) assignment that the member opens to pay. Sharing the pay link is how you collect payment from that member.
**Payout**\
A transfer of funds from Stripe to your connected bank account. Payouts follow Stripe's schedule (e.g. rolling or weekly).
**Slug**\
A URL-friendly identifier (lowercase, letters, numbers, hyphens). Used for the **club** (e.g. `my-club` in `rowhouse.co/my-club`) and for **pages**, **dues groups**, and **merch groups**.
**Storefront**\
The public store page where customers browse merch, select variants, and add items to the cart. Reached via the store URL (e.g. `rowhouse.co/store/org-slug`).
**Template (email)**\
A reusable email design (subject and body) with variables (e.g. `{{name}}`). You create **drafts** from templates and send to recipients.
**Transaction**\
A single payment record: who paid, amount, type (dues/event/merch), date. Viewed in Finance → Transactions.
**Variable (email)**\
A placeholder in a template or draft (e.g. `{{name}}`, `{{email}}`) that is replaced per recipient when sending. Custom variables are set per draft.
# Plan limits
Source: https://docs.rowhouse.co/guides/plan-limits
What is included in free, pro, and premium plans
Rowhouse offers **free**, **pro**, and **premium** plans. Higher plans unlock more features, higher member limits, and lower processing fees.
## Member limits
* **Free**: Up to **25 members** per organization.
* **Pro**: Up to **200 members** per organization.
* **Premium**: **Unlimited** members.
If you exceed your plan's member limit, you must upgrade before adding more members. Downgrading is only allowed if your current member count fits within the new plan's limit.
## Features by plan
| Feature | Free | Pro | Premium |
| ----------------------- | -------- | --------- | --------- |
| **Members** | Up to 25 | Up to 200 | Unlimited |
| **Analytics** (website) | No | Yes | Yes |
| **QuickBooks export** | No | Yes | Yes |
| **Multi-chapter** | No | No | Yes |
| **AI insights** | No | No | Yes |
| **Dedicated support** | No | No | Yes |
Emails, website (pages), dues, merch, and payouts typically require a **paid plan** (pro or premium). The exact locking of these features may be enforced in the app; when a feature is locked, you will see an upgrade prompt (e.g. in the sidebar or when opening the section).
## Pricing (typical)
* **Free**: \$0/month.
* **Pro**: e.g. \$10/month (check the app or [Subscription](/settings/subscription) for current price).
* **Premium**: e.g. \$25/month (check the app for current price).
Prices may be shown monthly or yearly (with a discount for annual billing). See the Subscription page in the app for exact amounts.
## Processing fees
* **Free**: e.g. 10% + 30c per transaction (dues, events, merch).
* **Pro**: e.g. 8% + 30c per transaction.
* **Premium**: e.g. 5% + 30c per transaction.
Exact percentages are defined in the app. See [Processing fees](/finance/processing-fees).
## Upgrade or change plan
* Go to **Settings** → **Subscription** and choose **Upgrade** (or **Change plan**). Select the plan and billing interval and complete payment. Your new limits and features apply immediately. See [Subscription](/settings/subscription).
# Introduction
Source: https://docs.rowhouse.co/index
Welcome to Rowhouse — all-in-one club, chapter, and team management
Rowhouse helps you manage dues, members, events, and payments in one place. Stop juggling spreadsheets and multiple apps.
## Who it's for
* **Clubs and chapters** (student organizations, fraternities, sororities)
* **Teams and committees** that collect dues and run events
* **Any organization** that needs member management, event RSVPs, and payment collection
## Get started
Sign up, create or join an organization, add members, and run your first dues or event.
## Core features
Add members, CSV import, custom columns, roles, and filters.
Organize members with groups and use them for emails and events.
Create events, send invites, track RSVPs and attendance, collect payments.
Templates, drafts, and bulk sending to members or groups.
Build and publish your organization's website with the page editor.
Assign dues, send pay links, track payments and ledger.
Sell merch with variants (e.g. size/color) and a public storefront.
Transactions, payouts, subscription, and club settings.
## Account and organization
Create an account and sign in with email or Google.
Set up your club and complete onboarding.
Join via invite link or join code.
Fix common sign-up, login, and onboarding issues.
## Guides and reference
What's included in free, pro, and premium plans.
Definitions for club, membership, dues group, ledger, and more.
# Add members
Source: https://docs.rowhouse.co/members/add-members
Add a single member or import many via CSV
Add people to your organization one at a time or in bulk with a CSV upload.
## Add one member
1. Go to **Members** in the sidebar.
2. Click **Add member** (or **Add**).
3. Enter:
* **First name** and **Last name** (or **Name**, depending on the form)
* **Email** (recommended so they can receive emails and pay links)
* **Phone** (optional; useful for payment and SMS if you use it)
4. Click **Save** or **Add member**. The new member appears in the list.
Required fields may vary. Email is usually required if you plan to send them dues links or event invites by email.
## Import members with CSV
For many members at once, use **Import** on the Members page and upload a CSV file. Rowhouse will map columns to name, email, phone, and optional custom fields. See [CSV upload](/members/csv-upload) for:
* Supported column names and format
* Column mapping and handling duplicates
* What happens if some rows fail
Use a spreadsheet (Excel or Google Sheets), then export as CSV. Ensure the first row has column headers (e.g. `email`, `first_name`, `last_name`).
## Members who join themselves
Members can be created automatically when they:
* **Pay dues** via a [pay link](/dues/pay-link) (they enter name, email, phone at checkout)
* **Pay for an event** or **RSVP** via an event link
* **Join via public form** or **join link** if you've set that up. See [Public join](/members/public-join).
Those members will appear in the list with **Joined via payment** (or similar) so you can see how they were added.
## Next steps
* Assign [roles](/members/roles-and-permissions) (e.g. promote to admin).
* Add members to [groups](/groups/assign-members).
* [Assign dues](/dues/assigning-dues) or [invite to events](/events/invite-members).
# CSV upload
Source: https://docs.rowhouse.co/members/csv-upload
Import members from a CSV file and map columns
Import many members at once by uploading a CSV file. Rowhouse maps columns to name, email, phone, and optional custom fields.
## Prepare your CSV
1. Create a spreadsheet (Excel, Google Sheets) with one row per member.
2. **First row** must be headers. Use recognizable column names so Rowhouse can map them:
* **email** (or Email)
* **first\_name** (or First Name, firstName)
* **last\_name** (or Last Name, lastName)
* **name** (full name if you do not use first/last)
* **phone** (or Phone)
* Any [custom column](/members/custom-columns) names you have defined (exact match)
3. Save or export as **CSV** (comma-separated values). UTF-8 encoding is best for special characters.
If you use custom columns, create those columns in Rowhouse first (Members, Custom columns or Settings). The CSV headers must match the custom column names exactly.
## Upload and map
1. Go to **Members** and click **Import** (or **Upload CSV**).
2. Select your CSV file or drag it into the upload area.
3. Rowhouse will preview the first rows and suggest column mapping. Confirm or change which CSV column maps to email, first name, last name, phone, and custom fields.
4. Review duplicates: if a row has an email that already exists in the org, you may be asked to skip, update, or add as duplicate. Prefer **Skip** or **Update** to avoid duplicate members.
5. Start the import. The import may run in the background for large files. Check the Members list or any success/error message when it finishes.
For very large files (e.g. thousands of rows), split into smaller CSVs or run one import at a time to avoid timeouts.
## After import
* New members appear in the **Members** list. You can [edit](/members/edit-and-remove) any of them.
* If some rows failed (e.g. invalid email, duplicate), Rowhouse may show a summary or export of failures. Fix the CSV and re-import the failed rows if needed.
## Troubleshooting
* **Column not found**: Ensure custom column names in the CSV match exactly the names in Rowhouse (case-sensitive).
* **Duplicates**: Use the duplicate handling option during mapping, or clean your CSV so each email appears once.
* **Import fails or times out**: Reduce file size (e.g. under 1,000 to 2,000 rows per file) and try again. See [Members troubleshooting](/members/troubleshooting).
# Custom columns
Source: https://docs.rowhouse.co/members/custom-columns
Add custom fields to your member list (e.g. graduation year, shirt size)
Custom columns let you store extra information for each member (e.g. graduation year, shirt size, committee) and use it for filtering and display.
## Add a custom column
1. Go to **Members** and open **Custom columns** (or **Settings** → **Member columns**, depending on your app).
2. Click **Add column** (or **Add custom column**).
3. Set:
* **Name**: Internal name used in the list and for CSV mapping (e.g. `Graduation Year`). Use letters, numbers, spaces; avoid special characters if you use CSV import.
* **Data type**: **String**, **Number**, **Date**, or **Boolean**.
* **Sort order**: Order in which the column appears in the list (lower numbers first).
4. Save. The column appears in the member list and in the add/edit member form.
Column names must be unique per organization. After creation, changing the name may affect CSV imports that use the old name.
## Data types
* **String**: Text (e.g. major, shirt size "M").
* **Number**: Numeric values (e.g. graduation year 2026, ID number).
* **Date**: Date only (e.g. join date, birth date).
* **Boolean**: Yes/No or true/false (e.g. "Board member", "Paid member").
## Fill in values
* **Per member**: When [editing a member](/members/edit-and-remove), fill in the custom column values.
* **Bulk**: Use [CSV upload](/members/csv-upload) and include a column whose header matches the custom column name exactly. Rowhouse will map and import those values.
## Filter and sort
* In the Members list, use [filters](/members/filters-and-search) to show only members where a custom column equals (or contains) a value.
* Sort by a custom column if the UI supports it (column header click or sort dropdown).
Use consistent values (e.g. "2025" not "Fall 2025" for a graduation year number column) so filtering and sorting work as expected.
## Reorder or remove
* **Reorder**: Change the **sort order** of custom columns so they appear in the order you want.
* **Remove**: Delete the column from the custom columns settings. Existing values for that column are removed from member records; other data is unchanged.
# Edit and remove members
Source: https://docs.rowhouse.co/members/edit-and-remove
Update member details, promote to admin, or remove from the organization
Edit a member to change their name, email, phone, role, or custom column values. Remove a member when they leave the organization.
## Edit a member
1. Go to **Members** and click the member (or **Edit** on their row).
2. Update **name**, **email**, **phone**, **role** (admin/member), and any [custom columns](/members/custom-columns).
3. Click **Save**. Changes apply immediately.
If you change their email, any future emails or pay links sent from Rowhouse will use the new address. Past sent emails still show the old address in history.
## Promote to admin
1. Open the member for editing (as above).
2. Set **Role** to **Admin**.
3. Save. They will now see **Settings** and **Subscription** and can manage the org. See [Roles and permissions](/members/roles-and-permissions).
## Remove a member
1. Go to **Members** and open the member.
2. Find **Remove** or **Remove from organization** (often at the bottom or in a menu).
3. Confirm. The member is removed from the organization's member list.
Removing a member does not refund dues or event payments they already made. It only removes their membership record. Their payment and RSVP history may still appear in transactions and event lists for accounting purposes.
* **Dues**: Unpaid dues assigned to them may remain (e.g. marked unpaid). You can [waive or cancel](/dues/waiving-and-cancelling) those assignments if needed.
* **Events**: Their event invites and RSVPs may remain in event data for history. You can leave as-is or adjust in the event's invite list if the UI allows.
## Profile picture
To add or change a member's profile picture, see [Profile pictures](/members/profile-pictures).
# Filters and search
Source: https://docs.rowhouse.co/members/filters-and-search
Find members by group, role, custom columns, or search
Use **filters** and **search** on the Members page to narrow the list and find specific people.
## Search
* In the **Members** list, use the **search** box (often at the top).
* Type part of a **name** or **email**. The list updates to show only members whose name or email matches.
* Search is typically case-insensitive and matches anywhere in the field (e.g. "smith" matches "Smith" and "[smith@email.com](mailto:smith@email.com)").
Search usually applies to name and email only. To find by group or custom column, use filters.
## Filter by group
1. Use the **Group** or **Filter by group** dropdown (or similar).
2. Select one or more [groups](/groups/overview). The list shows only members who belong to at least one of the selected groups.
3. Clear the filter to show all members again.
Use this to, for example, see only "Board" members or "Class of 2026" before sending an email or assigning dues.
## Filter by role
* Use the **Role** filter (if available) to show only **Admins** or only **Members**. Helpful when you want to review who has admin access.
## Filter by custom columns
* If you use [custom columns](/members/custom-columns), the filter dropdown may include those columns.
* Select a column and a value (e.g. **Graduation Year** = 2026) to show only members with that value. Exact match vs "contains" depends on the UI.
## Combine filters
* You can often combine search with one or more filters (e.g. search "john" and filter by group "Board"). The list shows members that match all applied criteria.
* Clear filters or search to return to the full list.
## Export (if available)
* Some plans or views may offer **Export** to download the current (filtered) list as CSV. Use it after applying filters to get only the subset you need.
# Members overview
Source: https://docs.rowhouse.co/members/overview
Manage your organization's member list, roles, and data
The **Members** section is your central list of everyone in your organization. You can add members manually, import from CSV, assign roles, add custom columns, and filter or search.
## What is a member?
A **member** (membership) is one person's association with one organization. Each member has:
* **Name**, **email**, and optionally **phone**
* **Role**: **admin** or **member**. Admins can manage the org (settings, dues, events, emails, etc.); members typically only view or act on their own (e.g. pay dues, RSVP).
* Optional **profile picture**
* Optional **custom column** values (e.g. graduation year, shirt size) if you have set up [custom columns](/members/custom-columns)
* **Groups**: members can belong to [groups](/groups/overview) (e.g. Board, Class of 2026) for emails and filtering
## Members list
* Open **Members** in the sidebar to see the full list.
* Use **Add member** to add one person, or **Import** to upload a [CSV](/members/csv-upload).
* Use [filters and search](/members/filters-and-search) to find people by group, role, or custom fields.
* Click a member to view or [edit](/members/edit-and-remove) their details, or to assign them to groups.
## Roles and permissions
* **Admin**: Can manage members, events, dues, emails, website, settings, and subscription. Only admins see **Settings** and **Subscription** in the sidebar.
* **Member**: Can view the dashboard (depending on your org) and use member-facing links (e.g. pay dues, RSVP). Cannot change org settings or other members data.
See [Roles and permissions](/members/roles-and-permissions) for details. To promote a member to admin, see [Edit and remove](/members/edit-and-remove).
## Related features
* **Groups**: Organize members into [groups](/groups/overview) and use them for [emails](/groups/using-groups-in-emails) and event invitees.
* **Dues**: [Assign dues](/dues/assigning-dues) to members and share [pay links](/dues/pay-link).
* **Events**: [Invite members](/events/invite-members) to events and track RSVPs.
Add one member at a time or import from CSV.
# Profile pictures
Source: https://docs.rowhouse.co/members/profile-pictures
Upload and manage member profile pictures
Members can have a **profile picture** (avatar) that appears in the dashboard and, depending on your setup, in member lists or next to their name.
## Upload a profile picture (for yourself)
1. Click your **avatar** at the bottom of the sidebar and open **User Preferences** (or **Profile**).
2. Find **Profile picture** or **Avatar** and click **Upload** (or the image area).
3. Choose an image file (e.g. JPG, PNG). Crop or adjust if the UI allows.
4. Save. Your avatar updates in the sidebar and anywhere your profile is shown.
## Upload a profile picture (for another member)
1. Go to **Members** and open the member (click the row or **Edit**).
2. Find **Profile picture** or **Avatar** and click **Upload** (or the placeholder).
3. Select an image file. Save. The member's picture appears in the list and on their profile.
Some orgs may restrict who can upload photos for other members (e.g. admins only). Members may be able to upload their own if the app allows.
## Supported formats and size
* Common image formats (e.g. JPG, PNG) are usually supported. Prefer square or near-square images so avatars don't crop oddly.
* Large files may be resized automatically. If upload fails, try a smaller image (e.g. under 2 MB).
## Remove a profile picture
* In the same place you uploaded (User Preferences for yourself, or the member edit form for others), look for **Remove** or **Clear** next to the picture. The avatar will revert to initials or a default icon.
# Public join
Source: https://docs.rowhouse.co/members/public-join
Let people join your organization via a public form or link
You can allow people to **join your organization** without an admin adding them manually. They use a **public join** form or link and, after submitting, become members.
## How public join works
* You share a **join link** (e.g. `rowhouse.co/clubs/join` with your org context, or a custom invite page).
* Someone opens the link, enters their name, email, and optionally phone (and any required fields you've set).
* They submit the form. Rowhouse creates a **membership** for your organization and may send a confirmation email.
* They may be marked as **Joined via payment** or **Joined via form** (depending on implementation) so you can see how they joined.
Public join may require your organization to have **join** or **invite** settings enabled. See [Join code and invite](/settings/join-code-and-invite) for how admins configure join links and codes.
## When to use it
* **Recruitment**: Let interested people sign up without waiting for an admin to add them.
* **Events**: Point attendees to the join link so they become members before or after an event.
* **Dues and merch**: New members can then receive dues assignments or shop your store; you can also send them the join link after they pay if they weren't already members.
## Join code vs invite link
* **Join code**: A short code (e.g. `ABC123`) that existing Rowhouse users enter in the app (club switcher → Join Club) to join your org. See [Join an organization](/getting-started/join-organization).
* **Invite link**: A URL you share (e.g. email, social) that opens the public join form. Anyone with the link can open it and submit; they don't need a Rowhouse account first (one may be created for them if they use email).
Configure both in [Join code and invite](/settings/join-code-and-invite).
## After they join
* New members appear in **Members** with the role **member** by default. Promote them to **admin** if needed. See [Roles and permissions](/members/roles-and-permissions).
* You can add them to [groups](/groups/assign-members), [assign dues](/dues/assigning-dues), or [invite to events](/events/invite-members).
# Roles and permissions
Source: https://docs.rowhouse.co/members/roles-and-permissions
Admin vs member: who can do what
Each member has a **role**: **admin** or **member**. Roles control what they can see and do in the organization.
## Admin
**Admins** can:
* View and edit **Members**, **Groups**, **Events**, **Emails**, **Website** (pages), **Dues**, **Merch**, **Transactions**, **Payouts**
* Add, edit, and remove members; assign members to groups
* Create and edit events, send invites, manage RSVPs and attendance
* Create email templates and drafts, send emails to members or groups
* Create and edit website pages, publish or unpublish
* Assign dues, waive or cancel, view ledger
* Create and edit merch groups and products, view store
* View transactions and payouts
* Access **Settings** (club name, logo, join code, etc.) and **Subscription** (plan, billing, Stripe)
Only admins see **Settings** and **Subscription** in the sidebar.
## Member
**Members** (non-admin) typically:
* Can view the dashboard or member-facing areas as configured by your org
* Use links sent to them: pay [dues](/dues/pay-link), [RSVP to events](/events/rsvp), pay for events or merch
* Cannot change org settings, other members' data, dues assignments, or event details
* Cannot send bulk emails or edit website pages
Exact member permissions can depend on your plan and app configuration. When in doubt, assume members can only act on their own (pay, RSVP) unless they are admins.
## How to change a member's role
1. Go to **Members** and open the member (click the row or **Edit**).
2. Find **Role** and set it to **Admin** or **Member**.
3. Save. The member's access updates immediately.
Only an **admin** can promote another member to admin or demote an admin to member. See [Edit and remove](/members/edit-and-remove).
Keep the number of admins small (e.g. leadership only) so only trusted people can change settings and financial data.
# Members troubleshooting
Source: https://docs.rowhouse.co/members/troubleshooting
Fix import failures, duplicates, missing columns, and permissions
Common issues when adding, editing, or importing members.
## CSV import
### Import fails or shows errors
* **Column mapping**: Ensure the first row of your CSV has headers and that you've mapped **email** (and name fields) correctly. See [CSV upload](/members/csv-upload).
* **File format**: Save as **CSV** (comma-separated), not Excel. Use UTF-8 if you have special characters.
* **File size**: Very large files (e.g. 5,000+ rows) may time out. Split into smaller files (e.g. 1,000–2,000 rows) and import in batches.
* **Custom columns**: If you're importing custom column values, the header names must **exactly match** the custom column names in Rowhouse (case-sensitive). Create the custom columns first, then import.
### Duplicate members after import
* During import, use the **duplicate handling** option: **Skip** or **Update** existing members by email instead of creating duplicates.
* If you already have duplicates: search by email, then [edit](/members/edit-and-remove) one record and **remove** the duplicate member, or merge data manually and remove the extra.
### Some rows didn't import
* Check the summary or error report after import (if shown). Common causes: invalid email format, required field missing, or duplicate email with "skip" selected. Fix the CSV and re-import the failed rows in a new file if needed.
## Custom columns
### Custom column not showing in CSV mapping
* The CSV header must **exactly match** the custom column name (spelling and case). Create the [custom column](/members/custom-columns) in Rowhouse first, then use the same name in the CSV.
### Values not saving or showing
* Ensure the **data type** matches (e.g. number column for years, date for dates). Invalid values may be ignored or show as blank.
## Permissions
### I can't edit a member / I don't see Edit
* You must be an **admin** to edit other members or change roles. See [Roles and permissions](/members/roles-and-permissions). Ask an admin to promote you or to make the edit.
### I don't see the Members page
* Confirm you're in the correct **organization** (club switcher). If you're a **member** (not admin), your org may restrict which pages you can see; admins always have access to Members.
## Profile picture
### Upload fails or picture doesn't show
* Use a supported format (e.g. JPG, PNG) and a reasonable size (e.g. under 2 MB). Try a smaller or different image. If the problem continues, try another browser or clear cache.
## Still stuck?
* [Getting started troubleshooting](/getting-started/troubleshooting) for sign-up, login, and onboarding.
* [Dues troubleshooting](/dues/troubleshooting) or [Events](/events/troubleshooting) if the issue is with paying or RSVPing.
# Cart and checkout
Source: https://docs.rowhouse.co/merch/cart-and-checkout
How customers add items and pay (Stripe)
Customers **add items** to the cart from the [storefront](/merch/storefront), then complete **checkout** with card payment (Stripe). You see orders in **Transactions** and receive funds per your [payout](/finance/payouts) schedule.
## Cart
* On the product page, the customer selects **variant** (e.g. size, color) and clicks **Add to cart**. The item (with variant and price) is added to the cart. They can continue shopping or go to checkout.
* Cart is usually stored in the browser (session or cookie) until they complete checkout or leave. Cart contents may be shown in a sidebar or cart icon with quantity.
## Checkout
1. The customer clicks **Checkout** (or **View cart** then **Checkout**).
2. They may be asked for **name**, **email**, **phone** (and optionally address) for the order. If they are already a member, some info may be pre-filled.
3. They enter **payment** (card) on the secure Stripe checkout page. Rowhouse sends the order and payment to Stripe; your org receives the amount minus [processing fees](/finance/processing-fees).
4. After success, they see a **confirmation** (and may receive an email if configured). The order appears in your **Transactions** (and possibly a dedicated Orders view if the app has one).
Rowhouse does not typically handle shipping or inventory fulfillment; you fulfill orders offline. Use transaction or order details (customer, items, variant) to ship and track.
## Multiple items
* Customers can add multiple items (same or different products) to the cart and pay once at checkout. The total is the sum of each item's price (per variant).
## Failed payment
* If the card is declined or payment fails, the customer sees an error and can try again or use another card. No order is created until payment succeeds. See [Merch troubleshooting](/merch/troubleshooting) for store or checkout errors.
# Merch editor
Source: https://docs.rowhouse.co/merch/merch-editor
Block-based content for merch group pages
The **merch editor** lets you add **block-based content** (text, images, buttons) to a merch group. This content is shown on the product or store page for that group (e.g. above or below the variant selector and add-to-cart).
## Where to find it
* Open the **merch group** (Finance → Merch → \[group name]) and look for **Edit content**, **Page content**, or **Merch editor**. You may be taken to a Puck-style editor (same concept as the [website page editor](/website/page-editor) or [dues group](/dues/dues-groups) content).
## What you can add
* **Text**: Headlines, descriptions, sizing info, care instructions.
* **Images**: Product photos, lifestyle shots.
* **Buttons**: e.g. "Size guide" linking to a page.
* **Columns** or **sections**: Layout blocks to arrange content.
Content is saved with the merch group and displayed on the public [storefront](/merch/storefront) product page for that group.
Use the merch editor to add a short description, sizing chart link, or return policy so customers have the info they need before adding to cart.
## No code required
* The editor is drag-and-drop. You do not need to write HTML. Change or remove blocks anytime and save; the live store updates when you publish or save (depending on the app).
# Merch overview
Source: https://docs.rowhouse.co/merch/overview
Sell merch with variants and a public storefront
**Merch** lets you sell items (e.g. t-shirts, hats) with **variants** (size, color) through a **storefront** and **cart/checkout**. Merch is built on **dues groups** with type "merch": options are product variants and custom properties collect choices (e.g. size, color).
## What you can do
* **Create a merch group**: A dues group with type "merch", name, slug, [custom properties](/merch/create-merch-group) (e.g. size, color), and [options](/merch/products-and-variants) (variants with prices).
* **Storefront**: A public page (e.g. `rowhouse.co/store/your-org-slug` or per-group slug) where visitors browse and add items to the **cart**.
* **Cart and checkout**: Customers complete payment (Stripe); you see orders in **Transactions** and can fulfill offline.
* **Merch editor**: Optional block-based content (like [dues group](/dues/dues-groups) content) for the product or store page.
## Where to find it
* **Finance** → **Merch** in the sidebar. Create and edit merch groups, view store link, and (if available) order or transaction summaries. Merch may require a **paid plan**. See [Plan limits](/guides/plan-limits).
## Related
* [Create merch group](/merch/create-merch-group), [Products and variants](/merch/products-and-variants)
* [Storefront](/merch/storefront), [Cart and checkout](/merch/cart-and-checkout), [Merch editor](/merch/merch-editor)
* [Troubleshooting](/merch/troubleshooting)
# Products and variants
Source: https://docs.rowhouse.co/merch/products-and-variants
Set up options (variants) and prices for merch
In a merch group, **options** are your product **variants**: each option has a **label** and **amount** (price). Custom properties (size, color) define what the customer picks; options map to those choices (e.g. "M / Blue" = \$25).
## Options (variants)
* Each **option** has:
* **Label**: Display name (e.g. "Medium - Blue", "Large - Green").
* **Amount**: Price in dollars (or cents, depending on the app).
* **Sort order**: Order shown in the list.
* **Metadata** (optional): e.g. `{"size":"M","color":"Blue"}` so the storefront can map the option to the selected size/color and show the right price.
* Create one option per variant (e.g. S Blue, S Green, M Blue, M Green, ...) or one per size if you only have one color.
## Custom properties and mapping
* **Custom properties** (e.g. Size, Color) define the dropdowns on the product page. When the customer selects "M" and "Blue", the app finds the option that matches (e.g. metadata `size: M, color: Blue`) and uses that option's **amount** at checkout.
* If you have a single product with no variants, you can create one option with one price and no or minimal custom properties.
Keep variant names consistent (e.g. "M" not "Medium" in metadata if your property options are "M") so the storefront can match correctly.
## Inventory (if supported)
* Some setups support **inventory** per variant (e.g. quantity). If available, set quantities so the storefront can show "Out of stock" and prevent over-selling. When not supported, you manage stock offline and remove or disable options when sold out.
# Storefront
Source: https://docs.rowhouse.co/merch/storefront
Public store URL and product pages
The **storefront** is the public page where customers browse your merch, select variants, and add items to the **cart**. Each merch group can have a product page; the store may list all groups or one group per URL.
## Store URL
* The main store URL is often `rowhouse.co/store/your-org-slug` (or similar). Your org slug is set when you [create the organization](/getting-started/create-organization). Share this link so customers can reach the store.
* A specific product (merch group) may be at `rowhouse.co/store/your-org-slug/group-slug` (or `/store/slug/product-slug`). Check the Merch section for "View store" or "Store link" to get the exact URL.
## What customers see
* **Store listing**: List of products (merch groups) with name, image (if set), and price range or starting price.
* **Product page**: Clicking a product opens its page with:
* Name, description, and block content (if you added [merch editor](/merch/merch-editor) content)
* **Custom property** selectors (size, color, etc.)
* **Price** for the selected variant (from the matching option)
* **Add to cart** (or **Buy**). See [Cart and checkout](/merch/cart-and-checkout).
Use clear product names and (if available) images so the store looks professional. Test the storefront in an incognito window to see the customer experience.
## Slug and visibility
* The merch group **slug** is used in the product URL. Ensure the slug is readable (e.g. `club-tshirt-2025`). Published/active merch groups are visible on the store; draft or inactive groups may be hidden depending on the app.
# Merch troubleshooting
Source: https://docs.rowhouse.co/merch/troubleshooting
Fix store not loading, variant issues, and checkout errors
Common issues with the storefront and merch.
## Store not loading or 404
* **URL**: Confirm you are using the correct store URL (e.g. `rowhouse.co/store/your-org-slug`). Check **Merch** for the "Store link" or "View store" button to copy the exact URL.
* **Slug**: Ensure your org has a valid **slug** and that the merch group slug is correct. Typos in the URL cause 404.
* **Publish**: Some apps require the merch group to be "published" or "active". Check the group settings and ensure it is visible on the store.
* **Plan**: Merch may require a **paid plan**. See [Subscription](/settings/subscription) and [Plan limits](/guides/plan-limits).
## Variant out of stock or wrong price
* **Options**: Each variant (e.g. M Blue) must have an **option** with the correct **amount**. If the price is wrong, edit the merch group and fix the option amount. See [Products and variants](/merch/products-and-variants).
* **Mapping**: If the customer selects Size M and Color Blue but the wrong price appears, check that the option **metadata** (e.g. `{"size":"M","color":"Blue"}`) matches your custom property values. Spelling and case must match.
* **Out of stock**: If you use inventory and a variant is out of stock, disable or remove that option (or set quantity to 0) so it does not appear or shows "Out of stock". When inventory is not supported, manage stock offline and update options as needed.
## Checkout errors
* **Payment declined**: The customer should try another card or contact their bank. Rowhouse does not control declines.
* **Stripe**: Checkout requires [Stripe Connect](/getting-started/stripe-connect) to be complete for your org. If Connect is incomplete, checkout will fail. Complete onboarding and try again.
* **Browser**: Have the customer try a different browser or device, and disable extensions that might block Stripe.
* **Cart empty**: If the cart is empty at checkout, the session may have expired. They can add items again and checkout.
## Order not showing in Transactions
* **Wait**: After payment, the transaction can take a few seconds to appear. Refresh **Finance** → **Transactions** and filter by type "merch" or "store" if available.
* **Webhook**: If Stripe webhooks were delayed or failed, the order might sync later. If the charge appears in Stripe but not in Rowhouse, contact support so they can reconcile.
# Quickstart
Source: https://docs.rowhouse.co/quickstart
Get your organization on Rowhouse in a few steps
Follow these steps to go from sign-up to collecting dues or running your first event.
## Step 1: Sign up
1. Go to [Rowhouse](https://rowhouse.co) and click **Sign up** (or **Get started**).
2. Sign up with **email** or **Google**.
3. If you use email, verify your address using the link we send.
Use the same email you'll use for your organization so you can be added as an admin.
## Step 2: Create or join an organization
**Create a new organization**
1. After signing in, click **Create Club** (or use the club switcher in the sidebar).
2. Enter your **organization name** and choose a **slug** (e.g. `my-club` for `rowhouse.co/my-club`).
3. Complete the onboarding steps: connect Stripe (for payments), add bank details if you'll receive payouts, and finish your profile if prompted.
**Join an existing organization**
1. Use the **Join Club** option in the sidebar, or open the invite link your admin shared.
2. Enter the **join code** if you have one, or sign in and accept the invite.
See [Create an organization](/getting-started/create-organization) and [Join an organization](/getting-started/join-organization) for details.
## Step 3: Add members
1. Go to **Members** in the sidebar.
2. Click **Add member** and enter name, email, and optionally phone.
3. For many members at once, use **Import** and upload a CSV. See [CSV upload](/members/csv-upload) for column mapping and format.
Members can also join via a public join link or by paying dues/event fees; they'll be created automatically.
## Step 4: Set up your first dues or event
**Dues**
1. Go to **Finance** → **Dues**.
2. Optionally create a [dues group](/dues/dues-groups) (e.g. "Fall 2025 dues") with a default amount.
3. Select members and click **Assign dues**. Enter amount, description, and optional due date.
4. Share the **pay link** with members so they can pay online. See [Assigning dues](/dues/assigning-dues) and [Pay link](/dues/pay-link).
**Event**
1. Go to **Events** and click **Create event**.
2. Enter title, date/time, location, and optionally a payment amount.
3. **Invite members** and send invites. Members can RSVP and pay (if the event has a fee) via the link in the email. See [Create event](/events/create-event) and [Invite members](/events/invite-members).
## Next steps
* **Groups**: Create groups (e.g. "Board", "Class of 2026") and use them to [send emails to a group](/groups/using-groups-in-emails) or manage event invitees.
* **Emails**: Create [templates](/emails/templates) and [drafts](/emails/drafts), then [send](/emails/sending) to members or groups.
* **Website**: Build your org's site with [Pages](/website/pages) and the [page editor](/website/page-editor).
* **Merch**: Set up a [merch group](/merch/create-merch-group) and [storefront](/merch/storefront) to sell items with variants.
See what's included in free vs pro vs premium.
# Club settings
Source: https://docs.rowhouse.co/settings/club-settings
Organization name, logo, email, description, website, join code
**Club settings** (organization settings) control how your organization appears and how people can join. Only **admins** can edit these.
## Where to find it
* **Settings** in the sidebar (admin only). You may see **General**, **Organization**, or **Club** as the main section.
## What you can change
* **Name**: The full name of your organization (e.g. "Economics Club"). Shown in the club switcher, emails, and public pages.
* **Logo**: Upload a **logo** image (used in the sidebar, storefront, emails). Use a square or near-square image; the app may resize. See [Troubleshooting](/settings/troubleshooting) if upload fails.
* **Email**: Contact email for the org (e.g. for "Contact us" or sender display). Optional.
* **Description**: Short description of the org (for public pages or directory). Optional.
* **Website**: External website URL (e.g. your existing site). Optional.
* **Join code**: A code members or invitees use to [join the organization](/getting-started/join-organization). See [Join code and invite](/settings/join-code-and-invite).
The org **slug** (URL identifier) is usually set at creation and may not be editable, or may be editable only with care (URLs can break). Check the UI before changing the slug.
## Save
* After editing, click **Save** (or **Update**). Changes apply immediately. Logo and name updates may take a moment to appear everywhere (e.g. cache).
# Instant payouts
Source: https://docs.rowhouse.co/settings/instant-payouts
Enable faster payouts to your bank (if available)
**Instant payouts** (when available) send funds to your bank **within minutes** instead of waiting for Stripe's standard schedule (e.g. 2 business days or weekly). A fee usually applies per instant payout.
## Is it available?
* Instant payouts depend on your **Stripe account** and **region**. Not all accounts or countries support them. If you see **Instant payouts** in **Settings** (or **Finance** / **Payouts**), you can enable it there. If you do not see it, Stripe may not offer it for your account yet.
## How to enable
1. Go to **Settings** (or **Finance** → **Payouts**) and find **Instant payouts** (or **Faster payouts**).
2. Turn it **on** (toggle or button). You may be asked to confirm the fee (e.g. 1% of the payout amount, minimum \$0.50).
3. After enabling, future eligible payouts can be sent instantly. You may still have the option to use standard payouts for specific transfers; check the UI.
## Fees
* Instant payouts typically have a **per-payout fee** (e.g. 1% of the amount, with a minimum). Standard payouts are usually free. Use instant when you need funds quickly; use standard to avoid the fee when timing is not critical.
## Limits and eligibility
* Stripe may limit instant payout amount or frequency. If an instant payout fails or is not offered for a given transfer, the funds will go out on the next standard payout. Check Stripe Dashboard or support for your account's limits.
# Join code and invite link
Source: https://docs.rowhouse.co/settings/join-code-and-invite
Set the join code and get the invite link for your organization
Control how new members **join** your organization: **join code** (for existing Rowhouse users) and **invite link** (for sharing by email or social).
## Join code
* The **join code** is a short code (e.g. alphanumeric) that someone enters in Rowhouse when they click **Join Club** (from the club switcher). Only people who know the code can join this way.
* **Set or change**: In **Settings** (or **Club settings**), find **Join code** (or **Invite code**). Enter or generate a code and save. Share it only with people you want to join (e.g. members, recruits).
* **Reset**: Change the code if it was shared too widely or compromised. The old code stops working; share the new code with the right people.
Join code is optional. If left blank, joining may be by invite link only (if supported) or by admin-adding members.
## Invite link
* The **invite link** is a URL that you share (e.g. in email, social). When someone opens it, they can sign up or sign in and **accept the invite** to join your organization. The link may be generic (e.g. `rowhouse.co/clubs/join`) or include a token; behavior depends on the app.
* **Get the link**: In **Settings** or **Members**, look for **Invite link**, **Share invite**, or **Invite members**. Copy the URL and share it. You may be able to customize the message or see how many have joined via the link.
Use the invite link for recruitment (e.g. "Join us: \[link]") and the join code for existing Rowhouse users who you have already told the code.
## Who can join
* Anyone with the **join code** (and a Rowhouse account) can join by entering it.
* Anyone with the **invite link** can open it and join (they may get an account created if they sign up with email). Restrict sharing so only intended people join.
# Settings overview
Source: https://docs.rowhouse.co/settings/overview
Club settings vs user preferences, and who can edit
**Settings** in Rowhouse are split into **club (organization) settings** and **user preferences**. Only **admins** can change club settings; any user can change their own preferences.
## Club settings (organization)
* **Who**: Only **admins** of the organization see and edit these.
* **What**: [Club settings](/settings/club-settings) (name, logo, email, description, website, join code), [Subscription](/settings/subscription) (plan, billing), [Stripe Connect](/settings/stripe-connect), [Join code and invite](/settings/join-code-and-invite), [Instant payouts](/settings/instant-payouts) (if available).
* **Where**: **Settings** (and sometimes **Subscription**) in the sidebar; only visible when you are an admin.
## User preferences (your account)
* **Who**: Any logged-in user.
* **What**: Your **name**, **email**, **profile picture**, **theme** (light/dark). See [User preferences](/getting-started/user-preferences).
* **Where**: Click your **avatar** at the bottom of the sidebar → **User Preferences**.
## Switching organizations
* Settings are **per organization**. Use the [club switcher](/getting-started/switching-clubs) to change which org you are viewing. Your **user preferences** apply to your account everywhere; **club settings** apply only to the selected org.
See [Troubleshooting](/settings/troubleshooting) for common settings issues.
# Stripe Connect
Source: https://docs.rowhouse.co/settings/stripe-connect
View status, re-onboard, or disconnect Stripe
**Stripe Connect** links your organization to Stripe so you can accept payments (dues, events, merch) and receive payouts. View status and fix issues from Settings.
## Where to find it
* **Settings** (or **Subscription** / **Payments**) and look for **Stripe**, **Payments**, or **Connect**. You see whether Connect is **complete** or **incomplete** and a link to **complete setup** or **re-onboard**.
## Status
* **Complete**: Stripe Connect is fully set up. You can accept payments and receive payouts. No action needed unless Stripe asks for more information (e.g. annual review).
* **Incomplete**: One or more steps are missing (e.g. identity, bank, EIN). Click **Complete setup** (or **Connect Stripe**) to open Stripe's onboarding and finish. See [Stripe Connect](/getting-started/stripe-connect) for what Stripe asks for.
## Re-onboard
* If Stripe or Rowhouse asks for updated information (e.g. new bank account, verification), use the same **Complete setup** or **Connect** entry point. You will be taken to Stripe to update details. After finishing, status should return to complete.
## Disconnect
* **Disconnect** (if available) removes the link between your org and Stripe. You will **no longer** be able to accept payments (dues, events, merch) or receive payouts until you connect again. Use only if you are closing the org or moving to another system. Disconnecting does not refund customers or cancel Stripe; handle those separately if needed.
# Subscription
Source: https://docs.rowhouse.co/settings/subscription
Plan (free, pro, premium), upgrade, and billing
Your organization's **subscription** determines your **plan** (e.g. free, pro, premium) and what features you can use (emails, website, dues, merch, etc.). Only **admins** can view and change the subscription.
## Where to find it
* **Settings** → **Subscription** (or **Billing**), or use the **Subscription** link in the sidebar (admin only). You may be redirected to a billing portal or see the plan and upgrade options in the app.
## Plans
* **Free**: Limited features; many advanced features (emails, website, dues, merch) may be locked. See [Plan limits](/guides/plan-limits).
* **Pro**: Unlocks emails, website, dues, merch, and lower [processing fees](/finance/processing-fees). Billed monthly or yearly.
* **Premium**: Highest tier with more features and lowest fees. Billed monthly or yearly.
Exact plan names and inclusions depend on the product. Check the Subscription page and [Plan limits](/guides/plan-limits) for current details.
## Upgrade or change plan
* Click **Upgrade** (or **Change plan**) and select the plan and billing interval (monthly vs yearly). You may be taken to Stripe Checkout or a billing portal to enter payment method. After success, the new plan is active and locked features unlock.
## Billing and payment method
* **Payment method**: Stored with Stripe. Update it in the billing portal or the link Rowhouse provides (e.g. "Update payment method").
* **Invoices**: You may receive invoices by email from Stripe or Rowhouse. Download from the billing portal or Stripe Dashboard if needed.
* **Cancel**: If you cancel, you may keep access until the end of the billing period; then the plan reverts to free (or lapses). Locked features will be unavailable after that.
# Settings troubleshooting
Source: https://docs.rowhouse.co/settings/troubleshooting
Fix plan upgrade, Stripe connection, and logo upload
Common issues with club settings and subscription.
## Cannot change plan or upgrade
* **Payment method**: Ensure you have a valid **payment method** on file. Use **Update payment method** (or the billing portal link) to add or fix a card. Declined cards block upgrades.
* **Already on plan**: If you are already on the plan you want, there is nothing to change. If you want a higher plan, use **Upgrade** and select the new plan.
* **Permissions**: Only **admins** can change the subscription. If you are a member, ask an admin to upgrade or promote you to admin. See [Roles and permissions](/members/roles-and-permissions).
## Stripe not connected or incomplete
* **Complete onboarding**: Open **Settings** → **Stripe** (or **Payments**) and click **Complete setup** or **Connect Stripe**. Finish all steps Stripe asks for (identity, bank, EIN if required). See [Stripe Connect](/getting-started/stripe-connect).
* **Re-onboard**: If Stripe later asks for more info (e.g. annual verification), use the same **Complete setup** link and submit the requested details. Status should return to complete.
* **New bank**: If you need to change the bank account, add or update it in Stripe (via Rowhouse **Add bank account** or Stripe Dashboard). Do not disconnect Connect just to change the bank.
## Logo upload fails
* **Format**: Use a common image format (e.g. JPG, PNG) and a reasonable size (e.g. under 2 MB). Very large or unsupported formats can fail.
* **Browser**: Try another browser or disable extensions. Clear cache and try again.
* **Permissions**: You must be an **admin** to upload the club logo. Confirm you are in the correct org (club switcher).
## Join code or invite link not working
* **Join code**: Verify the code in **Settings** (no extra spaces). Share the exact code. If you changed it, the old code no longer works. See [Join code and invite](/settings/join-code-and-invite).
* **Invite link**: Ensure you copied the full URL. If the link is token-based, it may expire after a time; generate or copy a fresh link. For "cannot join" errors, see [Getting started troubleshooting](/getting-started/troubleshooting).
## I do not see Settings
* **Role**: Only **admins** see **Settings** and **Subscription** in the sidebar. If you are a **member**, you will not see them. Ask an admin to promote you or to make the change you need. See [Roles and permissions](/members/roles-and-permissions).
* **Org**: Confirm you are in the correct **organization** (club switcher). Settings are per org.
# Website analytics
Source: https://docs.rowhouse.co/website/analytics
View page views and traffic for your site
**Website analytics** (under **Website** → **Analytics**) show how your public pages are performing: page views, visits, and sometimes traffic sources.
## Where to find it
* Go to **Website** → **Analytics** in the sidebar. You may need a **paid plan** to see analytics. See [Plan limits](/guides/plan-limits).
## What you might see
* **Page views**: Number of times each page (or the site overall) was viewed.
* **Visits / sessions**: Number of visits (one person may have multiple page views in a visit).
* **Top pages**: Which pages get the most views.
* **Time range**: Filter by date range (e.g. last 7 days, last 30 days).
* **Traffic sources** (if available): Where visitors came from (e.g. direct, search, social, referral).
Analytics depend on your app's integration (e.g. server logs, or a third-party like Google Analytics). Accuracy and metrics vary. Use them as a guide, not absolute truth.
## Use analytics for
* Deciding which content to update or promote.
* Checking if new pages get traffic after you share links.
* Understanding which pages are most important to your audience.
If analytics are missing or zero, confirm the feature is enabled for your plan and that the pages are **published** and receiving visits.
# Custom domain
Source: https://docs.rowhouse.co/website/custom-domain
Point your own domain to your Rowhouse site
A **custom domain** lets your organization's website be served at your own URL (e.g. `www.myclub.com`) instead of `rowhouse.co/your-org-slug`.
## Is custom domain supported?
* Custom domain is an optional feature. Your org may have a **custom domain** field in [Club settings](/settings/club-settings) or under Website. If you do not see it, the feature may not be available for your plan or instance. See [Plan limits](/guides/plan-limits).
## How it works
1. In **Settings** (or **Website**), find **Custom domain** (or **Domain**).
2. Enter your domain (e.g. `www.myclub.com` or `myclub.com`). Save.
3. Rowhouse may show **DNS instructions**: add a **CNAME** (or A) record at your DNS provider pointing to the value Rowhouse gives (e.g. `rowhouse.co` or a proxy hostname).
4. After DNS propagates (minutes to 48 hours), Rowhouse may automatically provision SSL (HTTPS) for your domain. Your site will then be reachable at your custom domain.
DNS must be correct for the custom domain to work. Use the exact hostname and target Rowhouse provides. Wrong CNAME/A records can break email or other services on the same domain; if unsure, ask your DNS host or support.
## Subdomains vs root domain
* **www**: Often you point `www.myclub.com` (CNAME to Rowhouse). Then `www.myclub.com` serves your site.
* **Root** (`myclub.com`): Some setups support the root domain; that may require an **A** record or CNAME flattening. Follow Rowhouse's instructions for root domain if offered.
## After setup
* Share your custom URL (e.g. `https://www.myclub.com`) instead of the Rowhouse subdomain URL. Existing links to `rowhouse.co/your-org` may still work if redirects are configured; check with support.
# Layout pages
Source: https://docs.rowhouse.co/website/layout-pages
Use layout pages to wrap child pages (header/footer)
A **layout page** is a special page that **wraps** other pages (e.g. shared header and footer). Child pages render inside the layout instead of as standalone full pages.
## What is a layout page?
* In the [page editor](/website/page-editor), the **root** (page) properties include **Layout** (or **isLayout**). When set to **Yes** (true), the page is a layout: its content (e.g. header, nav, footer) wraps **child** pages.
* Child pages are pages whose slug or hierarchy is under this layout (exact behavior depends on how your site resolves routes). They do not need to be "attached" manually in some setups; the router uses the slug structure.
Exact behavior (how child pages are assigned to a layout, and URL structure) can vary. Check your app or theme: sometimes a layout is applied to all pages, or to pages under a certain slug prefix.
## When to use a layout
* **Shared header/footer**: One layout page with nav and footer; all other pages render inside it.
* **Section layout**: A layout for a section (e.g. `/events/*`) with its own sub-nav; child pages under that path use it.
## Creating a layout page
1. Create a [page](/website/pages) as usual (e.g. slug `_layout` or `layout`—name depends on your app).
2. In the [page editor](/website/page-editor), set **Layout** to **Yes** (or **isLayout** = true).
3. Add the shared content (header, footer, optional sidebar) and a **zone** or **slot** where child content will render (if your editor supports it).
4. Save and [publish](/website/publishing). Child pages will render inside this layout according to your site's routing.
If you are unsure how layouts and child pages are matched, create one layout and one normal page, publish both, and check the URLs to see which page uses the layout.
# Website overview
Source: https://docs.rowhouse.co/website/overview
Build and publish your organization's website with pages and analytics
The **Website** section lets you create and edit **pages** for your organization's public site, view **analytics**, and (if supported) set a **custom domain**.
## What you can do
* **Pages**: Create and edit pages with a drag-and-drop [page editor](/website/page-editor) (Puck). Each page has a **slug** (URL path), **title**, and optional **layout** (wrapper for child pages).
* **Publishing**: Pages can be **draft** or **published**. Only published pages are visible on the public site. See [Publishing](/website/publishing).
* **Analytics**: View [website analytics](/website/analytics) (e.g. page views, traffic) if your plan includes it.
* **Custom domain**: Point your own domain (e.g. [www.myclub.com](http://www.myclub.com)) to your Rowhouse site if the feature is available. See [Custom domain](/website/custom-domain).
## Where to find it
* Open **Website** in the sidebar (under the main nav or its own section). You will see **Pages** and **Analytics**. Website features may require a **paid plan**. See [Plan limits](/guides/plan-limits).
## Typical flow
1. Go to **Pages** and [create a page](/website/pages) (title, slug).
2. Open the [page editor](/website/page-editor) and add content (sections, text, images, buttons).
3. [Publish](/website/publishing) the page so it goes live.
4. Share the URL (e.g. `rowhouse.co/your-org-slug/about`) or set a [custom domain](/website/custom-domain).
See [Troubleshooting](/website/troubleshooting) for page not showing, slug conflicts, or editor issues.
# Page editor
Source: https://docs.rowhouse.co/website/page-editor
Build pages with the Puck drag-and-drop editor
The **page editor** is a visual (Puck) editor where you add and arrange **blocks** (sections, text, images, buttons) to build your page. No code required.
## Open the page editor
* From **Website** → **Pages**, open a page and click **Edit** (or **Open in editor**). The editor loads with the page's current content (or empty for a new page).
## How the editor works
* **Canvas**: The main area shows the page as it will appear. You click elements to select them and edit in the **property panel** (right side).
* **Blocks / components**: Add blocks from a sidebar or panel: e.g. **Text**, **Image**, **Button**, **Columns**, **Hero**. Drag to reorder.
* **Properties**: When a block is selected, the right panel shows options (text content, link, image URL, colors, spacing). Root (page) props often include **title**, **slug**, **description**, **layout** (is this a layout page?), and **published** (draft vs published).
* **Save**: Save regularly. Use **View live** (or **Preview**) to open the public URL in a new tab; only **published** pages are visible to the public. See [Publishing](/website/publishing).
Start with a simple layout (e.g. hero + text + CTA button) and add more sections as needed. You can always reorder or remove blocks.
## Layout vs standalone page
* **Standalone**: Normal page (default). It renders as a full page at its slug.
* **Layout**: When **Layout** (isLayout) is enabled, the page acts as a wrapper (e.g. header/footer) around **child** pages. See [Layout pages](/website/layout-pages).
## After editing
* **Save** to keep changes. If the page is already published, saving updates the live page. If it is draft, [publish](/website/publishing) when ready.
* **Close** returns you to the Pages list. Your last save is preserved.
See [Troubleshooting](/website/troubleshooting) if the editor does not load or save fails.
# Pages
Source: https://docs.rowhouse.co/website/pages
Create and manage website pages
**Pages** are the building blocks of your organization's website. Each page has a **title**, **slug** (URL path), optional **description**, and **content** built in the [page editor](/website/page-editor).
## Pages list
* Go to **Website** → **Pages** to see all pages. You see title, slug, status (draft/published), and last updated. Create a new page or open one to edit.
## Create a page
1. Click **Create page** (or **New page**).
2. Enter:
* **Title**: e.g. "About Us" (shown on the page and in the list).
* **Slug**: URL path, e.g. `about` for `rowhouse.co/your-org/about`. Use lowercase, letters, numbers, hyphens. Must be unique per org. See [Slugs and URLs](/website/slugs-and-urls).
* **Description**: optional; for your reference or SEO.
3. Save. The page is created as **draft**. Open it in the [page editor](/website/page-editor) to add content, then [publish](/website/publishing) when ready.
Reserve slugs like `home` or \`\` (empty) for your homepage if your site uses them. Check existing pages to avoid duplicate slugs.
## Edit or delete a page
* **Edit**: Open the page and click **Edit** (or open in page editor). Change content, title, or slug (if allowed). Save.
* **Delete**: Remove the page from the list (Delete or similar). The URL will 404 after deletion. Cannot be undone.
## Layout pages
* A page can be marked as a **layout** page so it wraps other pages (e.g. header/footer). See [Layout pages](/website/layout-pages).
# Publishing
Source: https://docs.rowhouse.co/website/publishing
Draft vs published pages and view live
Pages can be **draft** or **published**. Only **published** pages are visible on your organization's public website.
## Draft vs published
* **Draft**: The page exists and you can edit it, but it is not visible at its URL on the public site. Visiting the URL may show 404 or a not found message.
* **Published**: The page is live. Anyone with the URL can view it.
## Publish a page
1. Open the page in the [page editor](/website/page-editor).
2. In the root (page) properties or the header, find **Status** or **Published**.
3. Set to **Published** (or click **Publish**) and **Save**. The page goes live at its [slug](/website/slugs-and-urls) URL.
## Unpublish (set back to draft)
* In the same place, set **Status** to **Draft** (or **Unpublish**) and save. The page is no longer visible on the public site; the URL will 404 or show a not-found page. You can edit and publish again later.
## View live
* In the page editor or Pages list, use **View live** (or **Preview**) to open the public URL in a new tab. This only works for **published** pages; for drafts you may see a preview mode or a message that the page is not published.
Publishing is immediate. Double-check content and links before publishing. Unpublish if you need to fix something.
# Slugs and URLs
Source: https://docs.rowhouse.co/website/slugs-and-urls
How page slugs and public URLs work
Each page has a **slug**: the URL path segment used in the public URL. Slugs must be **unique** per organization.
## What is a slug?
* The **slug** is the part after your org's base URL. Example: for slug `about`, the full URL might be `rowhouse.co/my-club/about` (where `my-club` is your org slug).
* Use **lowercase** letters, numbers, and hyphens. Avoid spaces and special characters. Good: `about`, `meet-the-team`, `2025-events`. Bad: `About Us`, `meet the team`.
## Uniqueness
* Two pages in the **same organization** cannot share the same slug. If you try to save a duplicate slug, you will get an error. Choose a different slug (e.g. `about-us` and `about-the-club`) or delete/merge the other page.
* Slugs are usually **editable** until the page is published; some setups may allow changing the slug after publish (the old URL may redirect or 404).
## Reserved or special slugs
* Your site may reserve certain slugs (e.g. `home` for the homepage, or empty slug \`\`). Check existing pages and any docs for your theme/site to avoid conflicts.
* Do not use slugs that conflict with app routes (e.g. `dashboard`, `login`) if they are reserved.
## Changing a slug
* If you change a page's slug, the **old URL** will no longer show that page (404 or redirect, depending on setup). Update any links (navigation, emails, social) to the new URL.
* Save the page after changing the slug so the new URL is in effect.
# Website troubleshooting
Source: https://docs.rowhouse.co/website/troubleshooting
Fix page not showing, slug conflict, and editor issues
Common issues with pages and the website.
## Page not showing on the public site
* **Publish**: Only **published** pages are visible. In the [page editor](/website/page-editor), set **Status** to **Published** and save. See [Publishing](/website/publishing).
* **Correct URL**: Confirm you are opening the right URL. It is usually `rowhouse.co/your-org-slug/your-page-slug`. Check [Slugs and URLs](/website/slugs-and-urls).
* **Org**: Ensure you are in the correct **organization** (club switcher). Each org has its own pages and slug namespace.
* **Cache**: Try a hard refresh (Ctrl+F5 or Cmd+Shift+R) or another browser/device. If you just published, wait a minute and try again.
## Slug conflict or duplicate slug error
* **Uniqueness**: Two pages in the same org cannot share the same slug. Rename one page's slug (e.g. `about` → `about-us`) or delete the other page. See [Slugs and URLs](/website/slugs-and-urls).
* **Reserved**: Some slugs may be reserved (e.g. `home`, `login`). Choose a different slug.
## Page editor not loading or save fails
* **Browser**: Use a supported, up-to-date browser (Chrome, Firefox, Safari, Edge). Disable extensions that might block scripts (e.g. ad blockers) and try again.
* **Network**: Save can fail if the connection drops. Copy your content elsewhere, refresh, and try saving again.
* **Permissions**: You must be an **admin** to create or edit website pages. If you are a member, you will not see the editor or save may be denied.
* **Size**: Very large pages (many blocks or huge images) may be slow or time out. Simplify the page or reduce image sizes and try again.
## Custom domain not working
* **DNS**: Verify the **CNAME** (or A) record at your DNS provider matches exactly what Rowhouse specifies. Propagation can take up to 48 hours. Use a DNS lookup tool to confirm the record.
* **SSL**: HTTPS may take a few minutes after DNS is correct. If the domain loads over HTTP but not HTTPS, wait and try again or contact support.
* **Plan**: Custom domain may require a specific plan. See [Plan limits](/guides/plan-limits) and [Subscription](/settings/subscription).
## Analytics missing or zero
* **Plan**: Analytics may be a paid feature. Confirm your plan includes website analytics.
* **Published pages**: Only traffic to **published** pages is typically counted. Draft pages are not public.
* **Time range**: Switch the date range (e.g. last 30 days) to see if there is data in another period.