Learn · Permissions, hooks & security · CCAR-F

Plugins and enterprise governance

Package a team setup as a plugin, share it through a marketplace, and lock company policy in with managed settings users can't override.

Key ideas

• A plugin packages skills, agents, hooks and MCP servers as one unit, with a manifest at .claude-plugin/plugin.json.
• A marketplace is a repo with .claude-plugin/marketplace.json; install with /plugin install name@marketplace.
• Use a plugin to share one setup across many repos; use the project .claude/ folder for a single repo.
• Plugins run code with your privileges: review third-party plugins before installing.
• Managed settings override every other level and are delivered by file, MDM or server-managed settings.
• Lock-down keys include allowManagedPermissionRulesOnly, allowManagedHooksOnly, allowManagedMcpServersOnly and permissions.disableBypassPermissionsMode.
• Commercial data isn't used for training; OpenTelemetry (CLAUDE_CODE_ENABLE_TELEMETRY=1) gives usage and cost metrics.

Worked example: Company rules developers can't override

Put enforced rules (deny lists, disabled bypass mode, allowed MCP servers) in managed settings, and written policy in a managed CLAUDE.md. Project and user settings can add to them but can't loosen them.

Exam traps

• Putting company-wide must-follow rules in a project CLAUDE.md that any developer can edit.
• Copying .claude/ folders between many repos instead of shipping a plugin.
• Thinking a command-line flag can override a managed setting.
• Installing third-party plugins without review; they run with your user privileges.

Official docs

• Plugins
• Managed settings

Practise CCAR-F questions · Next lesson: The RAG pipeline