Publishing & unpublishing

A finished run is private until it’s published. Before that, your organization’s admins can see the use case itself (its definition and data dictionary), but the run’s results are visible only to Neuralift. Publishing makes the run’s segments, actions, and exports visible to everyone in your organization. A run can be unpublished at any time to take it back out of view.

What publishing changes

Publishing is a visibility switch, nothing more. Here’s what a member of your organization sees before and after:

	Before publishing	After publishing
Dashboard	The use case doesn’t appear at all	A card with the run’s status, goal, and segment count
Segments & actions	Not accessible	Full access to the segment landscape, segment detail, and actions & action plans
Data dictionary	Not accessible	Readable, including column descriptions
Exports	Not available	CSV exports, where exports are enabled for your organization

Note. Publishing doesn’t move any data: no results leave Neuralift when a run is published. Delivering results to your warehouse is a separate, explicit step, and it requires the run to be published first.

Publishing a run

When a run reaches done, Neuralift quality-checks the results and reviews them with your team before anything is shared in the app. Once you’re happy with the segments and actions, Neuralift publishes the run. Its status changes to published and it appears on every member’s dashboard. Who does what is covered in Roles & permissions.

Unpublishing

Unpublishing reverses the switch: the run’s status returns to done, and the use case and its results drop out of view for your organization. Nothing is deleted: the run stays intact and can be published again later.

Unpublishing is also the first step if a published run needs to be removed entirely: only unpublished runs can be deleted. See Archiving & deleting.