Quick Start Guide
Step-by-step guide to get your organization up and running with SecureCodingHub in under 10 minutes.
Step 1 — Log in to Your Admin Dashboard
SecureCodingHub uses a passwordless login flow. Enter your email address and we will send you a one-time magic code. No passwords to remember or rotate.
Step 2 — Invite Your Team
Navigate to the Users page from the sidebar. Click Add User to invite team members one by one. Each user needs a first name, last name, email, and role.
| Role | Can do |
|---|---|
| Org Admin | Manage users, teams, assignments, view dashboard analytics |
| Learner | Complete challenges and scenarios, track personal progress |
Step 3 — Create Teams Optional
Teams let you group users by department, project, or skill level. This makes it easier to create targeted assignments and track progress by group.
Navigate to Teams in the sidebar. Click Create Team, give it a name, and add members. A user can belong to multiple teams.
Example Teams
Step 4 — Create Your First Assignment
Assignments let you direct specific training content to your team. Navigate to Assignments in the sidebar and click Create Assignment.
Assignment Target Options
| Target Level | Description | Example |
|---|---|---|
| Category | Assign an entire OWASP category | All of OWASP Web Top 10 |
| Topic | Assign a single topic within a category | SQL Injection only |
| Scenario | Assign a specific learn scenario | Reflected XSS Attack walkthrough |
Assignee Options
| Assignee | Description |
|---|---|
| User | Assign to a single person |
| Team | Assign to everyone in a team |
| Organization | Assign to all users in your organization |
Step 5 — Developers Start Training
Once assignments are created, learners will see them after logging in. Each learner has a personal dashboard showing their assigned training, progress, and XP.
Practice Challenges
Developers review real-world code snippets, identify the vulnerable block, and select the correct fix. Challenges are available in their preferred language and framework.
Learn Scenarios
Interactive, step-by-step attack walkthroughs in a simulated browser environment. Developers experience how vulnerabilities are exploited in practice.
As developers complete challenges, their progress and scores appear on your admin dashboard in real time. You can track completion rates, average scores, and identify topics where your team needs more training.
Common First-Day Mistakes
The most frequent setup mistake is skipping the stack preferences wizard for invited users. When learners click straight into a challenge before setting their backend, frontend, and mobile preferences, the platform defaults to a language that may not match their day job. A Python backend engineer sent into a Java challenge wastes the first ten minutes parsing syntax instead of looking for the vulnerability. Encourage your team to complete the wizard once at the start. The same applies for assignments: pick a single OWASP category for the first wave rather than the entire catalog, otherwise progress feels diluted and dashboards look empty for the first few weeks.
Another common mistake is racing through Phase 1 of a Practice challenge. Learners under deadline pressure tend to click the first red-looking line they see. Two-phase scoring exists precisely to slow this down. If you spot a team member finishing every challenge in under sixty seconds with consistently mid-range scores, that is a signal they are clicking, not reading. See Practice Mode for how the phase flow is designed.
How Long the First Week Typically Takes
For an Org Admin, the setup work in this guide is usually under thirty minutes once you have the user list ready. SSO and SCIM add another hour or two depending on your identity provider. Reviewing the first batch of analytics is something you do at the end of week one, not on day one. See Navigating the Dashboard for what to look for once data starts coming in.
For learners, the realistic time budget is two to four hours per week. A single Practice challenge takes five to ten minutes; a Learn scenario takes twenty to forty. Teams that mandate eight hours per week burn people out within a month and see completion rates drop. A steady cadence of three Practice challenges and one Learn scenario per week, sustained across a quarter, beats a one-week intensive push every time. Set assignment deadlines that respect that reality.