Skip to main content
Omni supports two ways to create and modify content:

​
Draft-only

Every Omni document has two states: draft and published. When you create a draft, you’re creating a saved - but unpublished - version of a document, including its workbook and dashboard. You can make changes in the draft without impacting the live version of the document. Publishing a draft creates a new, read-only version of the document, which is the version that users with access will see when they view the document. Drafts are specific to documents and a document can only have one draft at a time. This makes drafts ideal for things like quick changes, such as adding a new chart or calculated field. If you added a new field to a model, your workflow to add the field to documents might look like this:

​
Branch Mode

If you’re familiar with git - and it’s okay if you’re not! - branches in Omni are similar. In Omni, a branch is an isolated space that allows you to modify a model and/or content without affecting the live versions, typically referred to as production. This enables you to experiment, update, and refine changes at your own pace. Merging a branch immediately applies all changes in the branch to the live environment. It also publishes an updated version of any documents that were modified as part of the branch. The ability to stage changes across documents and the model that backs them makes branches ideal for bigger changes, such as adding a new field to visualizations in separate dashboards. Let’s go back to the example in the drafts section, where you added a new field to a model. If you use Branch Mode, your workflow might look like this:

​
Comparing drafts and branches

While both drafts and branches allow you to make changes without impacting live content, there are times when one approach may be a better fit. If you need some guidance, use the following table as a starting point:

​
Getting started

Check out these guides to get started working with your Omni content: