Kaish Web Manual

1. Sign in and choose the active workspace

1. Open Kaish Web in a supported current browser.
2. Sign in with the invited or purchasing email.
3. Select the intended workspace at the top of the page.
4. Confirm the role shown for that workspace before changing games, members, or shared content.

A browser session does not make one email a proven unified login across every Kaish product. Hockey remains intentionally separate, and product access follows the assigned entitlement.

2. Use Home to check readiness

• Confirm the active workspace, device mode, connection state, and any queued work.
• Review recent games or saved work before creating duplicates.
• Resolve a visible sync issue before beginning another large import.
• Use Team Roster only when your role allows membership and roster changes.

3. Create and manage games

1. Open Games and search before creating a new record.
2. Confirm opponent, sport, date, game type, and team.
3. Open the game and use the roster, live tag, review, report, or presentation path needed.
4. Keep test games clearly named and separate from customer or season data.

4. Open a local Kaish package

1. Open Review or Presentations.
2. Drag the complete supported Kaish package onto the drop area, or choose Open File.
3. Select the package document rather than an individual movie when you need tags, rows, sequence, or presentation structure.
4. If the package references external media, choose the correct source file or parent folder when prompted.
5. Verify at least one early and one late clip before editing.

Current portable .kaishcode and standalone presentation packages may include their required media. Older or reference-style documents can contain metadata and paths only, so the browser may ask you to relink video.

5. Open games and presentations from Dropbox

1. Connect Dropbox to the active workspace from Settings.
2. Return to Review or Presentations and open the Dropbox library.
3. Select a complete Kaish game or presentation package.
4. Wait for its manifest, rows, sequence, and available media to load before pressing Play.
5. Confirm the header says the intended package is streaming from Dropbox.
6. Use local Open File or drag-and-drop when the package is on the computer.

Open the complete package so review rows, source selection, and available media remain in one workspace. A raw movie alone cannot recreate missing Kaish metadata.

6. Review a complete game

1. Confirm the package name, media count, and source selection.
2. Choose Video, Split, or Library view as needed.
3. Filter the timeline or clip library instead of opening a raw segment by itself.
4. Select a row or clip, then confirm the player loads the bounded source range.
5. Use notes and drawings only after playback and timing are correct.

If the presentation or player jumps between times, stop playback, confirm the active item and source, then refresh the package once. Repeated jumping is a sync defect to report, not something to work around by changing clip timing.

7. Open and run presentations

1. Open Presentations and choose a local or Dropbox-backed presentation package.
2. Confirm the full item list appears before entering Present mode.
3. Select an item and verify the corresponding clip range and source media.
4. Use Edit Presentation to reorder or adjust supported details.
5. Present the complete sequence and verify auto/manual advance behavior before the meeting.

Open the package document, not a loose video segment. A standalone package is intended to carry required clip media; a reference presentation may still need its original sources.

8. Manage the Player Library

1. Invite or enable the intended Player accounts.
2. Link accounts to roster players when My Shifts should be available.
3. Choose the entire team, reusable groups, or individual players.
4. Set an optional expiration and read the final audience summary.
5. Publish, then review delivery and viewing progress.
6. Disable stale accounts when access should end.

9. Use reports and tactics

• Reports depend on the selected game, roster, player context, and clean tag data.
• Spot-check known events and players before downloading or sharing an output.
• Tactics boards are coaching assets; verify the selected team and presentation before reuse.
• Do not infer missing stats from an empty report—correct the underlying game data first.

10. Protect browser-local data

1. Use Protect storage when the browser offers persistent storage.
2. Create a Browser Backup before clearing site data, changing browsers, or moving computers.
3. Keep original Kaish packages and source video outside browser storage.
4. Do not treat a browser cache, Dropbox connection, or sync badge as the only backup.

Browser data can be removed by privacy tools, operating-system cleanup, profile deletion, or manual site-data clearing.

11. Resolve sync and connection states safely

1. Stop editing while a sync issue is visible.
2. Confirm internet connection, active workspace, device role, and Dropbox connection.
3. Save or export a recovery copy before restoring or replacing local state.
4. Refresh once, reopen the exact package, and verify the item count and media.
5. Contact support before deleting conflicting work.

12. Troubleshoot the failing boundary

13. Know the browser limits

• Browser storage is not a substitute for source packages and backups.
• Cloud connection does not prove a package contains all required media.
• Dropbox authorization can expire, and the browser may ask you to reconnect a package or source media.
• One signed-in identity does not automatically receive every workspace or product.
• Large packages and network playback depend on browser, bandwidth, provider authorization, and media format.

Browser readiness checklist

1. Correct account, workspace, and role shown.
2. Local package opens through both drag-and-drop and Open File.
3. Dropbox library lists complete game and presentation packages.
4. Rows, presentation sequence, and source media load together.
5. Early and late clips play without jumping.
6. Player Library audience summary matches the intended recipients.
7. Browser Backup has been created before cleanup or migration.