GoalDNA
home
Menu
AvailableLast updated May 13, 2026

Invite your team

Bring people into GoalDNA with scoped roles instead of shared access.

Quick answer

Invite staff first, then coaches, players, and guardians when each group has the right context.

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
  • Team managers

Step-by-step workflow

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

  • Invite owners/admins
  • Invite staff and coordinators
  • Invite coaches to team workflows
  • Add players
  • Link guardians where configured

What good looks like

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

  • Member list
  • Invite controls
  • Role controls
  • Profile context

Role visibility checks

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

  • Admin roles should stay limited.
  • Coaches should receive team-specific context.
  • Guardians should receive linked-player visibility only.

Common mistakes

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

  • Inviting too broadly before roles are checked.
  • Assuming rolling-out workflows are fully available.
  • Using one shared account instead of scoped roles.

Troubleshooting

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

  • Check workspace role, team assignment, and feature status before assuming a workflow is broken.

What not to rely on yet

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

  • Do not use one shared account for a team.
  • Deep account self-serve is partial.

Beta / partial notes

Use these areas carefully with pilot expectations and transparent communication.

  • Review feature status before relying on advanced automation, intelligence, or provider sync.

Example club scenario

Use this guide to move one real club workflow into GoalDNA, confirm role visibility, then expand when the team is ready.

Related workflows