> ## Documentation Index
> Fetch the complete documentation index at: https://docs.devtune.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Actions Workspace Overview

> Learn how DevTune's Actions workspace turns signals, content preferences, and outcomes into evidence-backed recommendations.

DevTune does not stop at showing metrics. The Actions workspace turns AI Search, Community Discourse, Owned Content, adoption, and AI Traffic signals into a working queue of evidence-backed recommendations.

The workspace has three main surfaces:

* **Suggestions** - Active recommendations that DevTune believes are worth considering now
* **Backlog** - Work your team has adopted
* **Outcomes** - Completed work and the impact it created

Alongside the workspace, the **Alerts** page keeps a project-level history of important events and digest notifications.

## Suggestions

Suggestions are evidence-backed recommendations generated from the current state of your project.

Each suggestion can include context from:

* AI Search prompt and citation performance
* Competitor movement
* Community Discourse overlaps
* Owned-content gaps or changes
* Adoption or AI Traffic context where relevant

For each suggestion, you can:

* **Generate brief** to create a fuller execution plan
* **Add to backlog** to commit the work
* **Use existing asset** when you already have a page that should satisfy the recommendation
* **Snooze** when the idea is valid but not timely
* **Dismiss** when it is not a fit

## Briefs

Generating a brief creates a reusable execution artifact for the action. The brief is designed to answer:

* What should we make or update?
* Why does it matter?
* What evidence supports it?
* Which existing assets or external pages matter?

Brief generation uses your available content credits. Included monthly credits are used first; purchased credits are the fallback for manual generation after monthly included credits are exhausted. See **[Account & Billing Overview](/account-billing/overview)** for the full credit policy.

DevTune may automatically prewarm briefs for high-priority suggestions so they are ready faster, but automatic prewarming only uses a capped portion of your included monthly credits and never uses purchased add-on credits. If a ready brief becomes stale, the existing markdown stays visible until you choose to regenerate it.

When project content preferences are enabled, Actions and briefs also respect the project's allowed and blocked content formats. Teams can use this to avoid formats that do not fit their strategy, such as comparison pages, while still letting DevTune choose the best allowed format for each recommendation.

## Backlog

Backlog contains work your team has chosen to do. This includes:

* Suggestions adopted from the feed
* Manual actions created directly by your team

Backlog items move through a simple execution workflow:

* **Backlog**
* **In Progress**
* **Blocked**
* **Done**
* **Canceled**

Generated actions keep their detail rail in backlog, so you can still review the summary, evidence, and brief after adopting them.

## Outcomes

Outcomes help you review what has been completed and what effect it had. Use this view to connect executed work to downstream movement in AI Search, Community Discourse, Owned Content, and related signals.

When you complete an Action, DevTune creates an **intervention** that monitors the target URL for citation changes. The system tracks whether your content changes resulted in increased AI citations, validating which Actions actually moved the needle.

## How recommendations become work

The usual workflow is:

1. Review **Suggestions**
2. Generate a brief where more context is needed
3. Move the best items into **Backlog**
4. Execute the work
5. Review completed work in **Outcomes**

## Alerts and notification history

The project **Alerts** page shows project-scoped notifications and event history, including important regressions, competitor threats, and digest-style updates.

Account-level notification settings control which events interrupt you immediately and which ones stay in scheduled digests.

## Accessing the workspace

Inside a project sidebar:

* **Actions** opens the actions workspace
* **Alerts** opens the project event history

Within **Actions**, you will see:

* **Suggestions**
* **Backlog**
* **Outcomes**

## Getting Started

1. **[Review the Actions workspace](/insights-actions/actions-hub)** - See how suggestions, briefs, and backlog work together
2. **[Configure alerts and digests](/insights-actions/alerts)** - Decide what should interrupt you
3. **[Explore analytics](/analytics/overview)** - Validate the evidence behind a recommendation

## Next Steps

* **[Working with Actions](/insights-actions/actions-hub)** - Review suggestions, backlog, and outcomes
* **[Alerts](/insights-actions/alerts)** - Set up notifications and digests
* **[Analytics](/analytics/overview)** - Investigate the data behind a recommendation