Who can play
Open a fork to the public, to your organisation, or to chosen groups and members; private and public games.
Each fork has its own access policy. Change it at any time; it applies immediately to the deployed release.
| Access | Who can play | Kind of game |
|---|---|---|
| Public | Anyone with the link, even without an account. | Public game |
| Organisation (default) | Every signed-in member of your organisation. | Private game |
| Restricted | Only the groups and members you choose. | Private game |
A public game is made for events: Maketools welcome screen, optional nickname, presenter mode and reports. It does not count towards your plan's private games. See Public games and events.
In restricted mode:
- pick groups (managed in the organisation's administration) and/or individual members;
- only groups and members of your organisation can be chosen;
- owners, admins and editors always have access, so they can check the game they manage.
Once the fork is deployed, every member who has access finds it on their home page, under their organisation's games: no need to share the link internally.
Players who are not signed in are asked to sign in; signed-in people without access see an "access denied" message.
Every change of access is recorded in the audit log (the visibility and the number of groups and members, not their names).
Private games and the plan limit
A private game is a deployed fork with Organisation or Restricted access. Your plan limits the number of private games online at the same time:
| Plan | Private games online |
|---|---|
| Free | 1 |
| Plus | 3 |
| Pro, Enterprise | unlimited |
Creating forks, editing them and publishing releases stays unlimited: only going online counts. A game takes a slot when it becomes private and online, and keeps it as long as it stays so:
- deploying a private fork for the first time, or switching a deployed public fork to Organisation or Restricted, takes a slot; beyond the limit, the action is refused and a window offers to change plan;
- redeploying or rolling back takes no new slot;
- switching between Organisation and Restricted keeps the slot;
- making it public, withdrawing the deployment or archiving the fork frees its slot. A game that becomes private again later takes the last slot.
After moving to a lower plan, the private games online beyond the new limit (the last ones put online) are suspended: they can no longer be played nor redeployed, their drafts and releases are kept. They come back online as soon as a slot is freed or the plan changes. A public game is never suspended by the plan: making a suspended game public brings it back online.
Public games
A public game is free and unlimited: it takes no slot of your plan. Anyone with the link plays without an account, after a Maketools welcome screen where they choose a nickname, shown on the leaderboard. The statistics of a public game are never named for players without an account.
For an event or a workshop, open the presenter mode (the fork's "More actions" menu in the list, or the link on the Access page of a deployed public game): a screen to project with the game link, the games in progress and the leaderboard of the session.
Any player can report a public game. The Maketools moderation reviews every report and may suspend the game: see "Suspension by moderation" in Deploy.