Cricket Auction Pro
Available— Core module — access scoping tied to user roles.
Fine-Grained Auction Permissions
Permissions are the practical layer beneath roles — deciding exactly what a given login can click, see, or change. An auctioneer can drive live bidding but shouldn't necessarily be able to change purse rules mid-event; a team manager should see their own roster without editing another team's data. That separation is built into how access is scoped.
Why organizers use this
- Sensitive actions like rule changes are naturally restricted once an auction is live
- Team-level scoping keeps managers focused on their own squad
- Reduces accidental or unauthorized changes during a live event
- Works alongside audit logs, so restricted actions are also traceable
Typical use cases
- Preventing a team manager from viewing a rival team's purse strategy
- Ensuring only the tournament admin can change squad rules before an auction locks
- Giving a sponsor or guest a view-only permission set for a demo
Frequently asked questions
- Are permissions the same as roles?
- Roles are the label (like auctioneer or team manager); permissions are the specific actions that role is allowed to perform. Each role comes with a sensible default permission set.
- Can permissions be customized beyond the default roles?
- Today, access follows the defined roles rather than fully custom permission sets — most committees find the existing roles cover their real-world structure.
Ready to run your auction?
Start free for up to 3 teams. Scale per auction when your tournament grows.
Looking for pricing? See current auction plans or auction pricing explained.