diff --git a/gk-dev/gk-dev-automations.md b/gk-dev/gk-dev-automations.md
index a112a16..5cbaafb 100644
--- a/gk-dev/gk-dev-automations.md
+++ b/gk-dev/gk-dev-automations.md
@@ -5,7 +5,7 @@ taxonomy:
     category: gk-dev
 ---
 
-<kbd>Last updated: July 2025</kbd>
+<kbd>Last updated: December 2025</kbd>
 
 Use **GitKraken.dev Automations** to create rule-based workflows that trigger actions when pull requests and issues match specific conditions. Automations help you streamline collaboration and enforce consistency across teams.
 
@@ -62,13 +62,28 @@ Click <button class="button button--success button--ui button--nolink">+ Create
 
 ***
 
+
 ## Set Conditions
 
-Conditions define when an action is triggered. GitKraken currently supports:
+Conditions define when an automation is triggered. GitKraken currently supports the following condition types:
+
+- **Pull request content**  
+  Trigger on PR metadata, activity, or discussion.
+
+- **Review: Status**  
+  Watch for approvals, missing reviews, or stale feedback.
+
+- **Branch and origin**  
+  Trigger based on the source or target branch, or the repository.
+
+- **CI/CD checks**  
+  React to build, test, and deployment outcomes.
 
-- **File location**
-- **File contents**
-- **Pull request**
+- **File condition**  
+  Match file paths, folders, or specific code snippets.
+
+- **GitKraken AI**  
+  Analyze pull request diffs and metadata to detect conditions you care about.
 
 <figure>
   <img src="/wp-content/uploads/gkdev-createautomations3.png" class="help-center-img img-bordered" alt="Conditions configuration screen">
@@ -106,15 +121,46 @@ You can choose whether **all** or **any** of the conditions must be true.
 - **PR author**
 - **PR labels**
 
+
 ## Actions
 
 GitKraken supports these automation actions:
 
-- **Add comment**: Posts a comment on the PR.
-- **Add to checklist**: Adds checklist items to the PR description.
-- **Add assignee**: Assigns the PR to selected users and can include a message.
-- **Add label**: Applies a GitHub label to the PR.
-- **Add reviewer**: Assigns a reviewer or team, with an optional message.
+### AI
+
+- **GitKraken AI**  
+  Post a comment with a summary generated from an AI prompt.
+
+### People
+
+- **Notify user**  
+  Send a custom notification to selected users.
+
+- **Add reviewer**  
+  Assign a reviewer or team, with an optional message.
+
+- **Add assignee**  
+  Assign the PR to selected users, optionally including a message.
+
+- **Remove reviewer**  
+  Unassign a reviewer or team from the PR.
+
+- **Remove assignee**  
+  Unassign a user from the PR.
+
+### Pull Request
+
+- **Add comment**  
+  Post a comment on the PR.
+
+- **Add label**  
+  Apply a GitHub label to the PR.
+
+- **Close PR**  
+  Automatically close the pull request.
+
+- **Add to checklist**  
+  Add checklist items to the PR description.
 
 <div class='callout callout--warning'>
     <p><strong>Note:</strong> Authors can’t review their own PRs. If selected, GitKraken will skip that step and apply all others.</p>
diff --git a/gk-dev/gk-dev-dashboard-management.md b/gk-dev/gk-dev-dashboard-management.md
index eb669a8..12a6ca4 100644
--- a/gk-dev/gk-dev-dashboard-management.md
+++ b/gk-dev/gk-dev-dashboard-management.md
@@ -4,7 +4,7 @@ description: Learn how to add and interpret key DORA and Pull Request metrics, a
 taxonomy:
     category: gk-dev
 ---
-<kbd>Last updated: October 2025</kbd>
+<kbd>Last updated: December 2025</kbd>
 
 
 ## Overview
diff --git a/gk-dev/gk-dev-insights.md b/gk-dev/gk-dev-insights.md
index a99b48b..cc2ee2e 100644
--- a/gk-dev/gk-dev-insights.md
+++ b/gk-dev/gk-dev-insights.md
@@ -4,7 +4,7 @@ description: Learn how to request access, understand plan availability, and conn
 taxonomy:
     category: gk-dev
 ---
-<kbd>Last updated: October 2025</kbd>
+<kbd>Last updated: December 2025</kbd>
 
 GitKraken Insights turns raw Git data into clear, useful metrics for developers and leaders. It pulls code activity, pull requests, issues, and CI/CD results into a single view that fits directly into existing workflows.
 
@@ -43,6 +43,7 @@ Currently, Insights supports connections with GitHub, GitLab and Jira Cloud. Sup
 3. Authorize GitKraken Insights by GitClear to connect with GitHub.  
 4. Select which repositories to track. Use the filter option at the top of the page to quickly narrow down the list.  
 
+
 <figure>
   <img src="/wp-content/uploads/data-connection-oct-25.png" srcset="/wp-content/uploads/data-connection-oct-25@2x.png" class="help-center-img img-bordered" alt="Overview of GitKraken Insights" />
   <figcaption style="text-align: center; color: #888">Connect GitHub, GitLab, or Jira to enable Insights</figcaption>
@@ -58,6 +59,15 @@ Currently, Insights supports connections with GitHub, GitLab and Jira Cloud. Sup
   <figcaption style="text-align: center; color: #888">Select which repos to import. You can always import more later.</figcaption>
 </figure>
 
+#### Avoiding GitHub API rate limits
+
+If you're importing a large number of repositories—typically over 100, depending on size and commit history—you may encounter GitHub's hourly API rate limits. This can temporarily throttle other GitHub services used by your organization.
+
+To avoid this, additional members of your organization can connect to Insights using a [Lead role](/gk-dev/gk-dev-organization/#roles). When multiple Leads are connected, GitClear distributes processing across their GitHub tokens to help avoid throttling.
+
+After the initial import is complete, rate limit issues are unlikely to recur.
+
+
 ---
 
 ### 2. Setup role