# Marketing

Marketing is where you write what you tell your customers. Each announcement is a **Marketing
release**: you give it a title, attach what it's about, such as the releases that shipped, the
features, the feature requests and the customer feedback behind them, and Productmind drafts from
those. A Marketing release has its own pace: you can announce a feature before, after or without a
release.

For each Marketing release, Productmind drafts public release notes: a headline, a short summary,
and the things your customers can now do, in plain benefit language. A Marketing release can have
several public release notes, for example one for each audience or each step of a launch. Your team
edits the notes together as a document, comments on them and tags them, then publishes them. Every
publish keeps an exact, numbered copy of what you told your customers. You can unpublish the notes,
and republish the same version later.

Productmind can also write long-form blog posts about the features a Marketing release is about, or
about passages of its published notes. Your team edits each post together, then approves it. Every
approval keeps an exact, numbered copy of the post.

Once notes are published, you can email each customer who asked for something the Marketing release
covers, or who reported a bug it covers. Productmind drafts a personal email for each of them: what's
new for them first, then a short summary from the notes you choose. You review the emails, choose who
gets them and send them, and Productmind keeps a log of every email sent.

<Availability plan="Scale and Enterprise. On other plans the Marketing menu entry shows a lock, and opening it names the plan that includes it." permission="Marketing: Read to see Marketing. Marketing: Update to create Marketing releases, attach what they're about, and write their notes, blog posts and customer emails. Marketing: Create to publish the notes, approve blog posts and send customer emails. Marketing: Delete to delete Marketing releases and blog posts. Customer emails also need Contacts: Read." />

## Key concepts

**Marketing release.** One announcement to your customers, with its own title, an ID such as
**MKT-3**, and a status you set. It holds everything Marketing writes for that announcement: its
public release notes, its blog posts and its customer emails. It isn't a release of your code: see
[Releases](/user-guide/product/releases) for those.

**Sources.** What a Marketing release is about, and what Productmind drafts from. Attach any mix of:
- **Releases**: the work that shipped in them, the features it belongs to and the customer feedback
  behind them;
- **Features**: their specifications, sub-features and the requests behind them, whether or not they
  have shipped in a release;
- **Feature requests**: what customers asked for, and the feature it was built into, if any;
- **Customer feedback**: a meeting, a support conversation or a feedback conversation, with what it
  led to.

A Marketing release can have up to 50 sources. A [private feature](/user-guide/product/private-features)
can't be a source.

**Status.** Where a Marketing release stands. You set it yourself, and it never blocks anything:

| Status | Meaning |
| --- | --- |
| **Planned** | Not started yet. Every new Marketing release starts here. |
| **In progress** | Its notes, posts or emails are being written. |
| **Announced** | It's out: your customers have been told. |
| **Archived** | Put away. The list hides it unless you filter on **Archived**. |

**Marketing materials.** What you write for customers in a Marketing release: its public release
notes and its blog posts. The list can show only the Marketing releases with materials, or only
those without.

**Public release notes.** What you tell your customers in a Marketing release. They are separate
from the release notes on a release itself, which are written for your team and go into its pull
requests and tags. Productmind reads your team's release notes as background when a release is a
source, and never copies or changes them. See [Releases](/user-guide/product/releases).

A Marketing release can have several public release notes. Each is one document, published on its
own, in three parts:
- **Headline**: the first line, as **Heading 1**, up to 120 characters, naming the main benefit.
- **Summary**: the paragraph right under it, up to 400 characters, on what customers get.
- **What's new**: one section for each thing customers can now do, each with a **Heading 2** and a
  few sentences. Several tasks and bug fixes that together give customers one new thing are one
  section.

**Customer quote.** A section can include a short quote from your customer feedback, as a quote
block, shown as coming from "a customer". Productmind removes names, companies and other
identifying details from it, and you confirm that every quote identifies no one before you publish.

**Published version.** Each time you publish, Productmind keeps an exact copy of the notes,
numbered **Version 1**, **Version 2** and so on. The newest version, marked **Live**, is the one your
customers were last told.

**Unpublished.** When you unpublish the notes, no version is live: every published version is kept,
and none is marked **Live** until you republish the newest one or publish a new one. Unpublishing one
public release notes document leaves the Marketing release's other notes as they are. While none of
them is live, the Marketing release's customer emails can't be written or sent.

**The state of the notes.** Each public release notes document shows one of these:

| State | Meaning |
| --- | --- |
| **No notes** | The Marketing release has no public release notes yet. |
| **Writing draft** | Productmind is writing a draft. |
| **Draft** | Notes that have never been published. |
| **Published** | The notes are exactly the newest published version. |
| **Unpublished changes** | The notes were edited or rewritten after the last publish. The last published version stays the live one until you publish again. |
| **Unpublished** | The notes were unpublished: no version is live, whether or not they were edited since. |

**Blog post.** A long-form article for your customers about what a Marketing release announces. A
Marketing release can have any number of blog posts. Each one is about features among its sources,
passages of one of its published public release notes, or both. A blog post is one document:
- **Title**: the first line, as **Heading 1**, up to 150 characters.
- **Introduction**: the paragraphs right under it.
- **Sections**: each with a **Heading 2**, on the problem, how it works and what your customers can
  now do. A section can include a customer quote, as in the notes.

**Guidance.** What you ask Productmind for when it writes a blog post:
- **Tone**: **Friendly**, **Professional** or **Enthusiastic**.
- **Length**: **Short** (about 500 words), **Standard** (about 900 words) or **Long** (about 1,400
  words).
- **Angle**: anything you want the post to lead with or focus on, such as who it's for.

**Approved version.** Each time you approve a blog post, Productmind keeps an exact copy of it,
numbered from 1. Approving doesn't publish the post anywhere: it records the text your team agreed
on.

**The state of a blog post.** Each blog post shows one of these:

| State | Meaning |
| --- | --- |
| **Writing draft** | Productmind is writing a draft of the post. |
| **Draft failed** | The post's first draft couldn't be written, so the post has no text yet. |
| **No draft** | The post has no text yet, for example because you stopped its first draft. |
| **Draft** | A post that has never been approved. |
| **Approved** | The post is exactly its newest approved version. |
| **Approved, with changes** | The post was edited or rewritten after its last approval. The last approved version stays as it was until you approve again. |

**Customer email.** A personal email to one customer about a Marketing release. It greets them by
name, describes each of their requests and each bug of theirs that the Marketing release covers,
then sums up the rest from the published public release notes you choose. It names no other
customer or company and quotes no one. It comes from "Your organization via Productmind", and a reply goes to the person who
sent it.

**Recipient.** A contact behind a feature request or a bug report the Marketing release's sources
cover: a feature request you attached, one built into a feature you attached, one or a bug delivered
by a release you attached, or one behind customer feedback you attached. Customer feedback that led
to no feature request or bug report adds no one. Two people at one company each get their own email.
Contacts that share one email address get one email between them.

**Send log.** Every email sent, or tried, about a Marketing release: who it went to, what it
covered, which notes it summed up, who sent it and when, and the exact text.

## The Marketing page at a glance

In the sidebar, under **Product**, choose **Marketing**.

**The list of Marketing releases** is on the left, newest first: each with its ID, its title, what
it holds (such as **2 release notes** and **1 blog post**, or how many sources it is written from
while it holds nothing yet), its readers' likes and dislikes once anyone reacted, and its status.
Choose a Marketing release to open it beside the list; choose it again to close it.

**An open Marketing release** has its header across the top: its ID, its status, which you can
change, **Delete** when it can be deleted, **Close** and its title, which you can edit. Under the
header, a menu down the left lists:
- **Overview**, its sources and everything it holds;
- **Public release notes**, each notes document with its state, and **+** to write new notes;
- **Blog posts**, each blog post with its state, and **+** to write a new one;
- **Customer emails**, with how many customers were emailed, and **+** to write the customer emails
  once notes are published.

Choose an item in the menu to open it beside the menu. When the page is narrow, such as with the
list open on a small screen, the menu shows only its icons: point at one to read its name. A group
with nothing in it yet shows its **+** there instead.

**The search box** at the top of the page finds a Marketing release by its title or its ID, such as
**MKT-3**. Its filters narrow the list by **Status** and by **Materials**: **With materials** lists
the Marketing releases that have public release notes or a blog post, in any state, and **No
materials yet** those with neither. Archived Marketing releases are listed only when you choose
**Archived** under **Status**. Marketing remembers your search and filters for your next visit.
**New Marketing release** is beside the search box.

Every item opens under the Marketing release's header with a header of its own: what is open and its
state (such as **Public release notes** and **Draft**), its actions, then its title.

**The overview** shows when the Marketing release last changed, then:
- **Sources**: what the Marketing release is about, with **Add source**, and how many
  customer-facing features they cover. A note under them says when the sources hold nothing
  customer-facing, or when an attached release isn't **Released** yet;
- **Public release notes**, with **New notes**;
- **Blog posts**, with **New blog post**;
- **Customer emails**.

**Public release notes with no text yet** show one card: what a draft would be written from (the
sources and the customer-facing features they cover) with **Generate draft** and **Write it
yourself**.

**Once they have text**, the notes open as a document:
- **The header** shows **Public release notes** and the state of the notes, then **Publish**, and
  the title under them.
- **The document** is a rich-text editor with a formatting toolbar, an outline of its sections, and
  the comments beside it. The toolbar ends with **Regenerate**, and **Edited** in it says when the
  notes were last saved.
- **Publishing**, in the rail on the right, shows what publishing checks and every published
  version.
- **Written from**, in the rail too, shows the Marketing release's sources and their customer-facing
  features with the feature requests behind them. To change the sources, open the overview.
  **Tags** is in the rail too.

**Blog posts** shows the Marketing release's blog posts, each with its title and its state, and
**New blog post** in the header. A blog post opens as a document, like the notes, with **Approve**
and **Delete** in its header, and **Close** to go back to the blog posts. Its toolbar holds the
**Tone**, **Length** and **Angle** the next draft is written with, and **Regenerate**. **Tags** and
two tabs are in the rail on the right:
- **Before you approve** shows what approving checks.
- **Written from** shows what the post is about, and is where you change it: its features with
  the feature requests behind them, and the public release notes with its passages highlighted.
  Choose a feature or request to open it there.

## Creating a Marketing release

Create a Marketing release for each announcement you want to make, then attach what it's about.
Nothing on a release creates one for you: a release becomes part of an announcement only when you
attach it.

### To create a Marketing release

1. In **Marketing**, choose **New Marketing release**.
2. Enter a title, such as **Faster search**, and confirm.

The Marketing release opens on its overview, with the status **Planned** and the next ID, such as
**MKT-4**.

### To add sources

1. Open the Marketing release's overview.
2. Under **Sources**, choose **Add source**.
3. Choose the kind (a release, a feature, a feature request or customer feedback), search, and
   choose what to attach.

The source is listed under its kind, and the next draft is written from it. Something already
attached is not added twice. You can't attach a private feature, or more than 50 sources.

Attach what proves what customers can now do, such as a release or a feature, and the feedback that
says why it matters. Customer feedback on its own frames the story but never proves that something
exists: attach the features or feature requests it led to as well.

### To remove a source

On the overview, point at the source and choose its **x**.

Notes, posts and emails already written don't change. The next draft is written without it.

### To rename a Marketing release or change its status

On the overview, edit the title, or choose the status and pick another. The status is yours to set:
Productmind never changes it, and it doesn't block publishing or sending.

### To archive a Marketing release

On the overview, change its status to **Archived**.

It leaves the list, with everything it holds kept. To find it again, filter the list on
**Archived**, and change its status back to bring it back.

### To delete a Marketing release

1. On the overview, choose **Delete**.
2. Productmind asks you to confirm. Confirm to delete it.

Its notes, blog posts, customer email drafts, comments and tags are deleted with it. Its sources
themselves are not: a release, a feature, a request or feedback you attached stays as it was.

**Delete** is offered only while nothing of the Marketing release was ever published, approved or
emailed. After that, archive it instead: what you told your customers, and the log of every email
sent, is kept.

:::caution
Deleting a Marketing release can't be undone.
:::

## Writing the public release notes

### To draft the notes with Productmind

1. In **Marketing**, open the Marketing release and choose **+** beside **Public release notes** in
   its menu.
2. Choose **Generate draft**.

The new notes show **Writing a draft**, and so does their item in the menu. Productmind writes the draft
in the background from the sources, so you can open other pages meanwhile. When it is done, the notes
open as a document with the draft in it.

You can draft more public release notes for the same Marketing release the same way: each is its
own document, published on its own.

### To write the notes yourself

1. In **Marketing**, open the Marketing release and choose **+** beside **Public release notes** in
   its menu.
2. Choose **Write it yourself**.
3. Write the headline as **Heading 1**, the summary under it, then a section with a **Heading 2**
   for each thing customers can now do.

You can also type `# ` at the start of a line for **Heading 1**, `## ` for **Heading 2** and `> `
for a quote block. You can write notes yourself with no sources attached.

### To stop a draft

While a draft is being written, choose **Stop**.

Productmind stops waiting for the draft, and the notes you had before, if any, stay as they were.

### When Productmind can't draft the notes

**No sources yet.** A Marketing release with nothing attached gives Productmind nothing to write
from, so **Generate draft** is unavailable until you add a source. You can still write the notes
yourself. See [To add sources](#to-add-sources).

**Nothing in these releases rolls up to a customer-facing feature.** Every source is a release, and
none of their work belongs to a feature your customers can see. Choose **Generate anyway** when your
customers would still notice the change, for example a fix they asked for: Productmind drafts, and
still leaves out what only your team would notice. Otherwise, attach the features the work is for,
or leave this Marketing release without notes.

**Nothing customer-facing.** Productmind read the sources and found nothing worth telling customers
about. Nothing is saved. When the sources are mostly customer feedback, attach the features or
feature requests that feedback led to, then choose **Try again**.

**Writing the draft failed**, or **took too long**, or **The draft came back incomplete.** Nothing
is saved; choose **Try again**. A draft that fails never changes the notes you already have.

## Editing the notes together

### To edit the notes

1. In **Marketing**, open the Marketing release and choose the notes under **Public release notes**
   in its menu.
2. Edit the text.

Your changes are saved as you type, and everyone with the notes open sees them as they are made.
If the notes were **Published**, they now show **Unpublished changes**, and your customers still see
the last published version until you publish again.

A headline over 120 characters or a summary over 400 is kept as you wrote it, but you must shorten
it before you can publish: **Publishing** shows the count.

While a new draft is being written, the notes are read-only, and the page says **Writing a new
draft**.

### To add an image

1. In the notes, place the caret where the image goes.
2. In the toolbar, choose **Insert image** and pick a PNG, JPG, GIF or WebP file of up to 10 MB.
   You can also paste an image, or drag a file from your computer into the notes.

The image appears at once, and everyone with the notes open sees it. To move it, drag it to another
place between paragraphs, or select it and choose **Move up** or **Move down**. Select an image to
resize it from its edges, align it, wrap text around it, edit its alt text or remove it.

Every image starts **private**: only people in your workspace can see it.

### To make an image public

1. Select the image.
2. In its toolbar, choose **Make public** (the globe).

A public image shows a **Public** badge. It has a link that loads without signing in, so it appears
in **What's new** and in the emails you send. To make it private again, select it and choose **Make
private**: its link stops working at once. An image you delete from the notes becomes private again
on its own, unless a published version or an email you already sent still shows it.

### To comment on the notes

1. Select the text, and choose **Comment** in the menu that opens below it.
2. Write your comment, mention people with @, and post it.

The text is highlighted and the comment appears beside it. To comment on the notes as a whole,
choose **Add a general comment**, at the top of the comments. Comments never change the notes, and
they are never published.

Mention **@pm** to have the PM agent answer, or rewrite the passage you highlighted, which you can
undo ([Ask PM in comments](/user-guide/product/ask-pm-in-comments)).

### To tag the notes

1. In the rail on the right, choose **Tags**.
2. Type a tag and press Enter.

### To write a new draft

1. In the toolbar, choose **Regenerate**.
2. Productmind asks **Write a new draft?** If the notes were edited after they were drafted, it asks
   **Replace your edited draft?** instead, and warns that the edits will be lost.
3. Choose **Write new draft**.

Productmind writes a new draft in the background, as when you first drafted, and it replaces the
notes for everyone when it is ready. Comments stay, but may no longer point at their text. The
published versions don't change.

## Publishing the notes

**Publishing** in the rail lists what publishing checks, as you write:
- **Attached releases are out**, when a release is attached: every attached release shows
  **Released**;
- **Headline**, with its length;
- **Summary**, with its length;
- **What's new**: at least one section;
- **Customer quotes**, when the notes quote customers: you confirm them when you publish.

Publishing waits only for the releases you attached: with no release attached, nothing waits, and
you publish when you're ready. **Publish** is unavailable until every attached release shows
**Released**, while a draft is being written,
while your latest edits are still saving, and when the notes are already the newest published
version. Point at it to see why. When the notes are unpublished and unchanged since, **Publish** is
not offered: choose **Republish** instead.

### To publish the notes

1. In **Marketing**, open the Marketing release, choose the notes under **Public release notes** in
   its menu, and choose **Publish** (**Publish changes** when the notes have unpublished changes, or were edited
   after you unpublished them).
2. Review the notes in the dialog, titled with the version they will become, such as **Publish
   version 2**. This is exactly what your customers will see.
3. If the dialog says **Not ready to publish**, it lists what to fix, such as a missing summary.
   Choose **Cancel**, fix it in the document, and start again.
4. If the dialog says **The text may name a customer**, check the notes don't identify those
   customers.
5. If the dialog says some images are private, they won't appear in **What's new**. Choose **Make
   them public** to include them, or publish without them.
6. If the notes quote customers, select **The customer quotes identify no one**.
7. Choose **Publish version** with its number.

The new version appears at the top of **Published versions**, marked **Live**, and the notes show
**Published**. Each public release notes document is published on its own, and each is its own entry
for your readers.

### To read a published version

In **Publishing**, under **Published versions**, choose the version.

It opens read-only, exactly as it was published, with who published it and when.

## Unpublishing and republishing the notes

### To unpublish the notes

1. In **Marketing**, open the Marketing release and choose the notes under **Public release notes**
   in its menu. They
   show **Published** or **Unpublished changes**.
2. Choose **Unpublish**.
3. Choose **Unpublish** again to confirm.

The notes show **Unpublished**, and no version is marked **Live**. **Publishing** says who
unpublished them and when. Every published version is kept, and you can keep editing the notes.

### To republish the notes

1. In **Marketing**, open the Marketing release and choose the notes under **Public release notes**
   in its menu. They
   show **Unpublished**.
2. Choose **Republish version** with its number.
3. Choose **Republish** to confirm.

The newest published version is live again, exactly as it was published, and no new version is
created. To make your edits live instead, choose **Publish changes**: they become the next version.

Every attached release must show **Released** to republish.

## Writing a blog post

A blog post tells your customers the fuller story behind an announcement. You choose what it is
about (features of the Marketing release's sources, or passages of its published public release
notes), Productmind writes the first draft in the background, and your team edits it together
before you approve it. See [Blog posts in Marketing](/user-guide/product/marketing-blog-posts).

## Emailing your customers

Once public release notes are published, **Customer emails** lists every customer behind a feature
request or a bug report the Marketing release covers, each with a personal email Productmind wrote
for them. You review the emails, choose who gets them and send them. See
[Customer emails in Marketing](/user-guide/product/marketing-customer-emails).

## How Marketing behaves

**What the draft is written from.** Productmind reads the Marketing release's sources: for each
release, the work that shipped in it and the features it belongs to; for each feature, its
specification and sub-features; for each feature request, what was asked and the feature it was
built into; for each piece of customer feedback, its summary and what it led to; and, for all of
them, the customer conversations behind them and short quotes from those conversations. A feature
reached through several sources is written about once. What the sources show customers can now do
is what the notes say; customer feedback explains why it matters, but never proves that something
exists. It also reads your product overview from the
[knowledge base](/user-guide/knowledge-base), to use your customers' words, and your team's
release notes of each attached release, as background only.

**What a blog post is written from.** Productmind reads the specifications of the features you
chose, their sub-features and the work delivered under them, the customer requests behind them, and
short quotes from those customers' conversations, with identifying details removed. It reads the
passages you chose, and the published public release notes they come from, so the post uses the same
names for things and never contradicts what you already told your customers. It also reads your
product overview, and your team's release notes of each attached release as background only, never
copied. A post about passages alone also reads every customer-facing feature of the sources, as
background.

**A blog post works without customer requests.** When no customer requests are behind a feature,
Productmind writes about it without customer quotes.

**Specifications are only read.** Writing a blog post never changes a feature or its specification.

**A post keeps what it's about.** Productmind keeps its own copy of the passages you chose, so
publishing the notes again later doesn't change what an existing post is written from. Each new
draft checks again that the post's features are still among the Marketing release's sources.

**Internal work is left out.** Productmind drafts only what a customer would notice, in benefit
language. Refactors, infrastructure, tests, dependency upgrades, internal tools and fixes a
customer wouldn't notice stay out, and so do ticket IDs, branch names and technical terms. You
review every draft before anything is published.

**Private features never appear.** A [private feature](/user-guide/product/private-features), and
the work that shipped under it, is left out of the draft, whoever asks for it. You can't attach a
private feature as a source, or choose one for a blog post.

**Customer names stay out.** Productmind drafts without naming any customer, person or company. A
capability, or a section of a blog post, has at most one quote, taken only from what your customers
said, with identifying details removed.

**The possible names check.** Before you publish, Productmind looks for the names of the contacts
and accounts behind the sources' customer feedback in your notes, and lists any it finds. Before
you approve a blog post, it does the same for the customer feedback behind the post's features. It
only knows the names recorded in Productmind, so it's a warning rather than a block: your own
check of the quotes is what counts.

**Only one draft is written at a time.** If two people start a new draft of the same notes at once,
Productmind writes one draft, and both of them see it. The same goes for each blog post and for the
customer emails, but different notes and different blog posts can be drafted at the same time.

**A draft that takes too long is stopped.** If a draft of the notes or of a blog post isn't written
within about an hour, Productmind stops it and says so. Choose **Try again**.

**Publishing checks the notes you reviewed.** If someone changes the notes while you have the
publish dialog open, publishing is refused and you're asked to review them again. A comment is not a
change. Approving a blog post checks the post you reviewed in the same way.

**A new version needs new notes.** When the draft is exactly the newest published version, there
is nothing new to publish, and the publish dialog says so. A blog post that is exactly its newest
approved version can't be approved again either.

**Changes are recorded.** Each Marketing release you create, rename, change the status of or delete,
each source you add or remove, and each publish of the notes, with the version it created, appears
in your organization's [audit log](/user-guide/settings/identity-and-access/audit-log), and so do
each unpublish and republish of the notes, each blog post approval, with its version, each blog
post you delete, and each send of customer emails.

**Likes and dislikes.** Only the release notes in **What's new**, Productmind's own, get readers'
likes and dislikes. Notes that have some show them on their row, and **Marketing** in the sidebar
counts them all: point at it for each one's.

**What a customer email is written from.** Productmind reads the public release notes you chose and
each request and bug the Marketing release covers: its title and description and what delivers it. It never sees a
contact's or company's name: any name on record is removed before it writes. It writes one paragraph
per request or bug, never per customer, and puts each customer's email together from their own.

**A customer is never emailed twice by accident.** If you press **Send** twice, two people send at
once, or your page is out of date, each customer gets one email. A second email about the same
Marketing release goes out only when you choose **Send again**, and the send log records it as the
second.

**Customer emails never quote anyone.** An email with a quote in it can't be sent. Before sending,
Productmind looks for the names of other customers on record in each email, and asks you to confirm.

**Drafting uses AI credits.** Each draft Productmind writes, of the notes, of a blog post or of the
customer emails, uses your organization's AI credits; notes you write yourself and your edits don't. See
[Usage](/user-guide/settings/billing-and-payments/usage).

## Permissions

| To | You need |
| --- | --- |
| See Marketing, Marketing releases and their sources, the notes, blog posts, published and approved versions, and what blocks publishing or approving | **Marketing: Read** |
| Create a Marketing release, rename it, change its status, and add or remove sources | **Marketing: Update** |
| Draft the notes and blog posts, draft them again, stop drafts and edit them | **Marketing: Update** |
| Publish, unpublish and republish the notes, and approve blog posts | **Marketing: Create** |
| Delete Marketing releases (while nothing of them was published, approved or emailed) and blog posts | **Marketing: Delete** |
| See customer emails and their send log | **Marketing: Read** and **Contacts: Read** |
| Write the customer email drafts and edit them | **Marketing: Update** and **Contacts: Read** |
| Send customer emails | **Marketing: Create** and **Contacts: Read** |
| Comment on the notes, blog posts and emails | **Marketing: Read** and **Comments: Create** |
| Ask PM in a comment | **Chat: Create** and **Chat: Update** |
| Apply PM's suggestion | **Marketing: Update** |
| Tag the notes and blog posts | **Tags: Create** |
| Add, move and remove images in the notes, blog posts and emails | **Marketing: Update** and **Attachments: Create** |
| Make an image public | **Marketing: Create** |
| Make an image private | **Marketing: Update** |

The **Owner**, **Admin**, **Power User** and **Product Manager** roles have every **Marketing**
permission. **Developer**, **Viewer** and **Customer** have none. With **Marketing: Update** but not
**Marketing: Create**, a role can write notes and blog posts but not publish or approve them, and
with **Marketing: Read** alone it reads them and comments on them.

**Custom** roles, and **Customized** versions of a built-in role, don't get the **Marketing**
permissions automatically. To add them, contact Productmind support. See
[Roles](/user-guide/settings/identity-and-access/roles).

**Publishing, unpublishing, republishing, approving, sending and making an image public work only
when you're signed in to Productmind yourself.** An AI assistant connected to Productmind, or an API
key, can't publish, unpublish or republish notes, approve a blog post, send customer emails or make
an image public.

## Troubleshooting

### Marketing is missing from the sidebar

Your role doesn't include **Marketing: Read**. Ask an **Owner** or **Admin** of your organization
for a role that does. See [Roles and permissions](/user-guide/reference/roles-and-permissions).

### Marketing shows a lock

Your organization's plan doesn't include Marketing: Scale and Enterprise do. Opening **Marketing**
names the plan that includes it, and an Owner or Admin can change the plan on
**Billing & Payments > Plan**. Your Marketing releases, notes, blog posts and the send log are
kept, and
come back once your plan includes Marketing. See
[Features that depend on your plan](/user-guide/reference/plans-and-limits#features-that-depend-on-your-plan).

### Publish is missing

Your role doesn't include **Marketing: Create**.

### Publish is unavailable

Point at it to see why, or check **Publishing** in the rail. The usual reasons:
- a release you attached isn't **Released** yet: wait for it, or remove it from the sources if the
  announcement doesn't depend on it;
- your latest edits are still saving: wait a moment;
- the notes have no headline, no summary or no section, or the headline or summary is too long;
- a draft is being written: wait for it, or choose **Stop**;
- the notes are already the newest published version.

### Publish is missing after unpublishing

The notes are exactly the newest published version, so there is nothing new to publish. Choose
**Republish version** with its number to make it live again.

### Unpublish or Republish is missing

Your role doesn't include **Marketing: Create**. **Unpublish** shows only while a version is live,
and **Republish** only while the notes are unpublished.

### I can't edit the notes

A new draft is being written: wait for it, or choose **Stop**. Or your role doesn't include
**Marketing: Update**, and you can read and comment on the notes but not change them.

### New Marketing release, Add source or New blog post is missing

Your role doesn't include **Marketing: Update**.

### Generate draft is unavailable

The Marketing release has no sources yet. Add a release, a feature, a feature request or customer
feedback on its overview, or choose **Write it yourself**.

### A feature can't be added as a source

It's a [private feature](/user-guide/product/private-features): nothing about it may reach your
customers. Or the Marketing release already has 50 sources.

### Delete is missing on a Marketing release

Something of it was published, approved or emailed, so it can't be deleted: change its status to
**Archived** instead. Or your role doesn't include **Marketing: Delete**.

### A Marketing release is missing from the list

It's **Archived**. In the search box's filters, choose **Archived** under **Status**.

For blog posts and customer emails, see the troubleshooting on
[Blog posts in Marketing](/user-guide/product/marketing-blog-posts#troubleshooting) and
[Customer emails in Marketing](/user-guide/product/marketing-customer-emails#troubleshooting).

## Related topics

- [Releases](/user-guide/product/releases)
- [Feature requests](/user-guide/product/feature-requests)
- [Blog posts in Marketing](/user-guide/product/marketing-blog-posts)
- [Customer emails in Marketing](/user-guide/product/marketing-customer-emails)
- [Documentation links in Marketing](/user-guide/product/marketing-documentation-links)
