Create and operate independent sessions
Sessions are light but complete events, independent of tournaments, rounds and circuits. They have an owner, administrators, date, place, common rules for their matches, participants and their own life cycle.
Player
Check the session, occupy or free an available seat and play the matches in which you were seated. If the session is exclusive, it must belong to the owning organization.
Organization
You can own the event, limit it to its members and keep a grouped reading of matches, participants and results.
Event Manager
Create and configure the session, add matches, assign seats, publish, start, end or reopen the event and correct matches when appropriate.
General session reading
Sessions function as light but comprehensive competitive events. They allow you to group matches, follow players and keep your own reading without depending on a traditional tournament.
What they contribute
They provide traceability to specific activity, help organize more agile events and fuel competitive reading and subsequent monitoring.
Reading by states
Created, published, started or ended: the session is understood by the status of the event. Validation pertains to each match, not to the session state.
When should a session be used
- When you want real competitive activity without deploying the entire structure of a tournament.
- When the most important thing is to seat players, activate tables and leave traceability of the game.
- When the event is light, fast or more informal, but you still want memory and reading later.
When to use a tournament instead of a session
- When you need rounds, pace of progress, phases, formats or a more complete sports history.
- When the institutional reading, the operating bar and the progression by blocks matter a lot.
- When the event should feel like a championship and not just a table activity.
Create and configure the session
- Activate the profile that will organize the activity and open the action to create a new session.
- Defines name, place and planned start. The session retains the owner profile even if other administrators are assigned.
- Selects administrators of type Tournament Administrator. These profiles will be able to operate the event within the permissions granted.
- Configures whether access is limited to members of the owning organization.
- Defines type of match, objective points, time per pair, total time and if the stopwatch should mark time out.
- Indicates how many initial matches will be created and reviews the summary before confirming.
Publish, start, end and reopen
Created → Published
The session is born as a draft. When published, the date of post is recorded and members linked to the owner organization are notified.
Published → Started
The administrator confirms that the event has started. From that moment on, the actual start date is recorded and the tables can operate as an ongoing activity.
Started → Finished
End consolidates the statistics of the validated matches of the session and records the end date. Incomplete items must be reviewed before closing.
Finished → Started
Reopen returns the session to logged in and clears its end date to allow controlled correction. Afterwards it must be finished again to consolidate the corrected result.
The listing allows the publish, start and end transitions to be applied in bulk to selected sessions. Each record retains its permission and status validations; a mass action does not bypass the event rules.
Seating and seating players
In independent sessions, table occupation is an operational reality. Sitting is not just appearing on the screen: it is occupying a specific place within the game.
Sit as player
The identity must be valid, the seat must be free and the person cannot be duplicated within the same table.
Seat another person
The administrator can complete the table when he needs to coordinate the actual start of the match.
Release seat
The table can go back if it hasn't actually started yet, which helps better reflect the actual occupancy of the game.
Warnings and verifications
Before seating someone, the platform can warn if that person is already playing at another active table. It does not always block, but it does help to decide with more awareness.
Overlap Warning
It is used to detect related active tables and avoid unwanted crossovers between simultaneous matches.
Basic checks
The identity must be valid, the seat must be free and, where applicable, session membership must be in order.
Review before closing
- Check in the matches tab which ones are created, started, finished or validated.
- Corrects markers through online editing only when the match state allows it.
- Reopen individually or massively the matches that need correction before ending the session.
- Check the players tab to confirm participation and activity statistics.
- End the session when the validated matches represent the final result that should feed the global statistics.