RedminePRO plugins: how configuration works

Updated 29 July 2026

Every RedminePRO workspace arrives with our features already installed. Installing, updating and migrating them is our job rather than yours. What you control, as a workspace administrator, is configuration: global settings, permissions, and per-project options.

The three places plugin configuration lives

Administration → Plugins. The global level. Each RedminePRO plugin appears here with a Configure link where its workspace-wide settings live: defaults, thresholds, feature toggles. You need administrator access to your workspace (which every RedminePRO plan includes).

Administration → Roles and permissions. Most plugins add their own permissions (for example manage_banner or manage_resources). Assign these to roles the same way as core Redmine permissions. A plugin's features stay invisible to users whose roles lack its permissions.

Project settings → Modules. Plugins that work per-project (banners, GitHub integration) appear as modules you enable per project, then configure from a new tab inside that project's settings. Global-level plugins (resource planning, attachment preview) don't need a module toggle.

What "admin access" means on RedminePRO

Your admin account has full Redmine administrator rights inside your workspace: users, roles, workflows, all plugin settings. Server-level concerns (installation, upgrades, backups, the database) are handled by RedminePRO as part of the service, so plugin guides in this knowledge base never ask you to touch a console or run a migration.

The plugin guides

More guides are added as new plugins ship to the platform. If something here doesn't match what you see in your workspace, contact support. Your workspace may be mid-rollout on a newer version.

← All Knowledge Base guides