Share & collaborate

Shared folders let signed-in teammates open the same project files, see collaboration presence, and work from a synchronized cloud workspace.

Choose local or shared work#

Use a local project when work should stay on one computer, must continue offline, or is not ready for the team. Use a shared folder when collaborators need access to the same current files.

Files in a shared folder are not local-only. They synchronize through Nebula Writer's cloud service, require network access for current shared state, and follow the folder's role permissions.

Create and invite#

Cloud collaboration is a Pro feature for the people creating, editing, sharing, or managing cloud folders. A typical setup is:

1. Sign in to a Pro account.
2. Create a shared folder from the project sidebar.
3. Add the files intended for the team.
4. Generate an invite link with the appropriate role.
5. Send the link through your normal secure communication channel.

Do not place private scratch files in a shared folder unless every member should be able to access them.

Understand roles#

Free users can accept an invite and view a shared folder. If a free user accepts an editor invite, the folder remains read-only until Pro cloud write access is available.

Role labels do not override plan entitlements. The app's invite and member controls show the effective access for the current account.

Work with shared files#

Presence shows when collaborators are active so the team can coordinate. Before a broad structural edit, tell collaborators what you are changing and save the current document.

For text files, shared updates can appear while people work. Office files use format-specific synchronized operations and save flows. A shared DOCX, workbook, or presentation deserves extra care because one operation can affect layout, formulas, or many objects.

For binary Office files:

• Work in a narrow page, sheet, or slide range.
• Save explicitly before switching projects.
• Confirm the shared save or sync state.
• Reopen the file when another collaborator's update looks stale.
• Keep a named delivery copy for important milestones.

Use the agent in a shared folder#

The agent can work with shared documents subject to the current user's access. Name the scope and avoid surprising collaborators:

Compare @launch-plan.docx with @risk-register.xlsx. List discrepancies only. Do not edit either shared file.

For a proposed change:

Update only the owner and due-date columns in the Risks table from @risk-register.xlsx. Preserve all other content and show the affected operations for review.

Review and save the result before announcing that the shared file is ready.

Connectivity and conflicts#

Shared work needs a network connection for synchronization. If connectivity drops, avoid assuming a local edit has reached the team. Wait for the save or sync state to recover, then reopen the shared file if needed.

When the app reports a stale file or conflicting state, compare the versions before choosing reload or overwrite. For important deliverables, keep an external backup in addition to shared history.

Remove access deliberately#

Owners should review members and invite links when a project changes hands or closes. Remove access that is no longer needed, and move sensitive follow-on work into a new local or shared folder with the right membership.