Best practices

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 and dues/merch 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 if needed.

Create groups for recurring audiences: e.g. “Board”, “Class of 2026”, “Committee chairs”. Use them for emails and event invitees so you do not re-select the same people every time.
Keep groups up to date: When roles or membership change, add or remove 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 and filters for one-off or complex segments.

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.

Templates first: Build templates for recurring messages (newsletter, reminders). Use drafts and 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 (group vs all members) and the count before sending. You cannot recall an email.

Invite in good time: Send event invites early so members have time to RSVP and pay. Use reminders if available.
Mark attendance: Use the attendance link 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 where appropriate (e.g. speakers, volunteers) before or right after sending invites.

Publish when ready: Keep pages draft until content and links are correct. Then publish and share the URL.
Merch variants: Define options for every size/color combination you sell so the storefront shows the right price and availability. Use clear labels (e.g. “M / Blue”) for customers.

Limit admins: Only give the admin role to people who need to manage the org. Use member for everyone else.
Join code: Do not post the join code publicly if you want to control who joins. Share the invite link only with intended audiences.
Stripe and bank: Complete Stripe Connect and bank details with the correct legal and bank information. Keep payouts and tax details up to date in Stripe.