Wiki and help

Everyone joins GameIn as a personal user. Verified status, professional roles, and managed organizations or teams are attached to that identity.

• Visitors can browse public profiles, organizations, teams, competitions, and venues.
• Registered users build profiles, follow pages, and manage preferences.
• Verified users can enter official workflows and create organizations, competitions, or venues.
• Coach, manager, caster, organizer, and judge are professional roles attached to a person, not separate accounts.

Accounts can be created with email and password or Google sign-in. An email already verified by Google is not verified again.

• After registration, the user reaches their profile and main feed.
• Keep me signed in uses a secure rotating token and never stores the password in a cookie.
• Signing out also revokes the persistent token for the current device.

Verified status means a GameIn administrator matched the user with the submitted identity details during a video call.

• The request needs a legal name, birth date, temporary ID number, and Discord contact.
• The administrator checks the identity in a Discord video call; the call is not recorded.
• After approval, temporary ID and Discord verification data are deleted.
• Verification never makes birth date or other personal data public.

Identity Credential is a device-bound authentication layer. GameIn stores a cryptographic credential confirmed by the device, not biometric data.

• A mobile credential supports biometric competition check-in; an optional computer key protects sign-in.
• Registration starts directly on mobile or through a QR code from a computer.
• Lost or replaced devices require a reasoned replacement request and administrator approval.
• Test verification confirms that the device and credential work correctly.

The profile is the player’s professional card: avatar, banner, primary nickname, country, roles, game accounts, and official activity.

• Each game account contains the game, displayed ID, and any required tag, region, or platform.
• The primary nickname is separate from game-specific IDs.
• Email, birth date, and non-public Discord data are visible only to their owner.
• Official history is generated by system events; other users cannot comment on it.

An organization is an identifiable esports entity that can manage multiple teams. A player becomes a member only through an accepted agreement.

• A verified user creates an organization with supporting documentation; an administrator reviews it before publication.
• Only the owner can create teams inside their approved organization.
• Agreements are versioned and activate only when both parties accept the same version.
• Owners manage organizations; assigned team managers manage their team and roster.

The market connects players, teams, coaches, managers, and casters through purpose-bound workflows rather than general chat.

• Verified players can advertise availability; organizations and teams can recruit for defined roles.
• Applying opens a private conversation visible only to participants.
• Rejection closes the process; moving forward starts the correct agreement template.
• Listings can be edited or closed and may specify game and expected contract dates.

A verified organizer or administrator can create a competition. Drafts remain private; published competitions appear in lists and the calendar.

• The announcement defines game, format, team size, deadline, venue, rules, and check-in window.
• Eligible teams enter organization events; verified players can form temporary teams for open events.
• Invited players receive a notification and confirm participation individually.
• Entry does not create feed noise; the public roster is available on the competition page.

Check-in confirms attendance and the bracket is built from closed entries. Seeds cannot change after the organizer starts the competition.

• Every player checks in separately using venue code, QR, or supported mobile biometric verification.
• The organizer seeds by registration order or shuffle, generates the bracket, and locks it by starting the event.
• Participants or authorized competition staff report results; a higher score determines the winner.
• Disputes can be opened before completion. Closing publishes standings, podium, and a GameIn Systems result post.

The GameIn feed is a professional event stream built from system events and organization announcements, without comments and with positive reactions.

• Colors and icons identify event types; feed filters instantly hide unwanted categories.
• Players, teams, organizations, and venues can be followed; mutual player follows create a connection.
• A red badge on the envelope signals a new decision, invitation, application, or system message.
• Object-bound conversations cannot be used as general messaging.

Professional events remain transparent while personal, financial, and contractual details are accessible only to the involved parties.

• Nicknames, roles, organization history, competition results, loan facts, and follower counts may be public.
• Email, birth date, ID data, contract content, financial terms, and private conversations are never public.
• Necessary cookies manage secure sessions and preferences; the pilot uses no advertising or tracking cookies.
• Users control optional public contact details from their own profile.

Profile HP shows which core details and community milestones build an active player profile. Invitations and achievements progress only from verifiable platform events.

• Core HP comes from required profile details. A city must be selected from verified search results; free text does not activate the city step.
• Each player has a personal invitation code, link, and QR code. A player can have one inviter, and the invitation completes only when the invited profile reaches active status.
• Badges unlock from real platform milestones such as active profiles, finished competitions, played matches, and current verified professional roles. Administrators can also grant or revoke special badges.
• Up to three earned badges can be displayed on the public profile banner. Badges do not replace identity or professional-role verification.

A competition organizer may request an optional informational city check. Comparison happens inside the player’s browser, so GameIn does not receive precise location data.

• The browser reads current location only after explicit permission, then compares it locally with the competition’s public city boundary.
• The server receives only the check result. Raw coordinates are not sent, stored, logged, or used for analytics.
• Denying permission, unavailable location, or a failed comparison does not block competition entry or check-in.
• The result is an informational signal, not proof of attendance. A competition judge or authorized administrator can use the manual fallback when needed.