@MaxonL16591286

SADashboards is a portal rule the case-type wizard now scaffolds in 24.2 to support App Studio dashboard authoring and previews; it’s not an end-user portal and won’t be used unless you explicitly point an access group to it. In other words, it’s a harmless helper artifact similar to other dashboard/portal plumbing in Pega. You can safely ignore it, and it won’t impact runtime if your users launch Manager/User portals as usual. I don’t recommend deleting it, because future edits to the case or dashboards can recreate it or expect it to exist. If you really want it out of deployments, just exclude it from your Product rule (or keep it in a dev-only ruleset) instead of hard-deleting. Before removing anything, double-check references (Actions → View references) and confirm no access group maps to it. Net: keep it, don’t map it, and exclude from packaging if you prefer a clean PROD footprint. This behavior aligns with how Pega treats dashboards/portals and with 24.2 wizard changes that create “SA*” portal artifacts (for example, SAPortal noted in 24.2.1 fixes)