# Hiding features

> Turn off Tamr's post-meal review ask, take-home suggestions, treats on the house or voice notes for an app that has its own, from the dashboard or from your app.

Source: https://tamr.link/docs/guides/hiding-features

An app with its own reviews, its own loyalty programme or its own retail suggestions can turn Tamr's off, so the diner never sees two of the same thing. You can only hide a feature, never turn on one the restaurant switched off.

## In the dashboard, today

In **Settings > Waiter in your app**, the restaurant can switch each of these off for its app: voice notes, the post-meal review ask, take-home suggestions and treats on the house. Changes are drafts until the restaurant publishes them, and the restaurant's switch applies whatever your app sends.

## From your app

| Feature | `appearance` field | Since |
| --- | --- | --- |
| Voice notes | `hideVoice` | 1.0.0 |
| The post-meal review ask | `hideReviews` | Next release |
| Take-home suggestions after the meal | `hideRetailSuggestions` | Next release |
| Treats on the house | `hideLoyalty` | Next release |

Pass them in `appearance` when you create the controller, or later with `setAppearance`. They are off-only: the restaurant's own switch wins, and an app never turns a feature on. On the web and in React Native, `microphone: false` also turns voice notes off without asking for the microphone.

## From your own chat

An app that draws its own chat sends `hide` with every message to [Send a message](https://tamr.link/docs/api/chat): `{ "retailSuggestions": true, "loyalty": true }` turns take-home suggestions and treats off for that turn. [Get the waiter](https://tamr.link/docs/api/get-waiter) returns the restaurant's own switches in `app`, which apply whatever is sent.
