KNOWLEDGE MOBILITY
Share the Live Source Take a Connected Copy
Give collaborators access to the base you maintain. When work needs to branch off, take a copy of the relevant notes and the links between them.
KNOWLEDGE HANDOFF
Don't Lose the Context When Work Changes Hands
A handoff should preserve the reasoning and make clear which version the next person can work from.
OUTDATED COPIES
Copies Miss Later Updates
You improve a method after sending it to a colleague. They still work from the version you sent last week.
Each correction means another attachment and another check that everyone has the same version.
MISSING CONTEXT
Conclusions Without Context
You send a useful conclusion to someone taking over the work. The evidence and examples stay in your base.
They can read the answer, but they have to reconstruct why it applies and when it might need to change.
THE LOREBO APPROACH
Choose What the Next Person Receives
Give people live access when they should keep using the source you maintain.
Export a connected selection when the next project needs its own copy.
The material can travel with its context, and you choose where future edits belong.
Video coming soon
We’re preparing a walkthrough for this section.
LIVE BASE SHARING
Keep Collaborators on One Live Source
Invite a named recipient to one whole base. Their grant sets what they can do while the host is reachable.
CURRENT SOURCE
Keep One Source Current
You maintain the original base. People with access can read its current notes from their own Lorebo workspace.
A correction is available the next time they use the base, without sending a new copy.
RECIPIENT PERMISSIONS
Set Recipient Permissions
Grant read, write, or admin access according to what the person needs to do in the shared base.
The grant covers that one base. Your other collections remain outside the invitation.
ACCESS LIFECYCLE
Decide When Access Ends
Set an expiry for temporary work, or revoke a grant when the person no longer needs the base.
When the grant ends, their live access ends. The original remains available to you.
REMOTE ACCESS
Bring People and AI to the Running Source
A shared-base invitation gives a person access in Lorebo. Remote MCP connects a compatible AI client to the host.
Choose the base and give the recipient the access they need. Send the invitation from the host that serves the base.
Video coming soon
We’re preparing a walkthrough for this section.
Accept the invitation and open the live base in Desktop. Browse or edit the source according to the access you received.
Video coming soon
We’re preparing a walkthrough for this section.
A compatible AI client can read permitted notes on your running Lorebo host. Managed remote MCP connects it over HTTPS.
SELECT, TRANSFER & MERGE
Carry the Context Not the Whole Project
Give independent work the notes and connections it needs, with a chance to review what will move.
FOCUSED SELECTION
Save a Reusable Scope
Save the selection rules as a scope in a Smart Folder. Reopen it to check the matching notes.
Preview the selection before export so unrelated work stays in the original base.
INDEPENDENT COPY
Export a Separate Copy
Graph export copies the selected notes and the links between them into a separate Lorebo base file.
Develop the copy on its own. Later changes to it stay separate from the original.
REVIEWED MERGE
Review Before You Merge
Preview what an incoming base would add to the writable destination. Check potential duplicates and conflicts.
Apply the merge after review, then inspect the result in the base that will carry the work.
EXPERTISE REUSE
Let Good Work Travel Without Rebuilding Its Context
Keep one maintained reference available, or give a new project a connected starting point of its own.
LESS REPEATED HANDOFF
Keep the Original Within Reach
Give a team live access to the methods and evidence you maintain. Later tasks can use the current guidance.
The same source remains available to everyone with access while the host is reachable.
ROOM TO ADAPT
Give the Copy Room to Grow
Give a project a focused copy of the notes and links it needs. It can adapt the material to its own work.
Edits belong to that project’s copy. The source can continue developing on its own terms.
TWO WAYS TO HAND OFF
You Choose Where the Next Change Belongs
Keep people on the live source when their work should use or improve the shared reference. Their permissions govern what they can change.
Give a project an independent copy when it needs to adapt the material. The relevant knowledge travels with its context, and future changes belong to that project.
Video coming soon
We’re preparing a walkthrough for this section.
Frequently Asked Questions
Good to Know
Can I share just a few pages?
A live invitation covers a whole base. Export selected pages or put them in a separate base before sharing.
What if the host goes offline?
Live access pauses until the host is reachable again. An exported base remains usable on its own device.
Can I revoke an export?
You can revoke live access. An exported copy stays with the person who received the independent file.
Can I limit my agent’s access?
You can restrict your agent’s access to a shared base further. Its permissions stay within the owner’s grant.
Are attachments exported?
A scoped export contains selected notes and links between them. Keep the attached files separately.
What if a note already exists?
Merge skips conflicting content with the same identity. The preview flags similar notes for you to review.
Explore More

Share a live base or transfer a selected copy. Pro adds whole-base sharing and Lorebo-managed remote MCP.