Plugin Management

PluginBoard provides a comprehensive system for managing your organization's design software plugins. As an administrator, you can create, deploy, update, and monitor plugins across multiple design applications from a central interface.

Understanding Plugin Visibility

Plugins in PluginBoard have two visibility statuses that determine which users can access them:

Status	Description	Use Case
Private	Available only to users within your organization's PluginBoard account	Internal tools, proprietary workflows, company-specific utilities
Public	Available to all PluginBoard users across all organizations	Open-source tools, broadly useful utilities, commercial plugins

info

To publish your plugin as public, please email contact@pluginboard.com with your request. Our team will review your plugin for quality and security before approving public distribution.

Creating a New Plugin

Follow these steps to add a new plugin to your PluginBoard account:

1. Navigate to the administration area by clicking Management in the top menu bar

2. Select the Plugins tab from the sidebar

3. Click the Create New Plugin button in the top-right corner

4. Select the host software that the plugin will run on

   • Important: The host software association cannot be changed after creation

5. Click the Confirm button

6. Complete the plugin details form:

   Field	Description	Requirements
   Plugin Name	The name displayed to users	Max 50 characters
   Plugin Icon	Visual identifier for your plugin	Recommended: 512x512px Max size: 2MB
   Description	Explains what the plugin does and how to use it	Supports Markdown formatting
   Visibility	Sets access level (Private/Public)	Default: Private
   Screenshots	Images showing the plugin in use	Up to 5 images Max 5MB each

7. Click Save to create the plugin record

Once your plugin is created, you'll need to add at least one version before it becomes available to users.

Managing Plugin Versions

PluginBoard uses semantic versioning to track plugin releases. Each version represents a specific build of your plugin with its own files, compatibility settings, and release notes.

Adding a New Version

To release a new version of your plugin to users:

1. Access the Management area from the top menu bar

2. Navigate to the Plugins tab in the sidebar menu

3. Find your plugin in the list and click the Versions button

4. Select Create New Version from the upper-right corner

5. Define your version parameters:

   Field	Description	Format/Requirements
   Version Number	Unique identifier following semantic versioning conventions	X.Y.Z format (e.g., 1.0.0, 2.1.3)
   Minimum Host Software Version	Earliest software version your plugin supports	Specific to each design platform
   Maximum Host Software Version	Latest software version your plugin supports	Specific to each design platform
   Release Date	When the version becomes available to users	YYYY-MM-DD
   Change Log	Documentation of updates, fixes, and new features	Supports Markdown for formatted text

6. Upload your plugin files:

   • Click the Select Local Plugin button
   • Choose your compiled plugin files or package
   • Review the included files by hovering over the plugin icon
   • Verify all dependencies and required components are included

7. Click Upload to publish the version

Plugin Structure Reference

Understanding the correct file structure for each design platform is crucial for successful plugin deployment. Below are the standard file structures for popular design applications supported by PluginBoard.

info

Why does PluginBoard only use AppData and not ProgramData?

• PluginBoard is designed to manage plugins on a per-user basis, ensuring that each user has their own plugin configuration and license management. This user-centric approach provides better security, personalization, and license compliance. Unlike system-wide installations (ProgramData), AppData storage allows PluginBoard to properly track individual user licenses and preferences.

AutoCAD Plugin Structure

Installation Path: %AppData%\Autodesk\ApplicationPlugins

AutoCAD plugins use a bundle structure with a mandatory PackageContents.xml manifest file:

%AppData%/
└── Autodesk/
    └── ApplicationPlugins/
        └── YourPlugin.bundle/
            ├── Contents/            # Contains your plugin implementation files
            │   ├── Resources/       # Images, icons and other resources
            │   └── Your.dll         # Main assembly and dependencies
            └── PackageContents.xml  # Required manifest defining plugin properties

tip

The PackageContents.xml file is essential for AutoCAD to recognize your plugin. Ensure it includes proper ApplicationPackage elements with compatible AutoCAD version ranges.

Blender Addon Structure

Installation Path: %AppData%\Blender Foundation\Blender\4.3\scripts\addons

Blender uses a Python-based addon system with specific metadata requirements:

%AppData%/
└── Blender Foundation/
   └── Blender/
      └── 4.3/                                # Specific Blender version
         └── scripts/
            └── addons/
               └── your_addon/                # Addon folder
                  ├── __init__.py             # Main entry point with bl_info dictionary
                  ├── blender_manifest.toml   # Additional metadata for Blender 4.0+
                  ├── operators.py            # Additional Python modules
                  └── resources/              # UI elements, presets, and assets

info

The bl_info dictionary in init.py is critical as it defines your addon's name, version compatibility, category, and other essential metadata that appears in Blender's addon manager.

SketchUp Extension Structure

Installation Path: %AppData%\SketchUp\SketchUp 2025\SketchUp\Plugins

SketchUp extensions are Ruby-based and follow this structure:

%AppData%/
└── SketchUp/
   └── SketchUp 2025/               # Specific SketchUp version
      └── SketchUp/
         └── Plugins/
            ├── your_extension.rb   # Main entry point (loader)
            └── your_extension/     # Extension folder (same name as RB file)

tip

Register your extension with SketchUp by using the SketchupExtension class in your main .rb file and properly setting the extension name, description, and version information.

Revit Plugin Structure

Installation Path: %AppData%\Autodesk\Revit\Addins\2025

Revit plugins require both an .addin manifest file and implementation assemblies:

%AppData%/
└── Autodesk/
   └── Revit/
      └── Addins/
         └── 2025/                  # Specific Revit version
            ├── YourPlugin.addin    # XML manifest file
            └── YourPlugin/         # Plugin folder (same name as addin file)

The .addin manifest file is an XML document that registers your plugin with Revit:

<?xml version="1.0" encoding="utf-8"?>
<RevitAddIns>
  <AddIn Type="Application"> <!-- or "Command" for simpler plugins -->
    <Name>Your Plugin Name</Name>
    <Assembly>YourPlugin\YourPlugin.dll</Assembly>
    <FullClassName>YourNamespace.EntryPoint</FullClassName>
    <ClientId>{unique-guid}</ClientId>
    <VendorId>YourCompanyName</VendorId>
    <VendorDescription>Brief company description</VendorDescription>
  </AddIn>
</RevitAddIns>

caution

Each Revit plugin must have a unique GUID in the ClientId field to prevent conflicts with other plugins. Generate a new UUID for each plugin you create.