External sharing and exports

Share content externally and export information with the right controls in place.

External sharing and exports are useful when people need information from Oculon but do not need to work inside the platform every day.

Decide whether the recipient needs live access

Before you export or share externally, decide whether the recipient needs:

• a live planning surface they can return to
• a controlled shared view of the current result
• a fixed snapshot or export for offline use

Use the narrowest option that still supports the review.

Common external patterns

Common use cases include:

• board packs for executive review
• tables for offline analysis
• controlled snapshots for audit or approval workflows
• exported outputs for people who only need the result, not the full planning context

The right choice depends on whether the recipient needs current data, repeat access, or only one handoff.

Protect context when data leaves Oculon

An exported number can lose the context that made it meaningful.

That context often includes:

• the active scenario
• the current filters
• the time range or reporting period
• whether the result came from a board, view, or model surface

Include enough framing so the recipient understands what they are looking at and whether it is still current.

Recheck external risk each time

Do not assume an export is safe just because the source item was shared correctly inside Oculon.

Before you send something out, confirm:

• the recipient really needs it outside the workspace
• the surface does not expose more detail than intended
• the exported result still matches the scenario and time context you mean to share

External sharing should reduce friction, not create a second uncontrolled copy of sensitive planning data.