> For the complete documentation index, see [llms.txt](https://docs.snyk.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.snyk.io/platform-administration/snyk-platform-subscription/legacy-plans/usage-settings.md).
# SKU-based licensing usage settings
How to view Snyk usage details for your Group or Organization, including tests and contributing developers
{% hint style="info" %}
The following usage settings are relevant only for subscriptions to the legacy, SKU-based licensing offerings for Snyk Open Source, Snyk Code, Snyk Container, and Snyk IaC. These settings do not apply to any capabilities entitled through the [Snyk Platform Subscription](/platform-administration/snyk-platform-subscription/snyk-platform-subscription-mechanics.md).
{% endhint %}
In your Group or Organization, navigate to **Settings** > **Usage** to view Snyk usage details for your Group or Organization:
* **Test usage**: the number of tests used
* **Contributing developers**: the number of developers contributing to Projects
{% hint style="info" %}
For more information about test frequency settings, visit [Project actions](https://docs.snyk.io/scan-fix-and-prevent/scan-with-snyk/snyk-projects#project-actions-on-the-project-listing-page) on the Project Listings page, which also explains bulk actions.
{% endhint %}
## Test usage
The **Test Usage** section shows how many tests you are using over the current billing period:
Test usage data
{% hint style="info" %}
Test limits vary for Snyk products and plans.
For the Free plan, the limits are 400 tests for Open Source, 100 tests for Code, 300 tests for IaC, and 100 tests for Container.
To see the limits that apply to you and how much of them you have used, open **Usage** in your Organization settings. On an Enterprise plan, your contract sets your limits, and Snyk does not publish them here. Your Snyk account team can confirm them. For more details, visit [Plans and pricing](https://snyk.io/plans/). For details of how Snyk counts tests, visit [What counts as a test?](https://docs.snyk.io/snyk-data-and-governance/what-counts-as-a-test)
{% endhint %}
## Contributing developers
Snyk defines contributing developers as developers who made a commit in the last 90 days to a private Git repo that Snyk monitors.
The **Contributing developers for SCM and CLI integrations** section shows contributing developer counts, both at the Organization level and the Group level.
The developer count is the number of developers who have contributed to the default branch of any private repository connected to an integration.
Snyk does not count contributions to public (open-source) repos because the pricing model is based on the number of contributing developers to private repositories.
The contributing developers count shows:
* **Total unique contributors across all integrations**: the number of contributors across all the integrations in your Snyk account. Snyk counts each contributing developer only once, even if they have contributed to multiple integrations or multiple repositories.
* **Breakdown by integration**: the number of contributors, Organizations, and repos in that integration.
Snyk identifies a contributor by the author email field in their local Git settings.
---
# 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.snyk.io/platform-administration/snyk-platform-subscription/legacy-plans/usage-settings.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.
