# Setting Up ACF

{% hint style="info" %}
This article is about the WordPress plugin GutenBricks, which allows you to create Gutenberg blocks using the Bricks Builder page builder in a no-code approach. Visit [**GutenBricks.com**](https://gutenbricks.com) for more information.
{% endhint %}

### TLDR;

Do what you normally do with ACF and Bricks, but make sure to set the location rule so that the field group is linked to the template. Read: [#most-important-step-set-location-rule](#most-important-step-set-location-rule "mention")

### Common Workflow

Step 1: Create a field group as usual

**Step 2: Set the location rule to Bricks Template or individual template post <- MOST IMPORTANT**

Step 3:  Apply the field values in the Bricks template

Step 4: Enter the ACF value in the Gutenberg editor

### Most Important Step: Set Location Rule&#x20;

Once you create a field group, all you have to do is set up a correct location rule to make the field group visible when users edit the block in the Gutenberg editor.

There are two common ways:

1. Assigning `Post` to a particular block as shown in the screenshot below.
2. Or less commonly, assigning `Post Type` to `Template.` In this case, the field group will be visible in every block. This can be handy if you have general fields used by every block.

<figure><img src="/files/yIQUT1ZpnPPQNlV6pC5f" alt=""><figcaption><p>Here, we are assigning the field group to FAQ Bricks Template</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gutenbricks.com/dynamic-data/acf/setting-up-acf.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.