On this page
The pieces of a hosted workspace that are not a feature you switch on: which plan you are on, how many people that allows, and where the support link goes. There is nothing here to configure — it reports what your subscription already says and enforces the one limit that follows from it.
On RedminePRO Cloud
Availability
Every plan. It is part of every hosted workspace.
Turn it on
Nothing to turn on and nothing to install. It is present on every hosted workspace.
Permissions
None. The plan badge is shown to administrators only; the support link is shown to everyone.
Settings
None. Your plan comes from your subscription, not from a setting in the workspace — which is the point, since a limit you could edit would not be a limit.
Using it
Your plan is shown in the top menu when you are signed in as an administrator. If it reads as unavailable, the workspace has no plan signal — expected on a self-hosted install, and worth a support conversation on a hosted one.
Seats. Each plan allows a number of active accounts. Locked accounts do not count, and neither does the RedminePRO service account. When you are at the limit, creating or unlocking an account is refused with a message saying so — lock a leaver to free a seat, or move up a plan.
The limit counts active accounts, so the way to make room is to lock people who have left rather than to delete them. Locking is reversible and keeps their history intact.
Where a feature shows a seat count — the Users area does, when it is installed
— that display is informational. The limit itself is enforced here, so there is
one place that decides and one answer.
The support link in the top menu goes to RedminePRO support. It is the right first stop for anything about the workspace itself rather than about your projects.
Plans and what they change
Your plan sets the seat allowance, and a few features read it:
- MCP requires Business or above.
- Audit Trail and Zaira AI cap how far back their records are kept, by plan.
Everything else behaves the same on every plan.
Troubleshooting
The plan is shown as unavailable. There is no plan signal. On a hosted workspace that is worth reporting to support; on your own server it is normal and means no limits apply.
An account cannot be created or unlocked. You are at your plan's seat limit. Lock an account that has left to free a seat, or move up a plan. Deleting is not required and not recommended — locking is reversible and keeps history.
A seat count disagrees with what you expected. Only active accounts count. Locked accounts and the service account do not.
A feature says it needs a higher plan. MCP is the one that gates outright. Audit Trail and Zaira AI do not refuse — they shorten how long their records are kept.