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

# 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.