Disclaimer: Swantide is a generative AI platform, therefore it may be inaccurate, incomplete, or not applicable. The output from Swantide is based on the inputs provided by the user, and any content generated by Swantide must be thoroughly reviewed and verified by you prior to use. Do not implement, rely on, or act on AI-generated output without first confirming its accuracy and suitability for your specific needs.
Scope
This document outlines the scope, features and functionality of the Swantide platform. This includes the Swantide AI Assistant, AI Documentation (also known as Data Dictionary), and AI Admin.
Swantide has access to Salesforce metadata only - we use the Metadata API and Tooling API to pull down metadata components from the Salesforce org connected to Swantide. This means that the following items are out of scope:
Anything outside of Salesforce
Anything in Salesforce but not on Core (e.g. legacy Marketing Cloud)
Record-level data in Salesforce
You can check the Salesforce Metadata Coverage report for more information on what is and isn’t Salesforce metadata, or use the Swantide data dictionary to find the metadata that you are looking for. See the table below for common metadata components and notes about how to approach them with Swantide:
Metadata Type | Notes |
CustomObject | Objects are Salesforce metadata; note that Salesforce uses the CustomObject metadata type to apply to both standard objects (e.g. Account) and custom objects. The object itself and its fields are Salesforce metadata; the records themselves are not.
You can use the Salesforce metadata to troubleshoot or understand specific things on records. For example, if you are trying to understand why certain records are not appearing in reports, Swantide can see things like the report filters and report types, and provide suggestions of potential things to troubleshoot, but it does not have access to the specific recordID in question. |
CustomField | Fields are also Salesforce metadata; note that Salesforce uses the CustomField metadata type to apply to both standard and custom fields |
Report | Reports are Salesforce metadata. You can see the report name, type, filters, as well as visible columns as Salesforce metadata. As mentioned above, you can use these things to troubleshoot why records are not showing up in certain reports, but the records themselves are not visible to Swantide |
Flow | Flows are Salesforce metadata. As part of the metadata Swantide can also see any call outs to sub-flows or apex classes |
Apex Class | Apex classes are Salesforce metadata; note that Swantide can see the same things that you can see in the org. This means that apex code that is protected as part of a managed package is not visible in Swantide |
Validation Rule | Validation rules are Salesforce metadata; you can see the name, error condition formula, and message. A common use case of the Swantide AI Assistant is inputting an error message generated by a validation rule and asking for guidance on how to avoid the error condition |
Profile | Profiles are Salesforce metadata, and can be used alongside permission sets to troubleshoot user related issues, as users are records and not Salesforce metadata (see below for more information); however, note that profiles in Salesforce store a huge amount of information, including access to all classes, layout assignments, objection permissions, and tab visibilities. Most profiles have thousands or tens of thousands of individual settings on them.
This makes it challenging to compare and contrast profiles holistically in a digestible way. Swantide is good at answering targeted questions (e.g. what permissions does Profile X have on object Y). Broader prompts (e.g. compare and contrast all profiles in this org) are more challenging to get a concise and useful answer. Be sure to use targeted prompts when asking about profiles and permission sets |
Permission Set | Permission sets are similar to profiles, in that they are Salesforce metadata and store a substantial amount of information (albeit less than profiles). Be sure to use targeted prompts when asking about profiles and permission sets |
Users | Users are not Salesforce metadata, they function as record-level data. If you need to troubleshoot why users are unable to do certain things in Salesforce, you can start by analyzing things that are metadata which are associated with users, such as profiles and permission sets |
Clouds Supported
Cloud | Supported? | Notes |
Marketing Cloud | Partial | Not compatible with Pardot (not on Core) |
Data Cloud | Yes | Compatible with all metadata |
Sales Cloud | Yes | Compatible with all metadata |
Commerce Cloud | Yes | Compatible with all metadata |
Experience Cloud | Yes | Compatible with all metadata |
IC, Automotive | Yes | Compatible with all metadata |
IC, Financial Services | Yes | Compatible with all metadata |
IC, Healthcare + Life Sciences | Yes | Compatible with all metadata |
IC | Yes | Compatible with all metadata |
Einstein | Yes | Compatible with all metadata |
Agentforce | Yes | Compatible with all metadata |
Mulesoft | No | Not on Core |