> For the complete documentation index, see [llms.txt](https://docs.bluestorm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bluestorm.io/administration/policies.md). # Policies The policy manager is used to configure the policies that control your apps. AppControl has a default set of policy checks and all of these are included in the global policy. This is automatically created, configured and is checked automatically. The global policy can be configured to meet the needs of your organization. Policies have a specific scope. The scope determines which apps a policy applies to. There are 3 differentscopes in AppControl: * **Global.** This policy will apply to all apps in your organization. * **Group.** This policy applies to all apps in a specific app group. * **App.** This policy applies to a specific app. Policies are applied hierarchically (Global > Group > App), however only a single policy is used to check an app. If for instance a group policy is configured, this policy will be used instead of the global policy. If you want specific checks to be mandatory for all apps (or the entire policy), you can make the complete global policy mandatory or just specific checks in the global policy. There are 2 tabs in the policy manager: * [**App**](/administration/policies/app.md)**:** This is an overview of all your app policies. These policies contain the policy checks that check the state of your apps. * [**Data**](/administration/policies/data.md)**:** This is an overview of your data policies. Data policies are used to classify app data, module role access, and user role access. The information in these policies is used by app policies to check the security of your apps. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.bluestorm.io/administration/policies.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.