> ## 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 Public Access

> Granting public access to an object

In this guide you will learn how to grant public access to an [object](/fga-concepts.md#what-is-an-object), such as a certain document, using [type bound public access](/fga-concepts.md#what-is-type-bound-public-access).

**When to use**

Public access allows your application to grant every user in the system access to an object. You would add a relationship tuple with type-bound public access when:

* sharing a `document` publicly to indicate that everyone can `view` it
* a public `poll` is created to indicate that anyone can `vote` on it
* a blog `post` is published and anyone should be able to `read` it
* a `video` is made public for anyone to `watch`

## Before You Start

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

<details>
  <summary>
    Assume that you have the following [authorization model](/fga-concepts.md#what-is-an-authorization-model).\\

    You have a [type](/fga-concepts.md#what-is-a-type) called `document` that can have a `view` relation.
  </summary>

  ***

  In addition, you will need to know the following:

  ### Direct Access

  You need to know how to create an authorization model and create a relationship tuple to grant a user access to an object. [Learn more →](/modeling/basics/modeling-basics.md)

  ### Auth0 FGA Concepts

  * A [Type](/fga-concepts.md#what-is-a-type): a class of objects that have similar characteristics
  * A [User](/fga-concepts.md#what-is-a-user): an entity in the system that can be related to an object
  * A [Relation](/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](/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](/fga-concepts.md#what-is-a-relationship-tuple): a grouping consisting of a user, a relation and an object stored in Auth0 FGA
  * A [Type Bound Public Access](/fga-concepts.md#what-is-type-bound-public-access): is a special Auth0 FGA concept (represented by `<type>:*`) can be used in relationship tuples to represent every object of that type
</details>

> [!WARNING]
>
> Make sure to use unique ids for each object and user within your application domain when creating relationship tuples for Auth0 Fine-Grained Authorization (FGA). We are using first names and simple ids to just illustrate an easy-to-follow example.

[The Playground
Try this guide out on the Auth0 FGA Playground](https://play.fga.dev/)

## Step By Step

In previous guides, we have shown how to indicate that objects are related to users or objects. In some cases, you might want to indicate that everyone is related to an object (for example when sharing a document publicly).

### 01. Create A Relationship Tuple

To do this we need to create a relationship tuple using the [type bound public access](/fga-concepts.md#what-is-type-bound-public-access). The type bound public access syntax is used to indicate that all users of a particular type have a relation to a specific object.

Let us create a relationship tuple that states: **any user can view document:company-psa.doc**

> [!WARNING]
>
> **Wildcard syntax usage**
>
> Please note that type-bound public access is not a wildcard or a regex expression.
>
> **You cannot use the `<type>:*` syntax in the tuple's object field.**
>
> The following syntax is invalid:
>
> ```json theme={null}
> [
>   // It is invalid to use this syntax in the object field. The below relationship tuple is invalid and does not mean that Bob can view all documents.
>   {
>     "user": "user:bob",
>     "relation": "view",
>     "object": "document:*"
>   }
> ]
> ```

> [!WARNING]
>
> **Wildcard syntax usage**
>
> **You cannot use `<type>:*` as part of a userset in the tuple's user field.**
>
> The following syntax is invalid:
>
> ```json theme={null}
> [
>   // It is invalid to use this syntax as part of a userset. The below relationship tuple is invalid and does not mean that members of any org can view the company-psa document.
>   {
>     "user": "org:*#member",
>     "relation": "view",
>     "object": "document:company-psa.doc"
>   }
> ]
> ```

### 02. Check That The Relationship Exists

Once the above *relationship tuple* is added, we can [check](/fga-concepts.md#what-is-a-check-request) if **bob** cab `view` `document`:**company-psa.doc**. Auth0 FGA will return `{ "allowed": true }` even though no relationship tuple linking **bob** to the document was added. That is because the relationship tuple with `user:*` as the user made it so every object of type user (such as `user:bob`) can `view` the document, making it public.

## Related Sections

Check the following sections for more on how to model with Auth0 FGA.

[Modeling: Getting Started
Learn about how to get started with modeling.](/modeling/getting-started.md)

[Configuration Language
Learn about Auth0 FGA Configuration Language.](/modeling/configuration-language.md)

[Modeling Blocklists
Learn about model block lists.](/modeling/basics/blocklists.md)