Rugby Event Entity Requests

Q: How can I, as rugby event organiser, review my Team Entity Requests? Where can I, as rugby event organiser, see all of the registered teams for my Rugby Event?

Teams are required to be linked to a club. When the member who registers the team and links it to a club, which they do not have club admin user permissions, an email to be sent to linked club admins for review. 

  1. Administration > Entity Requests
  2. Click into Team Request
  3. Select your Entity from the dropdown
  4. Select Status of 'Approved' or 'Declined'
  5. Add Note
  6. Click "Update"

The member who registered the team will receive an email notification to confirm whether their team request was approved or declined. 

  • If Approved, they will receive a registration link to finalise their team. 
  • If Declined, the team request stops. 

Once teams have registered to your event, you can see them in:

  • Rugby Events > Rugby Event Comps > Events > Allocated Teams
  • Entities > Teams
  • Rugby Event Team Registration Report. 

Entities > Teams > Squad Management will allow you to transfer and/or remove players between teams if required. For more information on this process, please click here.


Example email received by Club Admins:

Rugby Event Team Request

A new Rugby Event Team Request has been created and requires your review.

  • Competition:
    • _id: XX
    • Name: [Event Competition Name]
    • Team: 
      • Name: [Team Name]
      • Club:
        • _id: XX
        • Name: [Club Name]
      • Contact:
        • Name: [Contact Name]

Click here to review this team request.

Rugby Xplorer Team

Your Rugby Connection


Example email received by Team Admins:

Entity Request Update

Entity request for new team has been approved by club (Club Name).


Entity Request Id: XX

Entity Type: Team

Entity Name: [Team Name]

Note: NA

Please continue with your registration of Team '[Team Name]' here: [unique registration link]

Yours in Rugby,

Rugby Xplorer Team

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.