generating-permission-set

Name: generating-permission-set
Availability: InStock
Author: cchrisv

Generate deploy-ready Salesforce PermissionSet XML with object, field, user, and app permissions.

Updated Apr 19, 2026

Search Tags:#deployment #security #metadata #xml #salesforce #fls #permission-set

Ready to run

npx skills add https://github.com/cchrisv/professorFlowVisualPicker --skill generating-permission-set

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: generating-permission-set
Source: https://github.com/cchrisv/professorFlowVisualPicker/tree/main/.agents/skills/generating-permission-set
Command: npx skills add https://github.com/cchrisv/professorFlowVisualPicker --skill generating-permission-set

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the creation and deployment of precise Salesforce permission-set metadata, reducing manual configuration errors and deployment time.

Core Features & Use Cases

Generate complete PermissionSet XML with object permissions, field permissions (FLS), user permissions, and app visibility.
Validate settings for licenses, record types, and tab visibility to ensure compliant deployments.
Use cases include creating new permission sets for teams, or updating existing metadata before releases.

Quick Start

Generate a deploy-ready PermissionSet XML by defining core properties, permissions, and visibility in your Salesforce org.

Frequently Asked Questions about generating-permission-set

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I generate a deploy-ready Salesforce permission set XML?▼

To generate a deploy-ready Salesforce permission set XML, define your core properties, object permissions, field-level security, user permissions, and app visibility. This produces valid metadata formatted safely for deployment via the Metadata API.

What should a Salesforce permission set include for field-level security?▼

A Salesforce permission set for field-level security must include field permissions defining read or edit access. It should also accurately represent object permissions, user permissions, and app visibility to ensure compliant metadata deployments.

How do I update existing Salesforce permission sets before a release?▼

To update existing Salesforce permission sets before a release, modify the metadata XML to adjust object permissions, field-level security, and app visibility. Validate settings for licenses, record types, and tab visibility to ensure deployment-safe configurations.

Does the Metadata API support deploying permission sets with custom app visibility?▼

Yes, the Metadata API supports deploying permission sets with custom app visibility. The generated XML accurately represents app visibility alongside object permissions and user permissions to ensure proper naming and valid metadata formatting.

What is the best way to automate Salesforce permission set creation for teams?▼

The best way to automate Salesforce permission set creation for teams is to generate a complete PermissionSet XML that validates settings for licenses, record types, and tab visibility, reducing manual configuration errors and deployment time.

Why do my Salesforce permission set deployments fail due to invalid metadata formatting?▼

Salesforce permission set deployments fail due to invalid metadata formatting when the XML lacks proper naming or accurate representation of object and field permissions. Enforcing deployment-safe configurations across environments prevents these errors.