# Claims

> This page is about FlutterFlow (the app builder you use by describing your app), not FlutterFlow Studio.

URL: https://docs.flutterflow.io/ffx/claims

Turn claims on or off for a person in Backend › People, so your app's rules let them do what their role allows.

Use **Backend › People** to give a person the roles and other permissions that your app checks, such as an admin or moderator role. These are called *claims*.

## Declare claims {#declare-claims}

Your app's backend lists the claims that it can give people. To add one, ask the agent in a thread to declare it in your app's backend, and say what each role can do. For example:

> Example request: "Add an admin role. Only admins can delete other people's posts."

Then [push the thread](https://docs.flutterflow.io/ffx/push). **People** lists a new claim only after you push the thread that declares it. You can give people only the claims that your app's backend declares. To try a role on a thread's own accounts before you push, see [Test sign-in](https://docs.flutterflow.io/ffx/test-sign-in).

## Give claims {#give-a-person-claims}

To turn a person's claims on or off:

1. Open **Backend › People**, and select the person.
2. Under **Claims**, click **View claims**.

   A dialog titled **Claims for** and the person's name lists every claim that your app declares, each with a switch.
3. Turn on each claim that the person should have, and turn off each claim that they shouldn't. Turning a claim off removes it from the person.
4. For each claim that's on, choose or enter its value in the box that follows the switch. A yes-or-no claim takes **true** or **false**, and a claim with a fixed list of values offers that list.
5. Click **Save claims**.

<Mock name="claims-dialog" alt="The Claims for dialog with two claims, one turned on with its value shown, and the Save claims button." />

A claim that your app's backend no longer declares still shows for a person who has it. To remove it, turn it off.

## How claims are checked {#how-your-app-checks-claims}

Your app's backend rules check a person's claims when the person reads or changes data. For example, a rule can let only people with the admin claim delete other people's posts. The rules run in the backend, so a rule that checks a claim protects the data even if the app shows a button for the action.

When you save a person's claims, the change applies to the person across your app.

## Troubleshooting {#if-something-goes-wrong}

For problems with backend records or sign-in setup, see [Troubleshoot data and sign-in](https://docs.flutterflow.io/ffx/troubleshoot-data).