Request a branded demo

Modules

Catalog Pathways Curriculum Board Essentials Free Assist Coming soon

Catalog

Digital catalog Program pages Courses Search Publishing workflow

Pathways

Career exploration Wage data Program outcomes Student discovery Transfer articulation

Curriculum

Proposals Approvals Vote records Evidence archive Catalog year lifecycle
Capabilities MCP Coming soon API and exports Integrations College branding
Platform overview How the modules share one record, and why that matters at publish time.
Packages Compare Catalog Pathways Curriculum Academics
Academic Affairs Catalog governance Curriculum approvals Accreditation evidence
Catalog & Curriculum Teams Publishing workflow Course and program updates Version control
Enrollment & Marketing Program discovery Career outcomes Search and conversion
Information Technology WordPress ownership Data exports SIS compatibility AI and API readiness
Need help choosing? Tell us what is hardest to manage today and we will recommend a package and setup path. See it in your own colors Request a demo We stand up a full Kenii site carrying your logo and colors, loaded with demo catalog content, so your team can click through the real thing instead of watching a slide deck.

Proof

Why colleges choose Kenii Compare with incumbents Customer stories
Documentation

Documentation Kenii Catalog Reference

Roles and Capabilities

Applies to 3.18.5 and later Generated from the code

The Catalog Editor role and the permission model behind every screen and route.

Roles and Capabilities

Generated from code at version 3.18.5. Do not edit by hand; run the reference generator to refresh.

Kenii ships a dedicated staff role so catalog staff never need a WordPress administrator account.

The Catalog Editor role

  • Role: kenii_catalog_editor (label “Catalog Editor”). Registered on the site: yes.
  • Capability: kenii_manage_catalog (constant KENII_CAP_MANAGE_CATALOG). Administrators also pass every check via manage_options.
  • Catalog Editors see only the Kenii admin; the core WordPress dashboard and admin bar are hidden for them.

Permission model

  • Admin routes (/kenii/v1/admin/*): allowed when kenii_can_manage_catalog() returns true, i.e. the user has kenii_manage_catalog or manage_options.
  • Public API routes (/kenii/v1/api/*): reads are authorized with an API key sent as X-Kenii-API-Key; writes still require a manage_options session.
  • Core WordPress roles grant nothing here. Catalog rights come only from the Kenii access levels and administrators. A stock Editor, Author or Contributor cannot create, edit or delete catalog records, including through the core WordPress routes.
  • A lapsed license grants no write right to anyone. Once the renewal grace has run out, catalog pages stay readable and every write is refused for every role, administrators included, except entering a renewed license key. Export stays available. A revoked license serves nothing.