Summary

To prevent unauthorised registration of players who are not playing at the club, or to check the identity of each member who registers, a club can opt to validate each player's registration before the player can receive event information and personal results on the Bridgemate app.

 


Why validate?

The Bridgemate app enables players to register quickly and easily with the club by selecting the club and providing their membership number. But there is nothing to stop a player from entering someone else's membership number. While such a player wouldn't be able to receive their own personal information in the app, they could access information belonging to somebody else playing in the same event who isn't using the Bridgemate app. This could reveal unauthorised information about boards the player might still have to play, which is obviously undesirable. In smaller clubs and events, there is less chance that this would happen, but in bigger events, it could become a problem, and so to prevent this, clubs can enable the validation of player registrations.

 


Procedure

Enabling/disabling validation

To enable or disable validation, log in to your club account and click on App configuration.

App validation setting

Select Validate new player registrations and click Save to enable validation. Conversely, clear this option and click Save to disable validation.
 

Validate new player registrations

With validation enabled, each new player registration with your club in the Bridgemate app needs to be validated. To validate the entries, click on Player registrations in your club account.

Validate players

Players who are not yet validated are marked as "No". Click on validation OK to validate the registration. Make sure you have verified that the combination of name, email address and player number are correct.
After validation, the player can now receive event information and personal results via the Bridgemate app.

 


Additional information

There is no additional information available for this article.

 


See also

No further references available for this article.

 


Update history

23-01-2015 - Article published