Team, Admin, and Account Manual

1. Separate workspace, membership, role, and product access

A person can belong to more than one workspace, and each workspace can assign a different role. Always select the intended workspace before editing members or shared content.

2. Create or verify the team workspace

1. Sign in to your own owner or admin account.
2. Create the team once, or open the existing workspace.
3. Confirm the workspace name, sport, season, and current owner.
4. Open the member-management area and review the active members and available seats.
5. Add only the people who need access now.
6. Before adding team data, confirm you are still in the intended workspace.

3. Invite a member safely

1. Enter the exact email the person will use to sign in.
2. Select the least-privileged role that supports the person’s job.
3. Assign the relevant team, sport, group, or player relationship when requested.
4. Send the invitation and confirm it remains pending until accepted.
5. Ask the recipient to accept using the invited email.
6. After acceptance, confirm the membership is active and the role is correct.
7. If a duplicate invitation exists, remove only the verified stale invitation.

An accepted invitation confirms workspace membership. Product access may also require an available seat or plan assignment.

4. Assign access by job

• Owner: controls the workspace and should remain a small, protected set.
• Admin: manages members and team operations when delegated by an owner.
• Coach/staff/member: works with assigned team data without owner-level account control.
• Scout/evaluator: uses the assigned scouting scope, sport, team, or organization.
• Player/viewer: sees only content explicitly published or assigned through supported sharing.

Role names and exact permissions can vary by product. Start with the narrowest role that supports the member’s work, then expand it only when needed.

5. Verify access without impersonating a member

1. Confirm the invitation was accepted and the member appears in the correct workspace.
2. Confirm the assigned role and any required product seat.
3. List every required product instead of treating “Kaish access” as one entitlement.
4. Ask the member to sign in to their own account and select the intended workspace.
5. Have the member open one expected workflow in each required product and confirm one restricted workflow remains unavailable.
6. If access looks stale, ask the member to sign out, reopen that product, and sign back in.
7. If the result is still wrong, stop changing roles and contact Kaish Support.

Do not request the member’s password, verification code, recovery link, or screen-control access. A screenshot is useful only after private team and account details are hidden.

6. Let each member maintain their own account

• Use the sign-in screen’s recovery flow for a forgotten password.
• Complete email verification from the member’s own inbox.
• Review profile and security settings while signed in to the member’s own account.
• Choose the correct workspace after sign-in when more than one is available.
• Sign out on shared devices and avoid saving credentials in a shared browser profile.
• Contact Kaish Support when the expected account controls or workspace do not appear.

7. Link player accounts and choose the audience

1. Confirm the player’s own login identity.
2. Link that identity to the correct roster player.
3. Verify team, season, and group membership.
4. Choose the whole team, selected groups, or specific people when publishing.
5. Set an expiration when appropriate.
6. Confirm the final audience before Publish.
7. Remove access when the sharing purpose ends.

Use the dedicated Player Library guide for the complete workflow. A team role does not replace a player link, and unpublished coach work remains private.

8. Remove workspace access without losing team work

1. Confirm the member and every workspace role that should end.
2. Transfer workspace ownership and team responsibilities before removing an owner.
3. Preserve team-owned games, presentations, reports, and other required records.
4. Remove stale pending invitations and the former member’s active membership.
5. Revoke public links or Player Library publications that should no longer be available.
6. Confirm the former member no longer appears in the protected workspace.
7. Tell the member to sign out on devices that previously used the workspace.

9. Check the visible account state first

10. Send a focused support request

1. State the Kaish product and device or browser.
2. Describe the expected workspace, role, and workflow.
3. Describe what the member sees and the last successful step.
4. Include the app build or browser version when available.
5. Attach a redacted screenshot if it clarifies the problem.

Use the product-specific workflow