How are marketplace apps reviewed?

Extensions go through a governed review path with permission scopes and operational safeguards before you activate them on a campus.

Can we enable an app on one campus only?

Yes—marketplace activation is per campus. Groups keep shared governance without forcing the same app mix everywhere.

Yes—use the developer platform and packaging flows documented for partners and internal builders.

Marketplace

Extend your platform with approved apps, ready-made setups, and integrations—activate per campus so local policy stays local.

Simulated data — illustrative only

Enable extensions campus by campus—permissions, fees, and workflows follow each school’s configuration, not a one-size HQ mandate.

LMS, payments, messaging, and data exchange with versioning and kill switches scoped to the campuses that need them.

Review pipeline, permission scopes, and sandbox so only safe extensions reach the tenants you choose.

Groups standardize governance and reporting; each campus chooses which marketplace apps to turn on—no imperial “enable everywhere” default.