Team-oriented challenge workflows
Organization routes and invite flows are already present in the product.
What org mode is trying to solve
Teams adopt practice tools when the ritual is easy to run and the work matches what people actually ship. Individuals keep habits; orgs need shared visibility and lightweight coordination so momentum does not depend on one volunteer.
EraCode’s organization flows cover membership, invites, team challenges, and manager visibility so a small team can run a shared practice habit without standing up another heavy program.
What admins and leads can do today
Create or join an organization, invite teammates, and create team challenges from a quick prompt, an uploaded file, or a connected GitHub repository—then feature one so it shows up on every member’s dashboard.
Open the manager analytics dashboard to see participation, completion, top challenges, and a member leaderboard for the windows you care about.
Generate org-scoped API keys and pull the same aggregates into your existing dashboards through the read-only analytics API.
Visibility and integration
Completed org and public community challenges expose Results and Leaderboard views, with member privacy controls so people can opt out or show initials instead of a full name.
For deeper reporting, the analytics API returns org rollups and per-challenge drill-downs on a schedule your tools control; check pricing for which seats and integration features your plan includes.
Good to know
Analytics are aggregate-first: API responses authenticated with a Bearer key never include member emails.
When a challenge is timed, we use a server-anchored timer and combine your AI score with how long you took—across coding, terminal, and multi-part submissions.