> ## 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.

# Managing Group Access

> Granting a group of users access to a particular object

Auth0 FGA allows you to grant a group of users access to a particular object.

**When to use**

Relationship tuples are helpful when you want to specify that a group of users all have the same relation to an object. For example, Auth0 FGA allows you to:

* Grant a group of `engineers` `viewer` access to `roadmap.doc`
* Create a `block_list` of `members` who can't access a `document`
* Share a `document` with a `team`
* Grant `viewer` access to a `photo` to `followers` only
* Make a `file` viewable for all `users` within an `organization`
* Manage access to a `database` for `users` in a certain `locale`

## Before you start

Familiarize yourself with basic [Auth0 FGA Concepts](https://docs.fga.dev/fga-concepts.md) before you continue.

<details>
  <summary>
    In the example below, you have the following [authorization model](https://docs.fga.dev/fga-concepts.md#what-is-an-authorization-model) with two [types](https://docs.fga.dev/fga-concepts.md#what-is-a-type):

    * `company` that can have an `employee` relation
    * `document` that can have a `reader` relation.
  </summary>

  ***

  In addition, the following concepts are important to group access management:

  ### Modeling user groups

  Auth0 FGA allows you to add users to groups and grant groups access to an object. [For more information, see User Groups.](https://docs.fga.dev/modeling/basics/user-groups.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): 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
</details>

## Step by step

### 01. Adding company to the document

The following [Relationship Tuple](https://docs.fga.dev/fga-concepts.md#what-is-a-relationship-tuple) assigns ever `employee` of a type `company`  a `reader` relationship with a particular object of type `document`, in this case `document:planning`):

```json theme={null}
[
  // Every employee in the company can read document:planning
  {
    "user": "company:xyz#employee",
    "relation": "reader",
    "object": "document:planning"
  }
]
```

### 02. Add an employee to the company

Below is a [relationship tuple](https://docs.fga.dev/fga-concepts.md#what-is-a-relationship-tuple) specifying that `Anne` is an `employee` of `company:xyz`:

### 03. Checking an individual member's access to an object

Call the Check API to verify that Anne can read `document:planning` returns true:

The same check for Becky, a different user, returns false, because Becky does not have an `employee` relationship with `company:xyz`:

## Related Sections

Check the following sections for more on how to model group.

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

[Managing Group Membership
Learn about managing group membership.](https://docs.fga.dev/writing-data/managing-group-membership.md)