If a client can open a Notion page but cannot see its synced block, check access to the page containing the original block. Sharing the page with the copy does not make the original's content visible. Notion's original-page access rule explicitly requires the viewer to have access to that source page.
I'd check that permission before rebuilding the block, since a rebuild can change the evidence before you know the cause. Then decide what the client gets: access to the original page if the whole page is appropriate, or an independent copy of the approved text if it isn't. Making the original public is a poor shortcut when that page also contains internal material.
Confirm the symptom under the client's account
| Client's result | First check | Next step |
|---|---|---|
| Cannot open the destination page | Destination sharing and the invited account | Fix page access before diagnosing the synced block. |
| Opens the page but cannot read the synced content | Access to the page marked ORIGINAL | Choose an appropriate source-page grant or unsync this copy. |
| Reads the content but cannot edit it | Edit access to the original block | Change editing access only if the client needs to edit the shared text. |
Check using the client's intended account, not your own editor view. Invited guests need their own Notion account to access a shared page, as the guest-sharing instructions explain. Confirm the invitation went to the account the client is using. If the whole destination is inaccessible, the client portal access review covers that broader problem.
Reading and editing require different checks. Notion says a person needs edit access to the original block to edit any synced copy. If the client just wants to read the instructions, that doesn't justify giving them editing rights.
Locate the original without changing its text
- Open the destination page as someone who can inspect the block.
- Select the synced block. Its border identifies the synced content.
- Open Editing in … other pages and find the page marked ORIGINAL.
- Follow that location and inspect its sharing settings and surrounding content.
The location control and ORIGINAL marker are documented in Notion's synced block editing guide. Avoid changing the shared text while tracing the source: an edit in one synced instance appears in the other instances too.
Say the client destination is Client handoff, and its location list points to Internal operations, marked ORIGINAL, and Team handbook. Internal operations is the source that matters, even if Team handbook is already shared. Write down that original URL and look through its contents before you choose a repair.
Give the client the original page's link and check whether that same account can open it. If that account cannot open it, you have found the documented permission condition. If the account already opens the original, that condition alone does not explain the missing copy; keep the evidence and use the final check below.
Share the original only if the whole page is appropriate
Inspect the source page before you change access. A handoff checklist, for example, might sit on an operations page beside internal budget notes. Granting the client access to that page lets them read what's on it, so fixing one missing paragraph with a broad permission grant can create a larger problem.
If the original is suitable for the client, open Share, enter the client's email, choose the required permission level, and select Invite. For a client who only needs the instructions, start with Can view. Notion's page-sharing steps let you choose a level for each invitation, and its access-level definitions distinguish reading from editing and sharing.
If the client is already listed, use the permission dropdown beside that person instead of adding another invitation. Review other grants too: Notion applies the broadest access a person has, so a narrow direct grant does not cancel wider access granted elsewhere.
This repair keeps the live connection. Once the client has access to both the original page and the destination, they should be able to read the copy. Future edits to the synced content still affect every connected instance, which is useful for shared instructions that must stay consistent.
Keep a private original private by unsyncing one copy
If the client needs the text but should not access the original page, make the destination copy independent. I would choose this for a fixed handoff note that does not need future updates from the internal source.
Use the menu on the client copy. Do not delete the original or choose Unsync all to repair one destination. Notion warns that with more than 10 copies, those actions remove all copies; after deleting the original in that case, Undo will not restore them.
- Confirm you are on the client destination and have selected its copy.
- Hover over that copy and select ••• → Unsync.
- Review the independent text, including every link and embedded item, before the client uses it.
Notion's single-copy Unsync procedure breaks that copy's connection. Subsequent source edits will no longer update its text. Assign someone to keep the independent instructions current, especially if they describe a changing process.
Unsyncing preserves page links inside the block. It doesn't make their private destinations readable: those pages still have their own sharing permissions. If the client can read the paragraph but can't open an internal link in it, the handoff isn't finished. Remove the link if it shouldn't be there, or deliberately share the target once you've approved it.
For continuing updates, build an appropriate shared source
If the client needs future updates and the current original can't be shared, create a separate page that holds only the approved instructions. In the example, name it “Shared handoff instructions” and leave internal budget notes on Internal operations. You're redesigning content and access here; another copy of the old original would keep the same permission dependency.
- Put the approved, current instructions on the new source page. Inspect page links and embedded content before sharing it.
- Select those blocks, open ⋮⋮ → Turn into → Synced block, then use the block’s copy icon and paste it into the client destination. These are Notion’s documented sync controls.
- Share the new original with the intended client account at Can view, following the invitation steps above. Review the new destination copy’s location list: the ORIGINAL page should now be Shared handoff instructions.
- Have the client check the new copy and its appropriate linked targets before retiring the old handoff arrangement. Keep the private original and its other instances intact.
Assign an owner to the approved source. That person should update the shared instructions when the process changes and keep internal-only additions on the internal page. A new source page is useful because its full contents can be appropriate for the client, not because synced blocks replace sharing permissions.
Confirm the result from the client's side
Ask the client to reopen the destination with the intended account and confirm that the exact text is visible. If you kept the synced copy, also confirm they can open the source page. If you unsynced it, check that the wording is current and that any linked pages are appropriate and accessible. Confirm editing separately, and only if it's part of the intended workflow.
If the client can access both pages but the synced text is still missing, record the destination URL, original URL, account involved, and exact visible message for Notion support. Describe whether the problem affects only that account or also someone with source access. Preserve the original and its other copies while the cause is unresolved; a destructive rebuild would change the evidence before the permission diagnosis is complete.
