Skip to main content
School of Medicine IT

Plugins

Plugins are little programs that extend the functionality of our sites. They add features that are not included in WordPress by default, such as:

  • Forms
  • Page layouts and design components
  • Directories
  • Tables
  • Events

In the School of Medicine web system, many commonly used features are powered by plugins. When a plugin is enabled, its features become available for use on your site.

Most sites already have a small set of commonly used plugins enabled by default. Additional approved plugins can be enabled as needed. Our Web Guide documentation references plugins where applicable and explains how to use their features.

Important Guidelines

  • Only editors assigned the Administrator role can manage plugins.
    Other roles will not see the Plugins option in the dashboard.
  • Only enable plugins you truly need.
    Every active plugin adds complexity to your site and can impact performance, security, and long-term maintenance.
  • If you’re not using a plugin, leave it disabled.
    Disabled plugins do not affect your site and can be re-enabled later if needed.

How to Enable or Disable a Plugin

  1. From the Dashboard, select Plugins.
  2. You’ll see a list of available plugins on your site.
  3. To enable a plugin:
    1. Locate the plugin in the list.
    2. Click Activate below the plugin name.
  4. To disable a plugin:
    1. Locate the active plugin.
    2. Click Deactivate below the plugin name.

Changes take effect immediately.

Requesting New Plugins

For security, performance, accessibility, and long-term maintenance reasons, only a limited set of vetted plugins is available in the School of Medicine web system. These plugins have been reviewed and approved to ensure they meet University standards and can be supported over time.

Sites can enable/disable existing plugins but cannot install new plugins.

Contact the Web Team to request a new plugin. Plugin requests must demonstrate broad value across SOM sites. Plugins intended for a single-site or highly specialized use cases are typically not approved.