GoalDNA
home
Menu
GuideLast updated May 13, 2026

FAQ

Common public questions about GoalDNA.

Quick answer

The FAQ gives visible answers about product scope, current features, beta areas, pricing, privacy, and support.

Before you start

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

  • Club evaluators
  • Coaches
  • Parents
  • Admins

Step-by-step workflow

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

  • Read the answer
  • Follow the related doc
  • Use feature status for rollout truth
  • Contact support when needed

What good looks like

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

  • Visible answers
  • Feature status links
  • Support path
  • Privacy links

Role visibility checks

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

  • Directors use FAQ for evaluation.
  • Coaches and guardians use FAQ for role-specific clarity.

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.

  • FAQ does not replace the privacy policy or customer support for account-specific issues.

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