Skip to content

Salesforce Support Login Access

VIDEO TRANSCRIPT | Recorded: 2025-09-23 | Verify against current system state

Abstract

Continuation of Salesforce support training covering how to grant login access to Salesforce support team for troubleshooting. Also includes discussion of AI coding tools (Claude Code integration with VS Code for documentation and code review vs ChatGPT limitations), Aplus5 managed services partnership for ongoing Salesforce support, and challenges with BitBucket repository access during I2C transition including continuous integration conflicts.

Key Procedures

  • Log into target environment (staging/production)
  • Go to Setup > Security > Login Access Policies (enable if needed)
  • Navigate to User Settings > Grant Account Login Access
  • Set access duration (e.g., 7 days) for Salesforce.com Support
  • Can also grant access to Chargent Support, Plow/Ploty if needed
  • Respond to support chat confirming access granted
  • For AI code review: use Claude Code in VS Code with repository context
  • For repository changes: submit pull requests through BitBucket

Notable Statements

  • 0:03:20 "How long do I want Salesforce support to have access I'm going to say a week."
  • 0:05:45 "Think of it like connecting to the Aptify support. It's not that much different."
  • 0:06:24 "Claude code connects to visual studio. And it can read your code."
  • 0:06:50 "I rarely let it update my code... but I do let it review the code."
  • 0:07:22 "I can push in all of the information I have in our SF docs site. So it understands our Salesforce environment."
  • 0:10:31 "If I was leaning on someone for Salesforce support, it would be Aplus5."
  • 0:11:14 "I2C does not really want them in their repository."
  • 0:12:06 "Every time I submit a pull request, there's some kind of conflict."

Systems & Configurations

Systems Mentioned

  • Salesforce (Login Access, Support)
  • BitBucket (repository management)
  • Claude Code (AI coding assistant)
  • ChatGPT (comparison)
  • VS Code (IDE integration)
  • Aplus5 (managed services partner)

Specific Configurations

Item Value/Setting Timestamp Notes
Login Access Duration 7 days 0:03:25 For Salesforce support
Support Options Salesforce.com, Chargent, Plow 0:03:54 Available vendors
Claude Code VS Code integration 0:06:32 With SF docs context
Aplus5 Status Through 2025 0:14:00 At minimum
I2C Exit March-April 2026 0:12:42 Expected timeline

Credentials/Access Mentioned

  • User Settings access for login grants
  • BitBucket repository (pending access for Aplus5)
  • Claude Code subscription

Errors & Troubleshooting

  • Issue: Pull request conflicts with I2C changes
  • Cause: Multiple developers, frequent updates
  • Resolution: Go through I2C conflict resolution process

  • Timestamp: 0:12:06

  • Issue: Aplus5 changes overwritten by deployments

  • Cause: No BitBucket repo access, changes made directly in staging
  • Resolution: Submit all changes through Jeff until repo handoff
  • Timestamp: 0:11:08

Transcript Gaps & Quality Notes

  • Continuation from part 1 of support training
  • Informal discussion about AI tools and development workflow
  • Important context about Aplus5 managed services relationship
  • Repository management concerns for post-I2C transition
  • Claude Code recommended for documentation and flow analysis