Data security
Data separated around your organization.
Your community has its own members, responsibilities and records. Clubward organizes data access around that boundary, from the workspace you open to the permissions a staff member holds.
Updated October 29, 2026
Organization-specific database routing
Workspace identity checked with the session
Permissions applied to staff workflows
The workspace is the starting point.
Clubward’s architecture is designed around a separate tenant database. A recognized organization hostname resolves to its configured workspace database, with an active and provisioned workspace required before the application uses that connection.
This keeps the organization context close to the data request. A workspace is more than a name displayed at the top of a shared screen; it helps determine which database connection the application uses.
A session belongs to a workspace.
A signed-in session is checked against the workspace being accessed. Knowing another organization’s address should not grant a person authority to use it.
Database routing and identity checks work together. Staff permissions then govern the tasks and records available within the organization. Each layer has a different job in protecting the member relationship.
Separation is one layer of protection.
Organization-specific routing reduces dependence on a single organization filter to select the right records. It still needs careful permissions, secure account practices and operational review around it.
Shared application services and external providers also have responsibilities. Data separation does not mean every part of the service runs on physically independent infrastructure or that an incident can never affect more than one customer.
Review access and accountabilityReview the boundary in your own setup.
During onboarding, identify the organization workspace, the people allowed to administer it and any supported integrations that receive its information. Review staff access again when roles change or seasonal teams turn over.
If an account or workspace looks unfamiliar, stop and contact our team. Share the page address and a description of the issue through your established support channel, keeping sensitive member records out of website inquiries.
A person behind the answer
Let’s talk through what matters to you.
Bring a security question, a data request or a workflow your board needs to understand. We’ll help you find the relevant information and the next step.