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

# Modeling With Multiple Restrictions

> Modeling system that requires multiple authorizations before allowing users to perform actions on particular objects

In this guide we are going to model system that requires multiple authorizations before allowing users to perform actions on particular objects using [Auth0 FGA](https://docs.fga.dev/fga.md).
For example, *[users](https://docs.fga.dev/fga-concepts.md#what-is-a-user)* are allowed to delete a `document` if both of these conditions are met:

* they are a member of the organization that owns the document
* they have writer permissions on the document

In this way, we prevent other users from deleting such document.

**When to use**

This is useful when:

* Limiting certain actions (such as deleting or reading sensitive document) to privileged users.
* Adding restrictions and requiring multiple authorization paths before granting access.

## Before You Start

In order to understand this guide correctly you must be familiar with some [Auth0 FGA Concepts](https://docs.fga.dev/fga-concepts.md) and know how to develop the things that we will list below.

<details>
  <summary>
    You will start with the *[authorization model](https://docs.fga.dev/fga-concepts.md#what-is-an-authorization-model)* below,
    it represents a `document` *[type](https://docs.fga.dev/fga-concepts.md#what-is-a-type)* that can have users
    **[related](https://docs.fga.dev/fga-concepts.md#what-is-a-relation)** as `writer` and `organizations` related as `owner`.
    Document's `can_write` relation is based on whether user is a writer to the document. The `organization` type can have users related as `member`.

    Let us also assume that we have:

    * A `document` called "planning" owned by the ABC `organization`.
    * Becky is a member of the ABC `organization`.
    * Carl is a member of the XYZ `organization`.
    * Becky and Carl both have `writer` access to the "planning" `document`.
  </summary>

  The current state of the system is represented by the following relationship tuples being in the system already:

  ```json theme={null}
  [
    // organization ABC is the owner of planning document
    {
      "user": "organization:ABC",
      "relation": "owner",
      "object": "document:planning"
    },
    // Becky is a writer to the planning document
    {
      "user": "user:becky",
      "relation": "writer",
      "object": "document:planning"
    },
    // Carl is a writer to the planning document
    {
      "user": "user:carl",
      "relation": "writer",
      "object": "document:planning"
    },
    // Becky is a member of the organization ABC
    {
      "user": "user:becky",
      "relation": "member",
      "object": "organization:ABC"
    },
    // Carl is a member of the organization XYZ
    {
      "user": "user:carl",
      "relation": "member",
      "object": "organization:XYZ"
    }
  ]
  ```

  > [!NOTE]
  >
  > Note that we assign the organization, not the organization's members, as owner to the planning document.

  ***

  In addition, you will need to know the following:

  ### Modeling Parent-Child Objects

  You need to know how to model access based on parent-child relationships, e.g.: folders and documents. [Learn more →](https://docs.fga.dev/modeling/basics/parent-child.md)

  ### Modeling Roles And Permissions

  You need to know how to model roles for users at the object level and model permissions for those roles. [Learn more →](https://docs.fga.dev/modeling/basics/roles-and-permissions.md)

  ### Auth0 FGA Concepts

  * A [Type](https://docs.fga.dev/fga-concepts.md#what-is-a-type): a class of objects that have similar characteristics
  * A [User](https://docs.fga.dev/fga-concepts.md#what-is-a-user): an entity in the system that can be related to an object
  * A [Relation](https://docs.fga.dev/fga-concepts.md#what-is-a-relation): is a string defined in the type definition of an authorization model that defines the possibility of a relationship between an object of the same type as the type definition and a user in the system
  * An [Object](https://docs.fga.dev/fga-concepts.md#what-is-an-object): represents an entity in the system. Users' relationships to it can be define through relationship tuples and the authorization model
  * A [Relationship Tuple](https://docs.fga.dev/fga-concepts.md#what-is-a-relationship-tuple): a grouping consisting of a user, a relation and an object stored in Auth0 FGA
  * [Intersection Operator](https://docs.fga.dev/modeling/configuration-language.md#the-intersection-operator): the intersection operator can be used to indicate a relationship exists if the user is in all the sets of users
</details>

## Step By Step

With the above authorization model and relationship tuples, Auth0 Fine-Grained Authorization (FGA) will correctly respond with `{"allowed":true}` when \*[check](https://docs.fga.dev/fga-concepts.md#what-is-a-check-request)\*is called to see if Carl and Becky can write this `document`.

We can verify that by issuing two check requests:

What we would like to do is offer a way so that a document can be written by Becky and Carl, but only writers who are also members of the organization that owns the document can remove it.

To do this, we need to:

1. [Add can\_delete relation to only allow writers that are members of the ownership organization](#01-add-can_delete-relation-to-only-allow-writers-that-are-members-of-the-ownership-organization)
2. [Verify that our solutions work](#02-verify-that-our-solutions-work)

### 01. Add can\_delete Relation To Only Allow Writers That Are Members Of The Ownership Organization

The first step is to add the relation definition for `can_delete` so that it requires users to be both `writer` and `member` of the owner. This is accomplished via the keyword [`and`](https://docs.fga.dev/modeling/configuration-language#the-intersection-operator).

### 02. Verify That Our Solutions Work

To verify that our solutions work, we need to check that Becky can delete the planning document because she is a writer AND she is a member of organization:ABC that owns the planning document.

However, Carl cannot delete the planning document because although he is a writer, Carl is not a member of organization:ABC that owns the planning document.

## Related Sections

Check the following sections for more on how to model privileged access.

[Modeling: User Groups
Learn about how to add group members.](https://docs.fga.dev/modeling/basics/user-groups.md)

[Modeling: Blocklists
Learn about how to set block lists.](https://docs.fga.dev/modeling/basics/blocklists.md)

[Modeling: Public Access
Learn about model public access.](https://docs.fga.dev/modeling/basics/public-access.md)