GoalDNA
home
Menu
AvailableLast updated May 13, 2026

Roles & permissions

How GoalDNA separates visibility for different club responsibilities.

Quick answer

Role-aware access keeps directors, staff, coaches, players, and guardians in the right view of the same workspace.

GoalDNA product preview showing schedule health, rosters needing review, guardian links, and setup readiness.
Owner command centerAvailable

Public-safe product preview based on current GoalDNA workflows.

Product preview context

This public-safe product preview is based on current GoalDNA workflows and uses no private customer, player, guardian, inbox, injury, or member data.

Status
Available
Product areas
DashboardTeamsScheduleMembersGuardian links

Before you start

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

  • Directors
  • Admins
  • Coaches
  • Guardians asking what they can see

Step-by-step workflow

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

  • Decide who owns club settings
  • Assign staff and coach roles
  • Keep player visibility relevant
  • Review guardian links
  • Update roles when responsibilities change

What good looks like

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

  • Role controls
  • Scoped dashboard context
  • Team and member visibility
  • Guardian-linked access

Role visibility checks

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

  • Directors see organization context.
  • Coaches focus on team work.
  • Players see assigned context.
  • Guardians see linked-player information.

Common mistakes

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

  • Using one shared account for several staff members.
  • Giving admin access to people who only need team context.
  • Assuming guardian access equals staff visibility.

Troubleshooting

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

  • If someone sees too much, reduce their role before changing team or guardian data.
  • If a coach cannot reach team workflows, confirm the assignment and member status.
  • If guardian access looks wrong, review linked-player records rather than expanding guardian permissions.

What not to rely on yet

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

  • Field-level privacy minimization still needs tightening in some areas.
  • Do not promise unsupported compliance certifications.

Beta / partial notes

Use these areas carefully with pilot expectations and transparent communication.

  • Some field-level privacy minimization is still tightening.
  • Complex academy role maps should be piloted with support before broad rollout.

Example club scenario

An academy director keeps workspace-level visibility, coaches work from assigned team context, and guardians only see linked-player schedule and communication where configured.

FAQ

Can one person have more than one responsibility?

Yes. Map the responsibility carefully and keep access scoped to what the person needs to run their part of the club week.

Are guardians admins?

No. Guardian access is linked-player visibility, not workspace administration.

Related workflows