> For the complete documentation index, see [llms.txt](https://docs.meterian.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meterian.io/the-meterian-webapp/advanced-functionalities/library-approval-policies.md).
# Library approval policies
Library Approval Policies will allow you to establish strict control over the third-party libraries permitted within their codebase. When enabled, Meterian monitors projects for unauthorized libraries and flags them as policy violations, ensuring that only vetted components are used.
Policies can be managed by account or team administrators and can be scoped to either a specific team or the entire organization. When defining scopes, account-level policies automatically take precedence over team-level policies. In essence an account-level policy is a policy that an account administrator creates and is associated with the account (the ‘Everyone’ team), while a team-level policy is a policy that a team admin or an account admin creates and is associated with a specific team.
Policies are defined by specific attributes, including library name, version range (expressed in the [interval notation](https://en.wikipedia.org/wiki/Interval_\(mathematics\))), severity, and associated team.
Administrators have versatile options for policy management. They can manually define policies in the dashboard (Dashboard > Policies > Libraries):
Utilize the 'Auto Provision' feature in the Policies tab to generate a baseline from existing reports:
Additionally, admins can approve or exclude dependencies directly from within security assessment reports:
To activate the feature please contact our [support email](mailto:support@meterian.com).
