Skip to content
CÉNIT — Documentación

Settings

TL;DR

Section titled “TL;DR”

/dashboard/settings consolidates all club configuration: visual identity, subdomain (slug), personal profile, formula parameters (MD window, ACWR method), visible player-profile tabs, session types, risk thresholds, team management, and staff access. It is a single page with internal sub-tabs (no separate pages).

For sales

Section titled “For sales”
  • Problem it solves: every club has its own identity, methodology, and thresholds. Without Settings, CÉNIT would be a rigid box; with Settings, the club configures its own without asking us for a release.
  • Typical use cases: upload the club’s logo and colors, adjust the ACWR ok/warn range to the club’s sport scientist, decide which player-profile tabs are visible (hide “mental” if there’s no psychologist yet), expand the model-match window (md_max_window_days) when there are few historical dates.
  • Plans that include it: all plans.
  • Differentiator: most competitors fix formulas and thresholds. CÉNIT exposes them per org.

How staff use it

Section titled “How staff use it”

Access and permissions

Section titled “Access and permissions”
  • Configuration tab (main): read for everyone; the forms that mutate the org accept writes only from Head of Performance and Sporting Director. The personal profile form is the exception: any role edits their own.
  • Teams tab: Head of Performance and Sporting Director only. Creates sub-teams and assigns players and staff.
  • Access tab: Head of Performance and Sporting Director only. Invites and revokes the org’s staff users (see also Users).

Configuration tab subsections

Section titled “Configuration tab subsections”
  1. Club identity — name, logo (PNG/JPG/WebP up to 5MB), primary and secondary color in hex. The colors override the app’s default branding for the org.
  2. Club slug — kebab-case subdomain, 2–40 characters. Unique per organization (white-label phase 1 passive — the system detects the subdomain but doesn’t enforce it yet).
  3. Profile — name, language (es/en/pt), avatar. Always edits the personal profile, regardless of role.
  4. Squad — team data — team name, season, season start date, division.
  5. Session types — manages custom types (label, color, order, active). Used by the Calendar event modal.
  6. MD window — range 90–360 days, default 90. Defines how many days back the system looks to compute the model match (average of the 3 best with the T1/T2/T3 tier system based on minutes played).
  7. Microcycle view — only trainings or trainings + match. Default includes the match.
  8. ACWR method — RMA (default, conventional ratio) or EWMA (Williams 2017, opt-in).
  9. Visible player tabs — controls which player-profile tabs render: general, tactical, physical, medical, mental, messages.
  10. Risk thresholds — every threshold consumed by the Risk Advisor: ACWR ok/warn, Hooper ok/warn, Vmax% ok/warn, pain, recent injuries, physio pain, and anxiety.

FAQ / edge cases

Section titled “FAQ / edge cases”
  • Slug already taken: the form warns that the subdomain is in use. Pick another one.
  • ACWR method change: applies from the next daily snapshot computation. Historical snapshots are not recomputed.
  • Hide player tabs: the filter applies when rendering the profile. A staff member with a direct link to a hidden tab still sees the URL but not the content.

How the player sees it

Section titled “How the player sees it”

Player surface: N/A. The player doesn’t enter Settings, but what the HoP configures impacts directly what they see: the club’s colors and logo on their PWA, the profile tabs, and the risk thresholds that generate alerts in their feed.

Integrations

Section titled “Integrations”
  • GPS Load: consumes the MD window, the microcycle view, the ACWR method, and session types.
  • Risk Advisor: consumes every risk threshold.
  • Squad: consumes the visible-tabs configuration to filter profile tabs.
  • Dashboard shell: consumes the logo and colors for org skin.