An organization per department or lab
Central IT runs one deployment; each faculty, lab or admin office gets an isolated organization. Row Level Security keeps a department's pages and tickets invisible to the rest.
Feature detailsUniversities are decentralised by design: departments, campuses and labs pick tools independently, which is how student data ends up in a dozen vendors nobody vetted. Tenon lets central IT offer one workspace with an isolated organization per unit, tied to the campus identity provider.
Recommended: Self-hosted Enterprise (campus data centre), or Tenon Cloud per department

Harvard, Penn, NYU, Princeton, Dartmouth and Columbia all suffered high-profile incidents in 2025. Departments engaging vendors independently, bypassing central IT, makes consistent oversight hard.
Source: FERPA Compliance in 2026, VirtruCentral IT runs one deployment; each faculty, lab or admin office gets an isolated organization. Row Level Security keeps a department's pages and tickets invisible to the rest.
Feature detailsConnect Shibboleth, Entra or Google Workspace via SAML or OIDC. Password login can be switched off per organization.
Feature detailsSyllabus drafts, lab protocols and self-study chapters are pages inside the project that tracks them, with Word and PDF import for the archive.
Feature detailsEach committee is a channel. Polls for quick votes, decision cards for outcomes, and a Decisions tab that answers "what did we agree in March?"
Feature details
A board per course or projectEach department's work in its own organization, with columns that match its process.

Committee decisions, pinnedOutcomes recorded where the discussion happened, findable next year.

Syllabi and protocols as pagesImported from Word, edited in place, linked from the tickets that track them.
These are complete configurations, not suggestions. Create the project, add these columns and custom fields, create the pages, and the rituals column tells you which Tenon features carry the week.
Build or revise a course with content, review and approval tracked module by module.
Async weekly update from each contributor. Decision cards for changes to learning outcomes. Public share link for external reviewers.
Run a multi-year funded project with deliverables, reporting deadlines and a lasting record.
Timeline against funder milestones. Hill chart for each work package. Brain drafts the progress report from the board and pages each quarter.
Coordinate evidence gathering across departments for an institutional review.
Portfolio health by standard. Steering committee reads the weekly AI summary. Chapters shared with the visiting team by public link.
Illustrative scenario based on how teams in this sector describe their week.
Self-hosted Tenon keeps education records on infrastructure the institution controls, with SSO, role-based organizations and activity logs. Whether a given use involves education records is your policy decision; Tenon gives you the controls to enforce it.
Yes, as members of an organization (a lab, a student project, a course team). Public share links let you publish pages to students without accounts.
Yes. Contact us with your institution details.
Start free on Tenon Cloud, or self-host it. Copy one of the project setups above and you have a working board in ten minutes.