diff --git a/doc/development/policies.md b/doc/development/policies.md
index f0c9d0ec5f95cdc0b106c24f72899ee8b6a3e96e..ddd6b8e9bcec63712b28536bc1d9bb69cf7d503b 100644
--- a/doc/development/policies.md
+++ b/doc/development/policies.md
@@ -10,6 +10,8 @@ The DeclarativePolicy framework is designed to assist in performance of policy c
 
 The policy used is based on the subject's class name - so `Ability.allowed?(user, :some_ability, project)` creates a `ProjectPolicy` and check permissions on that.
 
+The Ruby gem source is available in the [declarative-policy](https://gitlab.com/gitlab-org/ruby/gems/declarative-policy) GitLab project.
+
 ## Managing Permission Rules
 
 Permissions are broken into two parts: `conditions` and `rules`. Conditions are boolean expressions that can access the database and the environment, while rules are statically configured combinations of expressions and other rules that enable or prevent certain abilities. For an ability to be allowed, it must be enabled by at least one rule, and not prevented by any.