Why might a client be unable to deactivate a custom role?

A client might be unable to deactivate a custom role if there are still users assigned to that role. Each custom role is designed to manage permissions and access for users within a system or organization. If any users are currently assigned to that role, a deactivation cannot occur because it would create a situation where those users would lose their assigned permissions or access, which the system is likely set up to prevent.

In many systems involving custom roles, ensuring that every active role has assigned users helps maintain operational integrity and user permissions. This is why the option highlighting the presence of active users linked to the role is key to understanding why deactivation is restricted.

The other options may reflect various scenarios but do not directly address the specific condition that prevents deactivation due to user assignments. For example, exceeding the number of custom roles allowed could limit the creation of additional roles but does not affect the ability to deactivate an existing one. Similarly, if a role is linked to a payment method or is active for a project, those issues would typically prevent the creation of new roles or modifications to current rights but are less likely to hinder a role’s deactivation unless they affect user assignments directly.