GoalDNA
home
Menu
GuideLast updated May 13, 2026

Who GoalDNA is for

How directors, staff, coaches, players, guardians, and academies fit into the same role-aware workspace.

Quick answer

GoalDNA is built for clubs, academies, directors, admins, coaches, staff, players, and guardians who need different views of the same club week.

Before you start

Name the real owner, the first team, and the role boundaries before inviting more people.

  • Club owners and directors
  • Academy directors
  • Coordinators and admins
  • Coaches
  • Players
  • Guardians

Step-by-step workflow

Work through the setup in the order a club would actually run it during the week.

  • Map real responsibilities before inviting people
  • Keep owner/admin access narrow
  • Assign coaches to the right teams
  • Link players and guardians carefully
  • Review each role against schedule, matchday, and communication needs

What good looks like

These are the available or practical outcomes to verify before moving on.

  • Director and admin operating views
  • Member and invite workflows
  • Coach team and matchday context
  • Player participation visibility
  • Guardian linked-player visibility

Role visibility checks

Check access boundaries before inviting more staff, players, or guardians.

  • Directors/owners see workspace-level context.
  • Admins/staff coordinate structure and operations.
  • Coaches manage team workflows.
  • Players see relevant participation context.
  • Guardians see linked-player context only.

Common mistakes

Avoid these rollout errors; they create confusion faster than the product can clean it up.

  • Giving every helper admin access.
  • Inviting guardians before player links are clean.
  • Using one noisy group view for directors, coaches, players, and families.

Troubleshooting

Check the concrete schedule, team, roster, and role context before changing permissions.

  • If a role sees too much, reduce the role before changing roster data.
  • If a coach cannot find their team, check assignment and member status.
  • If a guardian needs staff controls, invite them as staff instead of widening guardian access.

What not to rely on yet

These limits should stay out of club-critical plans unless feature status changes.

  • Clubs that need payments, registration, full league administration, or live provider sync should treat those as outside the current core.
  • Complex academy rollout should be planned carefully.

Beta / partial notes

Use these areas carefully with pilot expectations and transparent communication.

  • Academies with complex multi-team rollout should start with a supported pilot.
  • Users needing payments, full registration, official league administration, or live provider sync should treat those as future or adjacent needs.

Example club scenario

A club owner reviews operating health, an admin manages members and schedule context, coaches run training and matchday, players see relevant updates, and guardians receive linked-player visibility without staff controls.

FAQ

Who should wait before using GoalDNA?

Clubs whose immediate requirement is payments, full registration, official league administration, or full live provider sync should confirm feature status before rollout.

Related workflows