<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Digadop</title>
    <link>https://digadop.ai/</link>
    <atom:link href="https://digadop.ai/rss.xml" rel="self" type="application/rss+xml" />
    <description>Notes from the Digadop team on AI-powered software for Salesforce teams.</description>
    <item>
      <title>Introducing Digadop: AI software for Salesforce teams</title>
      <link>https://digadop.ai/blog/2026-06-27-introducing-digadop/</link>
      <guid>https://digadop.ai/blog/2026-06-27-introducing-digadop/</guid>
      <pubDate>Sat, 27 Jun 2026 00:00:00 GMT</pubDate>
      <description>Digadop is a family of focused, AI-powered products that take the manual grind out of running a Salesforce org. Here is what we are building and why.</description>
      <category>Announcements</category>
      <category>digadop</category>
      <category>salesforce</category>
      <category>platform</category>
    </item>
    <item>
      <title>Who can see what in your Salesforce org? Start with access</title>
      <link>https://digadop.ai/blog/2026-06-27-start-with-access/</link>
      <guid>https://digadop.ai/blog/2026-06-27-start-with-access/</guid>
      <pubDate>Sat, 27 Jun 2026 00:00:00 GMT</pubDate>
      <description>Salesforce access is spread across profiles, permission sets, roles, groups, and sharing rules. Before you can secure it, you have to be able to see it.</description>
      <category>Salesforce security</category>
      <category>security</category>
      <category>access</category>
      <category>salesforce</category>
      <category>who sees what</category>
    </item>
    <item>
      <title>Why your Salesforce documentation is always out of date</title>
      <link>https://digadop.ai/blog/2026-06-27-why-salesforce-docs-go-stale/</link>
      <guid>https://digadop.ai/blog/2026-06-27-why-salesforce-docs-go-stale/</guid>
      <pubDate>Sat, 27 Jun 2026 00:00:00 GMT</pubDate>
      <description>Hand-written Salesforce docs drift the moment the build changes. The fix is to generate documentation from the configuration itself, continuously.</description>
      <category>Best practices</category>
      <category>documentation</category>
      <category>salesforce</category>
      <category>clionyx</category>
    </item>
  </channel>
</rss>
