> For the complete documentation index, see [llms.txt](https://documentation.opencollective.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencollective.com/fiscal-hosts/setting-up-a-fiscal-host/fiscal-host-security-old.md).

# Fiscal Host Security (Old)

Fiscal Hosts can opt-in to enforce 2FA for all of their admins. Any attempt at triggering admin operations or visiting the admin pages will be blocked until the admins enable 2FA on their profiles. A rolling payout limit can also be set so that 2FA is triggered when this limit is met.

Projects and events inherit the 2FA settings from their parents.

Access your security settings by navigating to your Fiscal Host Dashboard > Settings > Security. From here, you can set your two-factor authentication requirements for your Fiscal Host admins.

### Enforce 2FA for all admins

Information on how to enable this feature is in the [Security for Accounts](/advanced/security-for-accounts.md) section.

### Rolling Payouts

Admins will be asked to authenticate with 2FA authentication when they make their first payment and again once they’ve hit the rolling limit.

<br>


---

# 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://documentation.opencollective.com/fiscal-hosts/setting-up-a-fiscal-host/fiscal-host-security-old.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.