Plugin Permissions

Plugin permissions control who can interact with your plugins and how. The system uses three independent permission axes and three access modes.

Permission Axes

Each plugin has three separate permission settings:

Permission	Options	What It Controls
Edit	Me, Team	Who can modify the plugin’s YAML, parameters, and settings
Use	Me, Team, Public	Who can add the plugin to their scenarios
Clone	Me, Team, Public	Who can clone the plugin to create their own copy

Edit permissions are limited to Me or Team — there is no public edit option. If you want others to build on your work, set clone permissions to public so they can create their own copy.

Access Modes

When you open a plugin, the system computes your access mode based on your permissions and subscription status:

Mode	What You Can Do
Full Edit	Edit YAML, manage parameters, upload vault files, launch test builds
Edit (No Build)	Edit YAML and manage parameters, but cannot upload vault files or launch builds. This applies when you have edit access but lack the Launch Builds permission or have an expired subscription.
Clone Only	View the plugin’s YAML and configuration in read-only mode. You can clone it to create your own editable copy.

Setting Permissions

Open the Sharing panel from the plugin editor toolbar to configure permissions. Each axis (edit, use, clone) can be set independently.

Visibility Rules

Me — Only you can perform the action
Team — Anyone on your team can perform the action
Public — Any Rogue Arena user can perform the action

Trusted Builder

To share plugins publicly with the broader Rogue Arena community, you need the Trusted Builder endorsement. This applies to both the Use and Clone permissions.

Apply from your user profile — no prior experience is required. A Rogue Labs staff member will review your application.

Without Trusted Builder status, you can still:

Create and edit your own plugins freely
Share plugins within your team
Clone public plugins from others