Security overview
Useful access. Clear responsibility.
The right people need the right tools to serve your members. Clubward connects workspace access, staff permissions and recorded activity so your team can work with clear responsibilities.
Updated October 29, 2026
Access shaped by role and responsibility
Activity history for relevant staff actions
Human help when something needs investigation
Give access according to the work.
Staff access can be shaped by roles, positions and individual permission assignments. The platform also checks account status and the relevant module when authorizing supported workflows.
Start with what each person needs to do. A front desk shift, a finance review and a staffing decision may require different access. Review those assignments when someone changes position or leaves the team.
Explore staff roles and permissionsProtect the sign-in as well as the record.
Use the secure HTTPS address provided for your organization and protect the credentials for each individual account. Account passwords are stored using hashing rather than as readable text.
Production session cookies use security protections that restrict script access and how cookies are sent. These controls work alongside the organization’s responsibility to protect devices, keep access assignments current and report a lost or compromised account.
Keep organization context connected.
Clubward uses organization-specific database routing and checks session workspace identity. Those boundaries help keep a staff interaction tied to the organization the person is authorized to work in.
Administrative access deserves particular care. Use individual accounts, protect account credentials and avoid sharing a manager’s login to cover a routine staff task.
How data separation worksInvestigate using the available history.
Activity records can include the actor, action, module and affected record, with support or impersonation attribution where applicable. That context helps authorized reviewers investigate a change or explain a staff handoff.
Recorded activity is a practical source of context. Coverage depends on the workflow and the events captured; it should be reviewed alongside the underlying records and the people involved.
Explore activity and audit logsGive support access a defined scope.
Support access handoffs are time limited and connected to a workspace, ticket and identified people. The platform rechecks the support actor’s permissions and records relevant handoff events.
Support sessions have idle and absolute expiry. These controls support a focused investigation while keeping the support context attributable to the people involved.
Bring a concern to a person.
If you suspect unauthorized access or an unexpected change, contact our team promptly through your established support channel. Include the affected workspace, approximate time and a concise description of what you observed.
Do not send passwords, payment details or a full member export in a website form. We can agree an appropriate way to exchange the information needed for the investigation.
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.
