Permissions & Sharing
Plugins have three independent permission axes that control how others interact with your work.
Three Permission Axes
Section titled “Three Permission Axes”Edit — Who Can Modify
Section titled “Edit — Who Can Modify”| Setting | Who Can Edit |
|---|---|
| Just Me | Only you can modify the YAML, parameters, and settings |
| My Team | Your team members can also edit |
There is no “Public” edit option. If someone outside your team wants to modify your plugin, they must clone it first. This protects your work from unintended changes.
Use — Who Can Apply It
Section titled “Use — Who Can Apply It”| Setting | Who Can Add to Builds |
|---|---|
| Just Me | Only you can apply this plugin to scenarios |
| My Team | Your team members can also use it |
| Public | Anyone on the platform can use it (requires Trusted Builder) |
Clone — Who Can Fork It
Section titled “Clone — Who Can Fork It”| Setting | Who Can Clone |
|---|---|
| Just Me | Only you can clone to create new versions or plugins |
| My Team | Your team members can also clone |
| Public | Anyone can clone it to their own library (requires Trusted Builder) |
Trusted Builder
Section titled “Trusted Builder”Setting Use or Clone to Public requires Trusted Builder status. This ensures that publicly available plugins meet quality and trust standards. Contact your admin or info@roguelabs.io to request Trusted Builder access.
Ownership Buckets
Section titled “Ownership Buckets”When users browse plugins, they see them organized by ownership:
| Bucket | What It Contains |
|---|---|
| Mine | Plugins you created |
| Team | Plugins shared by your team members |
| Rogue Labs | Official plugins created by the Rogue Labs staff |
| Community | Public plugins from other users |
| Staff | Staff-created public plugins |