Update SA activity logging for Phase 1 rollout (Rattle retired) (aa74f5c4) · Commits · GitLab.com / Content Sites / handbook

content/handbook/solutions-architects/processes/activity-capture/_index.md

+4 −4

Changes for content/handbook/solutions-architects/processes/activity-capture/_index.md: 4 added lines, 4 removed lines.
Original line number	Diff line number	Diff line
		@@ -68,9 +68,9 @@ By capturing comprehensive data and leveraging AI, we are not just logging activ

		Capturing various types of data helps us build a comprehensive understanding of our activities and their impact. Below is a quick overview of the different data capture types, along with their status (Optional or Required) and links to detailed guides on how to perform each type of capture.

		### 1. Activity Based Logging (Rattle) [Required]
		### 1. Activity Based Logging (SA Activity Form) [Required]

		- Overview: Log activities such as meetings and calls using Rattle integrated with Slack and Salesforce.
		- Overview: Log activities such as meetings, calls, events, and partner work through the [GitLab SA Activity Form](https://sa-activity-e4fb10.gitlab.io/). This replaced Rattle as the single method for SA activity tracking on 2026-09-07.
		- Details: [Activity Based Logging Guide](/handbook/solutions-architects/processes/activity-capture/activity-logging)

		### 2. Email Logging (Gong) [Optional]
		@@ -97,5 +97,5 @@ Each type of data capture plays a crucial role in building a detailed and action

		## Feedback and Questions

		- Feedback: Create an issue in the Customer Success, Solutions Architecture Activity Capture project using the Feedback template.
		- Slack Channels: #rattle-users and #rattle-gitlab for discussions and questions.
		- Feedback: Create an issue in the Customer Success, Solutions Architecture Activity Capture project using the Feedback template. For the SA Activity Form specifically, use the [sa-activity project](https://gitlab.com/gitlab-com/customer-success/solutions-architecture/coe/requests/sa-activity).
		- Discussions and Questions: Open an issue in the [sa-activity project](https://gitlab.com/gitlab-com/customer-success/solutions-architecture/coe/requests/sa-activity) or bring questions to your team leader.

content/handbook/solutions-architects/processes/activity-capture/activity-logging.md

+83 −71

File changed.

Preview size limit exceeded, changes collapsed.

content/handbook/solutions-architects/processes/activity-capture/sfdc-logging.md

+2 −2

Changes for content/handbook/solutions-architects/processes/activity-capture/sfdc-logging.md: 2 added lines, 2 removed lines.
Original line number	Diff line number	Diff line
		@@ -108,7 +108,7 @@ Example situations that should have a Yellow SA Feasibility Rating:
		- Significant timeline delays
		- Customer Success Plan missing critical information
		- Uncertainty from organizational changes at customer or prospect
		- Siloed engagement in 1-2 customer [personas](/handbook/solutions-architects/processes/activity-capture/activity-logging/#logging-an-activity) (Development, QA, Operations, Security, DevOps, Infrastructure)
		- Siloed engagement in 1-2 customer [personas](/handbook/solutions-architects/processes/activity-capture/activity-logging) (Development, QA, Operations, Security, DevOps, Infrastructure)
		- Identified but distracted technical champion
		- Executive identified but with limited engagement
		- Opportunities too early in the deal cycle to have enough information
		@@ -122,7 +122,7 @@ Example situations that should have a Green SA Feasibility Rating:
		- Significant customer engagement through tailored demos and hands-on workshops
		- Approved Proof of Value on track
		- Well documented Customer Success Plan
		- Alignment across customer [personas](/handbook/solutions-architects/processes/activity-capture/activity-logging/#logging-an-activity) (Development, QA, Operations, Security, DevOps, Infrastructure)
		- Alignment across customer [personas](/handbook/solutions-architects/processes/activity-capture/activity-logging) (Development, QA, Operations, Security, DevOps, Infrastructure)
		- Obvious and strongly engaged technical champion
		- Strong executive engagement
		- Strong engagement from cross-functional GitLab teams, like Product, Professional Services, and Field CTOs

Original line number	Diff line number	Diff line
		@@ -68,9 +68,9 @@ By capturing comprehensive data and leveraging AI, we are not just logging activ

		Capturing various types of data helps us build a comprehensive understanding of our activities and their impact. Below is a quick overview of the different data capture types, along with their status (Optional or Required) and links to detailed guides on how to perform each type of capture.

		### 1. Activity Based Logging (Rattle) [Required]
		### 1. Activity Based Logging (SA Activity Form) [Required]

		- Overview: Log activities such as meetings and calls using Rattle integrated with Slack and Salesforce.
		- Overview: Log activities such as meetings, calls, events, and partner work through the [GitLab SA Activity Form](https://sa-activity-e4fb10.gitlab.io/). This replaced Rattle as the single method for SA activity tracking on 2026-09-07.
		- Details: [Activity Based Logging Guide](/handbook/solutions-architects/processes/activity-capture/activity-logging)

		### 2. Email Logging (Gong) [Optional]
		@@ -97,5 +97,5 @@ Each type of data capture plays a crucial role in building a detailed and action

		## Feedback and Questions

		- Feedback: Create an issue in the Customer Success, Solutions Architecture Activity Capture project using the Feedback template.
		- Slack Channels: #rattle-users and #rattle-gitlab for discussions and questions.
		- Feedback: Create an issue in the Customer Success, Solutions Architecture Activity Capture project using the Feedback template. For the SA Activity Form specifically, use the [sa-activity project](https://gitlab.com/gitlab-com/customer-success/solutions-architecture/coe/requests/sa-activity).
		- Discussions and Questions: Open an issue in the [sa-activity project](https://gitlab.com/gitlab-com/customer-success/solutions-architecture/coe/requests/sa-activity) or bring questions to your team leader.