> For the complete documentation index, see [llms.txt](https://hayston.gitbook.io/flp-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hayston.gitbook.io/flp-wiki/configuration-reference/bedrock.md).

# Bedrock policies

Set these options in the standalone server's FLP configuration, or on the **proxy** in a proxy network.

| Option                       | Default | Purpose                                                                                                  |
| ---------------------------- | ------- | -------------------------------------------------------------------------------------------------------- |
| `autoLoginFloodgate`         | `false` | Permit supported Floodgate passwordless login                                                            |
| `autoRegisterFloodgate`      | `false` | Permit supported Floodgate account creation; requires permitted auto-login                               |
| `allowFloodgateNameConflict` | `false` | Allow an unlinked Bedrock name to overlap a Java premium name under the applicable path's conflict rules |

For the auto-auth options, use:

| Value         | Meaning                                                      |
| ------------- | ------------------------------------------------------------ |
| `false`       | Do not grant this automatic action                           |
| `true`        | Permit it for supported linked/unlinked identities           |
| `linked`      | Permit only identities linked by Floodgate to a Java account |
| `no-conflict` | Permit subject to the applicable Java-name conflict check    |

`allowFloodgateNameConflict` should be treated as the boolean conflict switch, not as another auto-login selector. Keeping a non-conflicting Floodgate prefix is strongly recommended. Do not remove prefixes simply to reuse Java accounts.

## Spigot, Paper and Folia

With supported AuthMe versions, FLP can handle a Floodgate account before the login dialog appears. Automatic account creation requires both auto-registration and auto-login. Support varies by authentication plugin; see the [integration guide](/flp-wiki/compatibility-and-integrations/bedrock.md).

The Java `auto-register-unknown` setting does not replace `autoRegisterFloodgate`. Admission, account creation, linked identity and name conflict are separate checks.

## Fabric limits

Fabric accepts only the documented signed, **unlinked existing completed account** route. `autoLoginFloodgate` must permit it (`true` or applicable `no-conflict`); `linked` does not expand Fabric support. `autoRegisterFloodgate: true` does not enable Fabric account creation. Native EasyAuth Floodgate auto-login stays disabled so it cannot bypass FLP's checks.

See [Geyser/Floodgate setup and trust](/flp-wiki/compatibility-and-integrations/bedrock.md) before enabling these policies.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://hayston.gitbook.io/flp-wiki/configuration-reference/bedrock.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.