# Vuti for teams

> Separate creation, feedback, approval, and delivery so collaboration stays clear.

Canonical: https://www.vuti.io/docs/use-cases/teams
Last verified: 2026-08-11
Open in Vuti: https://www.app.vuti.io/review

## Define the handoff first

Before creating content, agree on who owns the source material, who edits, who gives final approval, and who watches delivery. One person may hold several roles, but the decision should still be explicit.

## Step 1: Centralize approved context

Put audience, positioning, voice guidance, claims, offers, and reusable media where the whole workspace can use them.

## Step 2: Plan with a named outcome

Give each slot a campaign purpose, platform, owner, and intended publishing time.

## Step 3: Keep feedback on the draft

Request changes or comment on the exact post instead of splitting the decision across chat threads.

External reviewers can use a public preview when they should comment without joining the workspace. Disable the link when the review is finished, and never use it for confidential material.

## Step 4: Approve with delivery in view

Confirm the copy, selected media, destination account, schedule, and readiness findings together.

## Step 5: Close the loop

Use Today and delivery history to assign publishing failures, reply opportunities, and learnings.

**Approval is a product state**

A message saying “looks good” is not the same as approving the item in Vuti. Use the review action so scheduling and delivery have a reliable source of truth.

## Continue learning

- [Set up the workspace](https://www.vuti.io/docs/workspace): Manage brand context, members, ownership, and roles.
- [Run the approval workflow](https://www.vuti.io/docs/review): Edit, request changes, approve, schedule, and resolve feedback.