Kaish Hockey Manual

1. Confirm access before signing in

1. Use the Kaish Hockey URL supplied during onboarding.
2. Confirm the exact account email, organization, team, season range, and role approved for the user.
3. Confirm whether access is active or trial-based.
4. Record the start and end dates for time-limited access.
5. Use a device and browser profile appropriate for confidential team data.

If the user needs data from teams or seasons outside their current team—for example, an approved league-wide or expansion-team history—ask the organization owner or Kaish Support to confirm that scope first.

2. Sign in and verify the visible scope

1. Open the Kaish Hockey sign-in page and use the assigned identity.
2. Complete verification or password recovery through the Hockey account path.
3. Confirm the account lands in the intended organization and team.
4. Check the role shown or the actions available.
5. Verify the expected current season and any approved historical seasons.
6. Do not enter or edit data until unexpected teams, seasons, or permissions are resolved.

A successful sign-in is not enough. Confirm that the user can see exactly the approved scope—and no unapproved scope.

3. Verify a trial precisely

1. Confirm the Hockey account and the trial dates shown to the signed-in user.
2. Review the product, role, team, and season scope.
3. Confirm whether the current date is inside the trial window.
4. Have the user sign in to their own account and open the intended workflow.
5. Review what the account will see when the trial expires.
6. Contact Kaish Support if the dates or visible access do not match.

4. Set up a team administrator

1. Locate the exact Hockey identity or create the approved account once.
2. Assign the intended organization and team.
3. Choose the team-admin role defined by the Hockey system.
4. Set trial or access dates if applicable.
5. Grant only the approved seasons and datasets.
6. Have the user sign in and verify one allowed administration task.
7. Verify that an organization-wide or owner-only action remains unavailable unless explicitly approved.

5. Request past-season visibility without mixing ownership

1. Write down the exact seasons and data types required.
2. Separate shared league history from team-only material.
3. Confirm the governing organization approves the new team seeing that history.
4. Ask the organization owner or Kaish Support for the narrowest available scope.
5. Test a known record from each approved season.
6. Confirm an unapproved record remains hidden.

Never solve missing history by reassigning old records to the new team. Visibility and ownership are different; preserve the source organization, team, season, and record history.

6. Work inside the selected team and season

• Verify the organization/team/season context before each session.
• Search existing players, games, or reports before creating new records.
• Keep notes and evaluations in the intended team context.
• Use share/export controls only for the intended recipients.
• Return to the correct current season after reviewing historical data.

Labels and available modules can vary by role and account scope. Follow current in-product navigation, and contact support when a documented control is not visible.

7. Protect Hockey data

• Do not copy production account lists into public support pages or screenshots.
• Blur emails, player identifiers, team-only notes, and confidential reports in training media.
• Do not reuse a shared login for several staff members.
• Do not export league or team data to personal storage without approval.
• Report unintended cross-team visibility immediately and stop editing.
• Never send passwords, tokens, database credentials, or billing details to support.

8. End Hockey workspace access safely

1. Confirm the exact member and requested end date.
2. Preserve required team records and transfer any ownership responsibility.
3. Remove or expire team and organization membership using the available owner/admin controls.
4. Revoke active share links where supported and required.
5. Confirm the former member no longer appears in the protected workspace.
6. Contact Kaish Support if any expected access control is unavailable.

9. Verify the account end to end

1. Sign in with the intended user identity.
2. Confirm the correct organization, team, role, and trial/access dates.
3. Open a known current-season record.
4. If approved, open a known historical-season record.
5. Confirm at least one unapproved scope remains inaccessible.
6. Complete one safe role-specific task and verify it persists.
7. Sign out and confirm the session ends.

10. Stop before a scope mistake becomes a data mistake

11. Know what this guide does not assume

• This customer guide does not identify customers, datasets, database projects, non-public URLs, or credentials.
• It does not claim Kaish App and Kaish Hockey share one login.
• It does not authorize league-wide visibility or changes outside the signed-in member’s available controls.
• Available modules can vary by role, team, and season scope.
• Final permissions must be verified with the current signed-in Hockey account.

Use the admin checklist