---
title: Edit a content block
description: >-
  Update Content Block DB entries or Learning Journey DB masters in Campus
  Management, sync changes to linked courses, and break or reset sync links when
  needed.
sidebar:
  order: 3
---

Edit blocks in the central **Content Block DB** when you need to fix or improve shared material. Changes can propagate to linked course copies through sync. For full structured journeys, edit the **Learning Journey DB** in Campus Management and sync linked courses from **Settings** — the same push model, at journey scale.

:::info
Requires the central content library to be enabled for your institution. Blocks with active sync links show sync status in the library table and in the course editor.
:::

## Why it matters

Central content only saves time if updates actually reach enrolled courses. Editing in the database is how institutions correct a broken link, refresh a reading, or revise quiz questions once instead of in every section. Understanding **save vs sync**, **conflict** states, and when to **break a link** keeps shared material trustworthy without trapping teachers who need a local variation.

## Where to edit

| Content lives in | You edit here | Linked courses receive updates via |
|------------------|---------------|-------------------------------------|
| **Content Block DB** | Campus Management → Course Management → **Content Block DB** → block edit page | **Save & Sync**, **Syncs** column, or **Sync all** |
| **Learning Journey DB** | Campus Management → Course Management → **Learning Journey DB** → database editor | Database **Settings** or **Sync now** on the list |
| **Course only (no link)** | Course **Learning Journey** tab | Not applicable — no database sync |

For blocks built [directly in a course](/docs/fuxam-web/lms/learning-journey/edit-a-learning-journey) without a database link, use the course editor — not this workflow.

## Key concepts

| Term | Meaning |
|------|---------|
| **Save** | Updates the library master only; linked course copies stay unchanged until you sync |
| **Save & Sync** | Updates the master and pushes changes to all linked course copies |
| **Synced** | Course copy matches the last successful sync from the source |
| **Pending** | Changes exist that have not yet been pushed to linked courses |
| **Conflict** | A course copy was edited locally after the last sync — resolution is required before push |
| **Error** | Sync failed; check the sync panel for details |
| **Break link** | Stops future syncs; the course keeps its current content |
| **Reset to source** | Overwrites the course copy with the current library version |

## Open a library block

1. Go to **Campus Management → Course Management → Content Block DB**.

2. Click the block name to open its edit page.

3. Update the title, content, or block-specific settings and save.

Fields you change here are **master content** — titles, files, questions, and similar. Course-specific delivery settings on linked copies (due dates, conditions, publish status) are configured in the course [learning journey editor](/docs/fuxam-web/lms/learning-journey/edit-a-learning-journey).

## Sync changes to linked courses

When a library block is **linked** to copies in course learning journeys, saving edits may prompt you to sync:

1. After saving, choose **Save & Sync** to push changes to all linked course copies, or **Save** to update the library only.

2. Alternatively, use the **Syncs** column actions on the Content Block DB table to sync individual blocks or run **Sync all**.

The sync panel shows linked courses, last synced time, and status (**Synced**, **Pending**, **Conflict**, or **Error**). Resolve conflicts when a course copy was edited locally after the last sync.

:::tip
Use **Save** first when you are still drafting a library change and linked courses should not receive it yet. Run **Save & Sync** or **Sync all** when the master is ready for rollout.
:::

## Break or reset a link

If a course copy should diverge from the library:

- **Break link** — stops future syncs; the course keeps its current content.
- **Reset to source** — overwrites the course copy with the current library version.

These actions are available from the block sync panel in the course **Learning Journey** editor or from library sync controls.

| Action | Use when |
|--------|----------|
| **Break link** | A section needs permanent local customisation; you accept no further central updates |
| **Reset to source** | Local edits went wrong and you want to discard them in favour of the library master |

:::danger
**Reset to source** overwrites the course copy with the library version. Local content changes on that copy are lost.
:::

## Edit Learning Journey DB content

For full journeys stored as databases, open the entry from the **Learning Journey DB** tab, edit in **Table View**, then sync linked courses from **Settings** or the **Sync now** action on the list.

:::warning
Courses linked to a Learning Journey DB cannot edit journey content locally. The message *This course is linked to a Learning Journey DB. Edit the database course and sync instead.* appears when sync is active.
:::

This is the main behavioural difference from **individual linked blocks**: a fully synced journey locks the entire course learning path to the database master, whereas linked library blocks typically leave course-specific settings editable on the copy.

## Best practices

- Communicate before **Sync all** on widely linked blocks — enrolled students may see updated material mid-term.
- Resolve **Conflict** status promptly; conflicting copies block clean propagation and confuse editors about which version is authoritative.
- Prefer editing the database over editing linked course copies; local course edits on synced fields create conflicts and undermine the single-source-of-truth model.

## Common pitfalls

- **Saving without syncing** — the library updates but linked courses still show the old content until you sync.
- **Editing a linked course journey** — for Learning Journey DB–linked full journeys, the course editor is read-only; edit in Campus Management instead.
- **Forgetting course-specific settings** — sync updates master content; due dates and publish status still live on the [course copy](/docs/fuxam-web/lms/learning-journey/edit-a-learning-journey).

## FAQ

**Why do I see Conflict after editing?**

A linked course copy was changed locally after the last sync. Resolve the conflict in the sync panel before pushing new library changes.

**Can I edit a linked course block at all?**

Master content fields synced from the source may be read-only on the course copy. Course-specific settings such as due dates and publish status are typically still editable on the copy.

**How do I update a full journey across many courses?**

Edit the Learning Journey DB entry in Campus Management, then sync from database **Settings** or **Sync now** — the same pattern as individual blocks, at journey scale.

## Related pages

**[Create a content block](/docs/fuxam-web/lms/content-database/create-a-content-block)**

Add new library blocks before you edit them.

**[Organize content](/docs/fuxam-web/lms/content-database/organize-content)**

Tags, sections, and course links for databases.

**[Edit a learning journey](/docs/fuxam-web/lms/learning-journey/edit-a-learning-journey)**

Edit blocks that live directly in a course without a database link.

**[Reuse content blocks](/docs/fuxam-web/lms/content-database/reuse-content-blocks)**

How blocks and journeys are imported or linked in the first place.
