> For the complete documentation index, see [llms.txt](https://docs.opencollective.com/help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.opencollective.com/help/fiscal-hosts/fiscal-host-settings/security.md).
# Security
{% hint style="danger" %}
With the implementation of the new [Dashboard interface](https://docs.opencollective.com/help/product/understanding-your-dashboard), we are currently in the process of updating our documentation and some pages may be out of date. Thank you for your patience. Please [contact](https://opencollective.com/contact) our support team if you need any assistance.
{% endhint %}
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.
### How to enforce 2FA for all admins and set your rolling payout limit
#### 1. Go to your fiscal host page
#### 2. Click on ADMIN on the right-hand side
#### 3. Click on Organization Settings
#### 4. Click on Security
#### 5. Check All 'Your Fiscal Host' admins must have two-factor authentication and/or set a rolling limit 2FA for payouts
**6. Click Save**
**When visiting admin pages without 2FA, admins will be prompted to enable it**
[](https://user-images.githubusercontent.com/1556356/202162859-7e9cf92e-cb93-49fe-975d-701e7c0b76e6.png)
---
# 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://docs.opencollective.com/help/fiscal-hosts/fiscal-host-settings/security.md?ask=&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.
