Write a comment...
0/9000
Featured group
Design Trailblazers
Write a comment...
0/9000
5 answers
Salesforce UX Designers should have these two certifications minimum depending on their level and responsibilities: https://trailhead.salesforce.com/en/credentials/designeroverview/
If they are in production delivery they will need additional Consultant and Developer certifications depending on what they are designing for (ie. Admin, Platform App Builder, Business Analyst, Sales Consultant, Agentforce Specialist)
We have noticed that some text in emails and comments section of cases are hard to read when the text there is black or gray. Users have to switch to light mode to read that.
9 answers
Hi @Jeremy York, I'm the PM for Dark Mode & SLDS 2. You are correct Dark Mode is currently in beta, so thank you for reporting this bug. I was able to reproduce this issue in a test org on the chatter feed, so I will get this triaged in our backlog to fix. Let me know if you have encountered any other Dark Mode issues!
Hey, builders 👋
If you're building Salesforce experiences with AI tools like AF Vibes, Cursor, or Claude, the new 👉
SLDS 2 AI Starter Kit is the best place to start.
The kit gives AI the context it needs to generate SLDS 2-compatible components every time you build, alongside a local preview environment to verify the build in light and dark mode - no org required.
Check it out and share your thoughts!
Could this accelerate how you build with SLDS 2 and AI?
CC:
5 comments
Thanks for sharing, Shannon! This looks like a great way to streamline component development. I'm definitely going to test how this integrates with my current workflow and share my thoughts here.
Dear all,
Are you able to share any expected final release date for dark mode? My Org won't allow using it since it is in Beta.
2 answers
There is no final date announced yet. It can be enabled in your org bet version. What issue are you facing?
https://www.salesforce.com/blog/salesforce-dark-mode/
Hi everyone,
We are working with Salesforce Agentforce Employee Agent, and we need to store the conversations that users have with the agent for auditing and analytics purposes.
Our goal is to save:
- user questions
- agent responses
We would like to know if there is any standard or recommended Salesforce configuration to store the full conversation between the user and the Employee Agent, so we can later perform analysis on those conversation records.
We are especially interested in understanding:
- whether Agentforce already provides built-in conversation persistence
- recommended architectures or best practices
- if teams typically use custom objects, Platform Events, Data Cloud, Apex, Flows, or another approach
- and how other organizations are handling conversation logging in production environments
Has anyone implemented this successfully or can share the recommended pattern? @* Customer Success * @* Known Issues * @* Salesforce Administrators * @Salesforce Flow Automation @* Salesforce Developers * @Design Trailblazers @Slack + Agentforce
3 answers
Hi, Keep in mind that Event logs store information for seven days and consumes Data 360 credits. Enable it with below steps:
- From Setup, in the Quick Find box, enter and then select Agentforce Agents.
- Select your agent.
- Click the edit icon next to Keep a record of conversations with enhanced event logs to review agent behavior.
- Select Keep a record of conversations with enhanced event logs to review agent behavior.
- Save your changes.
I'm getting an error when trying to send an email from a Case using a Chatter component.
What’s curious is that even if I use files with different names, I still get the same error.
The error message is:
Has anyone experienced this before or knows what could be causing it?@* Customer Success * @* Salesforce Administrators * @* Known Issues * @* Salesforce Developers * @Design Trailblazers
1 answer
Smitha Thomas (CIBC) 
Forum Ambassador
In Salesforce, each file share to a user, group, or record counts toward a limit, with a default maximum of 2,000 shares per file. If your current limit is below 2,000, Salesforce Support can restore it to the default without additional review. Check this help article for more info -
Increase the Maximum File Shares Limit in Salesforce File
Hi Trailblazers! The design systems team is recruiting a limited cohort for two upcoming SLDS 2 pilots and want you involved! The two pilots are:
- Permission-Based Theme Activation (May '26) - Run SLDS 2 alongside your existing theme for a subset of users. Phase your rollout by business group, validate with a pilot audience, and migrate at your own pace — with zero disruption to the rest of your org.
- SLDS 2 Theme Builder (June '26) - Style your org globally with clicks, not code. Set brand colors, typography, and spacing directly in Setup → Themes & Branding. Accessibility guardrails are built in, and your theme stays compatible as Lightning evolves.
Pilot participants get direct access to the SLDS 2 product team and early configuration support. To join the pilot:
- Fill out the interest surveys:
- Contact your Account Executive about your interest in the pilot
Spots are limited so please enroll by May 22nd!
Hi, When converting a Lead into a Contact, the Contact was assigned the “Student” record type, but it should not have happened that way.
The expected behavior is for the Contact to be created with the “Applicant” record type.
Where can I configure the default record type for Contact during Lead conversion, without modifying the standard conversion component, since the conversion is being done through the standard Salesforce process?
The curious part is that this only happens in the UAT environment.
In Production, when converting the Lead using the standard Salesforce conversion process, and without explicitly selecting a specific record type, the Contact is correctly created with the “Applicant” record type.
However, I cannot find where this behavior is defined at the configuration level, and I would like to understand what setting controls this default assignment.
2 answers
Simply navigate to the user's Profile in the UAT environment, go to the Contact Object Settings, and change their Default Record Type from 'Student' back to 'Applicant'."