Configure events, scouting fields, share codes, and review the audit log.
Check at least one event or add at least one team — a code can't be scoped to nothing. Combine both to cover, say, one team across several events. Set an expiry for codes you hand to outside teams.
Tagging a team number as a test team doesn't hide or delete anything it scouted — it just keeps that team out of the Team Database's rating comparisons and shows a clear "Test" badge, so a dummy number used to try out the Scout form never skews a real team's percentile.
Purely cosmetic — attaches a display name and logo to a team number so its card in the Team Database (query.html) shows who it is, instead of just a number. Works for our team or any opponent. Paste a logo link or upload an image (2MB max).
| Name | Access | Status | Actions |
|---|
Every change made through the portal, scouting pages, and member management — who did it, what role they were acting as, and when.