# Plugin Permissions

Plugin permissions describe what a plugin is allowed to access or do. OpenOnyx uses permission prompts so plugin capability is visible before a plugin becomes part of the workspace.

## Why permissions matter

Plugins run inside your knowledge environment. A useful plugin may need file access, network access, commands, settings, or custom views. A risky plugin may ask for more than its job requires.

## Review before enabling

Ask these questions:

- What problem does this plugin solve?
- Does it need access to the whole vault?
- Does it need the network?
- Does it modify files automatically?
- Does it store data in a portable format?
- Can I remove it without losing the notes?

## Test in a copy

Use a copied vault for plugins that rename files, create many files, rewrite links, import data, sync data, or run complex background work.

## Disable and remove

If a plugin misbehaves, disable it first. Then inspect files it created. Removing a plugin should not require deleting your notes, but plugin-specific data may remain in settings or plugin folders.

## Continue learning

- [Plugins](<Plugins.md>)
- [Obsidian Compatibility](<Obsidian Compatibility.md>)
- [Privacy](<Privacy.md>)