Provider registration
Founding professionals can apply now. Full registration will collect specialty, organization type, license or credential context when relevant, terms, MFA setup, and BAA status where applicable.
Professional portal in build
Fursan Pro is being built for physical therapists, dieticians, nutritionists, athletic trainers, strength staff, college teams, trainers, coaches, gyms, clinics, and multi-disciplinary practices.
Portal entry
This page will become the registration and access point for provider organizations, team accounts, and professional portal web access. The first real product surfaces are being sequenced around consent, MFA, audit, and scoped Client/Player 360.
Founding professionals can apply now. Full registration will collect specialty, organization type, license or credential context when relevant, terms, MFA setup, and BAA status where applicable.
Consent-scoped views for workouts, rehab/PT, nutrition, recovery, HR/HRV, body metrics, notes, messages, and team readiness.
Every professional data read is designed to be logged. Clients can revoke sharing, and provider access is gated by role, MFA, and active relationship status.
What makes Pro different
A trainer, RD, physical therapist, and college athletic trainer should not see the same interface with different labels slapped on top. The first Pro surface is being designed around specialty, consent, organization roles, and the real decisions each professional has to make.
Clients choose what to share: workouts, nutrition, rehab/PT feedback, recovery, body metrics, media, AI summaries, team readiness, or everything. Hidden categories stay hidden.
Need Attention should surface missed check-ins, nutrition drift, pain spikes, readiness risk, unread messages, and other signals that matter today.
Provider views are being built with MFA, relationship gates, org membership, BAA/terms state, and data-access logs before the portal exposes sensitive client data.
AI should summarize, cross-check, and flag patterns from permissioned data. It should not diagnose, replace licensed judgment, or create unreviewed clinical instructions.
Professional workflows
Home exercise adherence, pain/difficulty feedback, skipped reason, flare-up indicator, progression criteria, and return-to-activity context.
HEP firstFood diary, meal plans, meal photos, macro and micronutrient review, weight/body trends, GI notes, and credential-aware nutrition language.
Scope-awareHabit plans, hydration, fasting, behavior change, education resources, and safe non-medical coaching framing.
Habits + coachingRoster, athlete/player groups, position, availability, readiness, hydration and nutrition flags, return-to-play context, and staff roles.
Team modeWorkout compliance, PRs, progressive overload, rest, recovery warnings, equipment access, and quick encouragement.
Execution loopMulti-provider roles, private notes, secure messaging, access reviews, organization settings, and future BAA workflows.
Org controlsBuild order
Organizations, teams, roles, relationships, consent scopes, access logs, and backend enforcement.
Clients choose what a professional can see, then can revoke without ambiguity.
Providers see real clients/players, privacy-hidden states, Need Attention, and specialty-aware details.
Secure messages, private notes, provider briefs, practice settings, and team workflows after audit gates are proven.
Questions we expect from pros
Fursan Pro is being shaped around the reality that a trainer, RD, PT, athletic trainer, college staff member, and clinic operator all need different context, different boundaries, and different language.
No. Trainers and coaches matter, but the Pro model is broader: physical therapists, dieticians/RDs, nutritionists, athletic trainers, strength staff, college teams, gyms, clinics, and multi-disciplinary practices are first-class design targets.
The user does. The planned sharing model lets a client or athlete choose scopes such as workouts, rehab/PT feedback, nutrition, recovery, body metrics, media, AI summaries, or all shared categories. Revocation and audit trails are part of the foundation.
No. AI should help summarize patterns, cross-check plan-vs-reality, and surface useful context. It should not diagnose, prescribe, replace licensed care, or send unreviewed clinical instructions.
Team staff need roster-level visibility, position groups, readiness signals, hydration and nutrition flags, return-to-play context, staff handoffs, and enough privacy control to avoid turning a team tool into uncontrolled surveillance.
Public claims stay conservative. Fursan is building toward HIPAA-aligned controls, BAA-ready pathways, MFA for professional access, access logging, and SOC 2-aligned evidence collection, but it is not claiming certification or full compliance prematurely.
Founding professionals can apply through the private alpha flow now. The first useful Pro version should start with trust-first read-only access, then add notes, messaging, AI summaries, organization settings, and deeper team/practice tools after the access model is proven.