# Name who decides

At the end, a gate in your workflow names the teammate who decides it: the workbench says who it waits for, and the Slack thread mentions them and takes their press.

## At a glance

**Time:** 5 minutes.

**You need:**

- A workflow of your own with a Choice, Approve or Lock step: [Build your own](build.md)
- The teammate's email, as a member of your org

## Steps

1. **Open the workflow in the builder and click the gate.**

   You should see: the gate's form: its **Kind**, the question, then **Who decides**.

2. **Type the teammate's email in Who decides**, or pick it from the list when this machine is signed in to your org. The builder saves as you type.

   You should see: under the field, `Mentioned in the Slack thread when this waits, and heard for it. Anyone in the workbench can still answer.`

3. **Run it until the gate opens.**

   You should see: the decision card's eyebrow `Needs you · <step> · waits for <email>`, and the same `waits for <email>` on its row in **Needs you**.

4. **Start the same task from Slack** and let it reach the gate.

   You should see: the post `<@teammate> decides this.` and its title `<step> waits for <@teammate>`. Their press decides it, as does yours.

## Good to know

- Who decides is a hint about a person, never a permission. Anyone in the workbench may still answer the gate.
- In Slack it widens only that gate's buttons. Everything else in the thread still hears only the person who started it.
- The decided line in the conversation reads `You …` for everyone. The run's record names the member who decided.
- No direct message is sent. The mention in the thread is Slack's notification.

## If something is off

- **The thread says `<email> decides this; they open the link`.** Settings → Slack has no Slack person for that email. Match them there, or they answer from **Open in workbench**.
- **No list of members under Who decides.** This machine is not signed in to an org. Type the email instead.

## Next

- [Share a run](share.md)
- [From Slack](slack.md)