!> To unlock online publishing features for your slide decks [activate paid service](https://gitpitch.com/pricing).
Private publishing is ideal for providing early-access or previews of your slide deck. It can also be used to manage temporary audiences for your slide deck. Private publishing is also known as *stealth mode*.
### Publish 4.0
To publish a [4.0 slide deck](/whats-new-in-40.md) to the cloud you *must* activate the `gitpitch` setting in the [PITCHME.yaml](/conventions/pitchme-yaml.md) for your deck as shown here:
```yaml
gitpitch : 4.0
```
When activated as shown your slide deck can be published and shared in the cloud on **gitpitch.com**.
### Using Public Repos
Private publishing is not supported within *public* repositories.
### Using Private Repos
To publish a private slide deck using a *private* repository on GitHub, GitLab, or Bitbucket you must activate the `stealth` setting in the [PICHTME.yaml](/conventions/pitchme-yaml.md) for your deck. The stealth setting accepts a comma-separated list of one or more stealth-tokens. A token can be any arbitrary string value you define.
The following *PITCHME.yaml* snippet demonstrates a single value on the `stealth` setting:
Once activated, `git-push` your presentation files on any branch. A valid token is then required to open the [unique URL](#private-deck-urls) for your private slide deck in the cloud. The token must be appended to the URL using `?s={token}` or `&s={token}` query parameter syntax.
?> Any attempt to access a private slide deck without a valid stealth-token will be denied.
### Private Deck URLs
The following snippets demonstrate the basic structure of private slide deck URLs on **gitpitch.com**. Decks can be uniquely identified using PITCHME.md paths, branch names, tag names, and commit ids.
?> If the files for your slide deck are maintained within a branch named **master** you can omit the branch name from the URL for your slide deck. All other branches require the branch name to be specified on the URL.
