One registration link.
Every player ready to review.

The Registration settings show Full Name and Mobile Number as locked required fields, with Email Address and Primary Role locked but optional. The public player flow also validates a player photo and age. Organizers can then enable playing role, batting style, bowling style and experience, or add custom text, number, dropdown and checkbox questions.

Not as general file fields today. The public flow supports a player photo and, when a fee is enabled, one payment screenshot. A custom question can collect text, a number, one dropdown choice or checkbox answers, but it cannot upload an age certificate, NOC or ID document.

Yes. Set Maximum registrations in Settings, Registration. The public page counts registrations without downloading player records and closes sign-ups at the limit. The server-side registration function checks the limit again on submit, which covers two people trying for the last place at the same time.

No. For an INR tournament, the organizer sets an amount and UPI ID. The player pays the organizer directly and must upload a payment screenshot. The organizer opens that proof and verifies the player by hand. CricketOrganizer does not receive the entry fee or confirm the bank transaction.

A public submission lands with Pending status. On the Players screen, the organizer opens the player record, checks contact details, custom answers and any payment screenshot, then chooses Verify player or Reject registration. There is no separate automatic Paid status in the current player record.

Typed registration fields are saved as a local draft in that browser and restored for up to 7 days. Uploaded files are not stored in the draft, so a player still needs to choose the photo or payment screenshot again. A failed submission leaves the entered values in place.