Document community GitLab Duo usage policy and cap management

### GitLab Duo for Contributors

To support our mission to enable everyone to contribute, we offer complimentary GitLab Duo Enterprise

licenses across the GitLab community forks for all our wider community contributors.

licenses and [GitLab Duo Agent Platform](https://docs.gitlab.com/user/duo_agent_platform/) access

across the GitLab community forks for all our wider community contributors.

[GitLab Duo](https://about.gitlab.com/gitlab-duo/) features Code Suggestions, Chat, Root Cause Analysis

and more AI-powered features to help boost efficiency and effectiveness by reducing the time required

to write and understand code and pipelines.

Community contributors receive GitLab Duo once approved for [requesting access to the community forks](https://gitlab.com/groups/gitlab-community/community-members/-/group_members/request_access).

Usage limits and expectations are defined in the [GitLab Duo usage guidelines for community contributors](https://gitlab.com/gitlab-community/meta/-/blob/main/docs/duo-usage-guidelines.md).

#### Managing community GitLab Duo usage

GitLab Duo Agent Platform usage in the `gitlab-community` group is metered in GitLab Credits and capped per user

(see the usage guidelines for the current value). Managing it requires the Owner role on the

[`gitlab-community`](https://gitlab.com/gitlab-community) top-level group.

To check usage:

1. Go to `gitlab-community` > **Settings > GitLab Credits**, or open the

   [group credits dashboard](https://gitlab.com/groups/gitlab-community/-/settings/gitlab_credits_dashboard).

1. On the **Usage by user** tab, sort by **Total credits used**. The **Usage control status** column shows

   **Blocked usage** for anyone who has reached their cap.

1. Select a username to see their individual usage events, with links to Duo Agent Platform session details.

To reach out about high usage that does not look contribution-related, comment on the contributor's

[onboarding issue](https://gitlab.com/gitlab-community/community-members/onboarding/-/issues) using the

`Duo usage` comment template. Check their [contributor profile](https://contributors.gitlab.com/) and recent

merge requests first.

To raise, lower, or remove a user's cap:

1. On the group credits dashboard, select **Credit caps**.

1. Under **Per-user cap overrides**, select **Add override** (or adjust an existing row), pick the user,

   set the cap, and select **Save**. Turning the override's **Enabled** toggle off returns the user to the default flat cap.

1. Reply on the contributor's onboarding issue noting the new cap and why, so there is a record.

A user who is blocked becomes unblocked as soon as their override cap is above their current usage.

The default flat cap for all users is set on the same page.

Duo seats cannot be removed individually: they are managed at the top-level group and synced automatically

from the members of `gitlab-community/community-members`. To block a user's GitLab Duo Agent Platform usage

while keeping their community forks membership, set a per-user cap override of `0`.

To remove them from the community forks entirely, remove them from the `gitlab-community/community-members` group.

### Highlighting high-value contributions with product bonuses