Build a club operations workspace

A club can use Dashier as an administrative layer for people, events, and attendance. Start by modeling the operations data the team needs; do not treat this pattern as a ready-made ticketing, payment, or membership-renewal system.

Create the project and sources

In an organization, create a project for the club. Add Members, Events, and Attendance sources. Members can include a name, contact email, joined-on date, and membership state. Events can include a title, start time, location, and status. Attendance can reference an event and a member, plus check-in time or an attendance note.

This structure keeps event attendance separate from a person's profile. It also makes it possible to filter attendance by event or find a member's history. Choose source and field names before integrating so the resulting API slugs and field keys are stable.

Define staff roles

Use the roles and grants that match the team. A coordinator may need to edit events; a door volunteer might only need to verify a roster; a club owner may need broader member management. Confirm the actual dashboard role behavior and endpoint policy for every sensitive source. For public pages, expose only fields intended for public viewing.

Import an existing roster

Prepare a CSV with stable, clear headers. Map columns to the Members fields, inspect date and enum validation, and compare imported row counts with the source spreadsheet. Create a small test import before moving the full roster. Keep membership records accurate and give access only to staff who need it.

Connect a club site

A server-side API route can request events or membership records using a scoped Dashier key. Do not place a write key in client-side website code or a mobile application. If the site needs anonymous event listings, configure only the event fields and methods safe for public access.

Dashier does not calculate dues, process payments, send membership email, or enforce club-specific eligibility rules as a built-in feature. Implement those workflows in your application or a separate service and document the connection. See API generation, integrations, and permissions.