Review the whole space before adding members
In an Ora shared space, a reader can view the planning data, including notes, steps and recorded time. A personal observation written inside that space should not be treated as a note visible only to you. Before inviting someone, review everything the space contains.
Shared spaces are implemented and documented as a Pro capability in validation; visual and real multi-device acceptance remain pending. This guide explains the documented scope and proposes a preliminary review. It does not claim a live two-account test or guarantee instant collaboration.
An example without personal information
Imagine a space for a small home exhibition. “Choose three photos” has two steps: “Collect six candidates without identifying details” and “Choose three with permission to display them”. The shared note says: “Confirm permission for each image before finalizing the selection.” This supports reviewing preparation without including a personal reflection.
Another working sentence now appears: “I am worried about one particular person’s reaction.” You decide to retain that reflection outside the shared space and not copy its private context. The shared note keeps only the practical permission question. This is manual content selection, not a feature automatically detecting and moving sensitive notes.
In this example, the reviewer only needs to read the candidates and steps; editing stays with the person preparing the exhibition. You therefore choose the reader role for that review. Before inviting anyone, check that the entire space, not just this activity, is suitable for them. Rehearse the decision on paper without creating invitations or using real personal data.
Choose a role for the action the person needs
An owner manages access and edits; an editor edits planning; a reader views, can export or leave, and cannot write. Reader status limits editing; it does not make a note private to its author.
A Pro account creates the space and sponsors editing; invited participants do not each need to buy Pro to participate according to their role. The space is separate from personal planning. Personal provider connections are not mounted inside it.
Do not confuse this with a public snapshot link, which is another sharing workflow. Nor should another planner’s permissions or limits be assumed to apply to Ora.
Account for copies a person has already received
The documentation allows deliberate exports such as PNG or planning JSON backups. Someone who downloaded a file can retain it. Revoking access later does not delete that copy or establish its disappearance from a disconnected device.
Decide what belongs in the space before sharing it. Review notes and records as well as activity names. If something was shared accidentally, review access and the actual scope of copies without promising removal you cannot verify.
Shared-space drafts remain in memory and do not use the personal local copy. Do not treat them as durable recovery backups: reloading can lose unsaved changes. If a conflict appears, review the versions shown before choosing; there is no automatic field merge.
Prepare a decision before opening the space
Write three agreements: what content will be shared, who needs editing access and what information stays outside. Then check the current feature status and decide whether that scope meets your needs. This guide does not create invitations or change access for you.
Ora offers a temporary no-registration demo for exploring planning; it does not replace a real-membership and permissions test. Check account terms before using the shared-space capability.