Docs/Admin Guide/Organization Settings

Organization Settings

Org-wide preferences that change how the rest of the platform behaves. Today the page exposes two switches: the learner-facing leaderboard visibility, and the compliance coverage threshold.

Where this lives

Sidebar → Organization Settings under the Settings section, at /organization/settings. Visible to org admins only.

Leaderboard visibility

Controls whether the leaderboard panel is shown to learners across the organization. When the switch is on, every learner sees the standard leaderboard on their home page and can compare themselves against the rest of the team. When it is off, the leaderboard is hidden from the learner UI; admins still see it on the dashboard but with a small Hidden badge as a reminder that it is currently invisible to learners.

Most organizations leave the leaderboard on. The switch exists for the cases where it does not fit cultural norms (highly distributed teams, contractor-heavy rosters, or organizations whose HR policy discourages public peer comparison).

Compliance coverage threshold

Controls the percentage of eligible users that must be trained on a given OWASP module or regulatory control for that item to flip from partial to covered on the Compliance dashboards.

The slider is bounded between 50 % and 100 % and defaults to 80 %. Raising the threshold makes the compliance dashboards stricter: items that previously read covered may drop back to partial. Lowering it has the opposite effect. The setting is org-wide; it is not per-framework. Changes take effect on the next compliance read — no recalculation step is required.

Pick a value that matches your internal compliance policy rather than something cosmetic. Auditors will eventually ask what the threshold was at the time of an evidence pack, and being consistent ("we have always evaluated at 80 %") is the cleanest answer.

What about everything else?

Other org-scoped settings are surfaced on the page that owns the feature rather than centralised here:

  • SSO and SCIM are configured under Organization → SSO. The SCIM token is generated on the same page once SSO has been saved.
  • SCORM enabled toggle lives on the SCORM page itself.
  • API keys and webhooks are managed under API Keys and Webhooks.
  • Plan and seat cap (the maxSeats figure) are managed by the SecureCodingHub team. Contact your account manager to change them.