Use Cases

Roles

• anon: An unauthenticated user
• player: An authenticated user
• director: manages a game instance.
• admin: a bingo maintainer and administrator with full control of all APIs and data
• system: An automated process in the Bingo application

Database Roles

• viewer: A system user that can read public information.
• editor: A system user that can permissions to perform limited inserts and updates to the core system.
• admin: A system user that can perform all operations on the system.
• owner (director): A game user that has full control over the editable items in a game
• keeper (director): A game user that assists the owner in editing items related to a game (except for changing the owner)
• player: A game user with minimum privileges

Use Cases

anon

• Visit the site and see options/overview
• Signup / Signin
• anon receives a game link, what can they see ?

editor

• creates - Game Packs (sets of objectives)

admin

• can disable players
• can approve/CRUD a category
• can approve/CRUD objectives to a category

director

• creates a game instance
• selects a board size
• selects the category and filters objectives appropriate for the game instance
• invites players or anonymous
  • This may be a backend workflow which doesn't care. It either adds an existing player or sends an invitation
  • consider security ramifications of revealing information)
  • can find players or do they have to know e-mail addresses?
• can view all board instances for their game instances
• can promote players to directors for a game instance
• can generate the invite link

players

• have an alias / profile
• view their game card instances
• send a link to their board
• view others boards in a game instance
• see updates to the game feed (assume no secret states)
• proposes categories and objectives
• update their board with a 'completion' of an objective
• list games they are members of

system

• generate a feed of activity for a game