forcedotcom/sf-skills / skills/platform-policy-rule-generate
platform-policy-rule-generate
VerifiedTHE skill for creating a Data Cloud / Data Governance access policy — authors and deploys a PolicyRuleDefinitionSet + PolicyRuleDefinition pair (CRUD) covering OLS, FLS, RLS, masking/transform, and tag/classification-based access for the DATACLOUD or ALL consumer. TRIGGER when the user wants to create/write/author a Data Cloud or Data Governance policy, access policy, or policy rule, or to grant access to a Data Cloud object THROUGH A POLICY — a Data Cloud policy-create request routes here, not to the tag/classification surface. Resolves every reference via Data 360 MCP. SCOPE: Data Cloud policies only (not Security Center, DSAR, or User Access Policies). DO NOT TRIGGER to create tags/classifications, or to grant object/dataspace access via a PERMISSION SET / RBAC grant (use platform-dataspace-access-configure). For a vague object-access ask, surface both skills and ASK the permission-set way vs the policy way; if unsure the object is Data Cloud, ask which first.
references/templates-record.md
View on GitHub# RECORD Templates
These examples are distilled from retrieved policies. Use them to understand persisted structure, but generate only values published by the target release's MDAPI contract.
---
## RECORD — Basic RLS (record field = user attribute)
Source: `references/examples/PrincipalFieldMatchRLS/`
> **RLS MDAPI round-trip is fragile in real orgs.** Deploy/retrieve can fail with opaque gacks if a DMO field in `<valueDomain>` is not mapped in the org's data streams. Use read-only metadata inspection to verify the field mapping before generating XML; do not create or edit the rule in Policy Builder from this skill.
> `SCALAR_ATTRIBUTE` is a confirmed, deployable, Policy Builder-compatible principal path for record-field-to-principal-attribute comparisons, per DG UI source (this is how the builder itself authors the condition, not established by a per-shape round-trip). Use this template directly in normal author mode.
```xml
<?xml version="1.0" encoding="UTF-8"?>
<PolicyRuleDefinition xmlns="http://soap.sforce.com/2006/04/metadata">
<action>Read</action>
<category>RECORD_POLICY_RULE_DEFINITION</category>
<effect>Permit</effect>
<label>Rule 1</label>
<policyRuleDefinitionSetName>EXACT_SET_NAME</policyRuleDefinitionSetName>
<policyRuleResourceDomains>
<resourceDomain>EXACT_DMO</resourceDomain>
</policyRuleResourceDomains>
<principalAuthenticationLevel>INTERNAL</principalAuthenticationLevel>
<principalScopeType>ANY</principalScopeType>
<resourceScopeType>RECORD</resourceScopeType>
<ruleConsumer>DATACLOUD</ruleConsumer>
<transformPrecedence>0</transformPrecedence>
<whenPolicyRuleDefinitionClauseConjunction>
<conditions>
<clause>WHEN</clause>
<operator>EQUALS</operator>
<principalExpression>
<soqlTarget>
<select>EXACT_USER_FIELD</select>
</soqlTarget>
<type>SOQLTARGETLISTEXPR</type>
<version>1</version>
</principalExpression>
<resourcePath>RECORDFIELD</resourcePath>
<valueDomain>EXACT_DMO:EXACT_FIELD</valueDomain>
<valuePrincipalPath>SCALAR_ATTRIBUTE</valuePrincipalPath>
</conditions>
<conjunctionExpression>(AND 1)</conjunctionExpression>
</whenPolicyRuleDefinitionClauseConjunction>
</PolicyRuleDefinition>
```
## RECORD — RLS via PROJECTION Join
Source: `references/examples/ExistsJoinRLS/`
```xml
<conditions>
<clause>WHEN</clause>
<operator>EXISTS</operator>
<policyRuleDefinitionCondition>
<clause>WHEN</clause>
<operator>EQUALS</operator>
<policyRuleValueSet>
<valueText>${User.Email}</valueText>
</policyRuleValueSet>
<resourcePath>RECORDFIELD</resourcePath>
<valueDomain>RESOURCE_DMO:RESOURCE_FIELD</valueDomain>
</policyRuleDefinitionCondition>
<resourceExpression>
<projection>
<join>
<alias>JOIN_ALIAS</alias>
<predicate>
<attribute>JOIN_DMO:JOIN_FIELD</attribute>
<comparator>EQUALS</comparator>
<on>
<field>RESOURCE_FIELD</field>
<resourceAlias>resource</resourceAlias>
<schema>RESOURCE_DMO</schema>
</on>
</predicate>
<schema>JOIN_DMO</schema>
</join>
</projection>
<type>PROJECTION</type>
<version>1</version>
</resourceExpression>
<resourcePath>EXPRESSION</resourcePath>
<whereClauseConjunction>1</whereClauseConjunction>
</conditions>
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |