Account, Permissions, and AI Usage
Verify account security, manage mobile data permissions and connections, control automatic metric updates, and understand membership and AI usage.
Account, Permissions, and AI Usage
Account settings control identity and access; permissions control which device and provider data can enter Trainingload.ai; usage explains membership and AI consumption. Review them together when setting up a new device or investigating a missing feature.
Before you begin
- Sign in to the same Trainingload.ai account on web and mobile.
- Keep access to the account email for verification codes.
- On mobile, know whether the operating system has already denied Health or Location access.
- Decide which thresholds may update automatically before enabling any switch.
- Do not share verification codes, passwords, connection credentials, or screenshots containing private account identifiers.
1. Verify identity and password status
On web, open Account. On mobile, open Me → Account.
You can review:
- Display name.
- Account email and verification status.
- Whether a password has been set.
The current email field is read-only. If the account is unverified, request a six-digit verification code and enter it before it expires. On web, a sent code remains valid for five minutes and cannot be resent while its countdown is active.
Use Set password when the account has no password, or Change password when one already exists. An OAuth-based account can still show that no password has been set; use the displayed password action rather than assuming the account is broken.
Recover access and finish sign-in
From the login page, use Forgot password to request a reset email. Open only the newest reset link, confirm that it returns to the Trainingload.ai reset screen, and set a new password there. An expired, malformed, or already-used token must be replaced with a new reset request.
OAuth sign-in can pass through a completion or error screen before returning to the app. If completion does not redirect, return to Login and retry once; if an error page appears, record the visible error text without sharing tokens or the full callback URL.
When another application asks to access Trainingload.ai, the OAuth consent page shows the requesting application, signed-in account, requested scopes, and return destination. Approve only when all four match what you intended. Denying consent returns control without granting the requested access.
Confirm the account email, verification badge, and password status before changing connections or membership settings.
2. Review mobile permissions and data sources
Open Me → Account → Connections or the mobile Permissions page. Sources are separated into local device sources and third-party services.
Local sources include:
- Health: authorize supported health and workout reads, review granted or partial status, request a historical sync, manage connected devices, or open system Health settings.
- Location: allow route recording, or open system settings after permission has been denied.
Third-party sources can include Strava, Polar, COROS, Suunto, Wahoo, and Intervals.icu. The source row shows its current state. Open a source to connect it, review provider-specific settings, or continue to the connections page.
Review local Health and Location status separately from third-party provider connections, then open one source for its available actions.
Device permission and server connection are separate states. Health can be authorized in the operating system while the Trainingload.ai device connection still needs to be reconnected. Reopen the source detail after returning from system settings so the app can refresh both states.
3. Control automatic metric updates
Open Account → Auto update on web or mobile. Each switch authorizes updates for one metric:
| Group | Metrics |
|---|---|
| Power | FTP, CP, W′, Pmax |
| Pace | TP, CS |
| Heart rate | LTHR, Max HR |
Enable only metrics you want Trainingload.ai to update from qualifying evidence. A switch is not a promise that a new value will be available immediately; the system still needs sufficient supported activity data.
Automatic updates can change thresholds used by zones, charts, structured workouts, and load interpretation. After an update, check the metric history and review a recent activity before comparing old and new periods.
4. Review membership and AI usage
The Account membership card shows:
- Current plan and active state.
- Membership period or expiry context.
- Billing source.
- Whether cancellation is scheduled for the end of the period.
Only an active subscription from the supported subscription billing source exposes the in-app subscription management action. Other access sources can show membership status without the same management controls.
Open Usage from the membership card or mobile account area. The page shows:
- Current plan.
- Remaining weighted-token grants and the next grant expiry when available.
- Consumption and call count for the membership period.
- Token and call trends.
- Individual debit or credit events.
Choose 1 day, 7 days, 30 days, month to date, or last month. Debit events reduce the remaining balance; grant events add available tokens. Weighted tokens are the product's usage unit and should not be interpreted as a direct count of words or messages.
Compare plan, remaining grants, period consumption, selected-range trends, and the signed event ledger.
5. Set application preferences
Open Settings on web to choose:
- light, dark, or system theme;
- metric or imperial units;
- chart x-axis behavior;
- 12-hour or 24-hour time display;
- preferred interface language.
These controls use a temporary value until you press Save. Changing language also moves the current route to the selected locale and stores the preference for later visits. Units and time format affect presentation; they do not rewrite the underlying activity record.
6. Verify cross-device settings
After changing account, connection, permission, or auto-update settings:
- Save or complete the action on the current device.
- Return to the source list and confirm the displayed state.
- Refresh the other device.
- Confirm the same account email and relevant server-backed setting.
- For local permissions, verify the operating-system status on the device where the permission was granted; local permissions do not transfer to another phone.
Verify the setup
- The web and mobile sessions show the same account email.
- Email verification and password status match the intended sign-in method.
- Health and Location show the expected device-level state.
- Third-party providers show the expected server connection state.
- Only intended automatic metric switches are enabled.
- Membership status and the Usage ledger are consistent with recent grants or AI actions.
- Theme, unit, chart, time-format, and language settings persist after reopening Settings.
Troubleshooting
- The verification code does not work: enter all six digits, confirm the email, check expiry, and request a new code only after the resend control becomes available.
- The email cannot be edited: email change is not exposed in the current Account UI; the field is intentionally read-only.
- Health is authorized but not connected: reopen Health, check the server/device connection state, and use reconnect when offered.
- Location remains denied: open the operating-system app settings; a previously denied permission may not show another system prompt.
- A provider shows disconnected after OAuth: refresh the source status, confirm the same Trainingload.ai account, and inspect provider-specific settings.
- An automatic metric did not change: confirm the switch is enabled and that recent qualifying activities contain sufficient supported data.
- Usage appears empty: select a wider range and confirm the account has AI grant or consumption events.
- Membership cannot be managed in app: management is shown only for supported active subscription sources; verify the displayed billing source.
- A reset link is rejected: request a new email and use its newest link; do not reuse a consumed or expired token.
- OAuth consent looks unfamiliar: deny the request and verify the requesting app, scopes, account, and return destination before trying again.
- A preference appears unchanged: press Save, then reopen Settings; local display preferences and server-backed locale can refresh at different times.
Next steps
Connect Third-Party Platforms
Step-by-step setup for Strava, Polar, COROS, Intervals.icu, Suunto, Wahoo, and Garmin history on Trainingload.ai web and mobile.
Upload Activity Files
Upload GPX, TCX, or FIT activity files to Trainingload.ai and understand duplicate checks, import batches, processing status, and post-import analysis.