What it does
Curriculum sharing lets one program (the provider) make its curriculum visible to another program (the consumer) inside the same institution. When a share is active, the consumer program's Courses page lists the provider's courses and sessions alongside its own, labeled with the source program they come from.
Who it's for
Programs that run a common core — for example, a parent program whose curriculum several tracks consume. Program administrators and directors in the consumer program see the shared content; sharing links are administered at the institution level, not from the Curriculum workspace.
How it works
The merged list. With an active share in place, the consumer program's Courses page includes courses from every provider program sharing with it, merged with its own. Each shared course carries a badge naming its source program, so what's owned versus consumed is always clear. Sessions from shared courses are visible the same way, and filters, search, and pagination work across the merged list.
Access checks. Opening a specific shared course or session re-verifies that an active share from the source program still exists before showing it. Content from a program not sharing with you is treated as not found.
Before you start
Sharing links themselves are set up by institution administrators, not from the Curriculum workspace — this article covers what a consumer program sees, not how to turn sharing on.
You need at least view access to the consumer program's Courses page to see shared content.
Do this
Open the Courses page (
/curriculum/courses) → you should see your program's own courses merged with any shared in from provider programs.On the Courses list view, look for a badge naming a source program → confirm it reads Owned by [program name] rather than your own program.
On that list view, try to select Edit on the shared course's row → confirm the action is disabled and a tooltip explains the course is managed by the source program.
To make a change, switch to the source program using the program dropdown → confirm you can now edit the course from that program.
You're done when
✓ Shared courses appear in your course list with a badge naming their source program.
✓ Edit, archive, and remove actions are disabled on shared rows, with a tooltip naming the owning program.
✓ Switching to the source program lets you edit the same course directly.
Boundaries and limits
Sharing is visibility, not editing: the consumer program views the provider's curriculum but doesn't own it. Changes are made in the provider program.
Shares are directional (provider to consumer) and per program pair; visibility doesn't chain through intermediate programs.
Sharing works between programs within your institution; there's no cross-institution or cross-tenant curriculum share in this workflow.
A share must be active for curriculum content to appear; revoked or inactive shares immediately stop resolving.
Sharing links aren't created or edited inside the Curriculum workspace — they're administered as institution-level configuration.
Common questions
Q: How do I tell which courses are ours and which are shared in? A: Shared courses carry a badge naming their source program, so owned and consumed content is always distinguishable.
Q: Can we edit a course that another program shared with us? A: No. Shared curriculum is view-only from the consumer side; the edit action is disabled on those rows. Edits happen in the program that owns the course.
Q: What happens when a share is turned off? A: The provider's courses and sessions stop appearing in your curriculum views immediately, and direct links to them no longer resolve.
Related articles