
USER ROLE EDITOR
User Role Editor translation compatibility with REEID Translate — evidence review.
Official plugin evidence describes what User Role Editor does, but does not yet establish specific visitor-facing content values that REEID should translate.
AWAITING VERIFICATION
Translation scope is not yet established.
Plugin capabilities can be documented without treating structure, behavior, configuration or feature availability as translatable content.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
TRANSLATION SCOPE
No specific visitor-facing content values are currently approved for translation scope.
PLUGIN EVIDENCE
Plugin capabilities and distinctive features are documented separately from REEID translation support.
PRACTICAL WORKFLOW
Translation workflow
01 · Review official plugin evidence
Document factual capabilities, content models and relevant plugin behavior from the available evidence.
02 · Identify concrete visitor-facing values
Look for explicit labels, titles, descriptions, messages, placeholders or other human-readable content values.
03 · Approve translation scope
Only evidence-backed visitor-facing values become supported translation scope for the integration record.
04 · Test confirmed integration behavior
Validate approved content and plugin behavior before publishing compatibility claims.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Edits WordPress user roles and capabilities.
- Adds new roles and customizes role capabilities.
- Deletes custom roles when they are no longer assigned to users.
- Changes the default role assigned to newly created users.
- Assigns capabilities on a per-user basis and allows multiple roles per user.
- Adds and removes capabilities, including capabilities left behind by uninstalled plugins.
- Supports WordPress multisite.
Distinctive features
Role and capability management is the core differentiator. The plugin supports custom roles, per-user capability assignment, multiple roles per user, cleanup of unused custom roles, and capability changes tied to plugin removal leftovers.
Dynamic content
The supplied evidence describes role and capability changes at runtime, including per-user capability assignment and default role changes for newly created users. Broader dynamic content behavior is not established.
SEO and metadata
No SEO or metadata behavior is established in the supplied evidence.
URLs and navigation
No URL or navigation behavior is established in the supplied evidence.
Forms and commerce
No forms or commerce behavior is established in the supplied evidence.
CONTENT BOUNDARY
Keep plugin capabilities separate from translation scope.
Current evidence documents what User Role Editor does, but no specific visitor-facing content values have been approved as translation scope.
Structure, configuration, logic, integrations and runtime behavior are not translation claims.
LIMITATIONS & QA
Verification notes
- Official evidence does not establish security features such as access controls, firewalls, login protection, scanning, or content filtering. Behavior is documented around roles, capabilities, and multisite support rather than broader security functions.
COMMON QUESTIONS
User Role Editor and REEID Translate FAQ.
Does the current evidence establish translation scope for User Role Editor?
No specific visitor-facing content values are currently approved as translation scope for this integration.
What does the plugin intelligence section describe?
It summarizes factual plugin capabilities and distinctive features separately from REEID translation-support claims.
What is required before translation scope is published?
Concrete visitor-facing content values must be supported by evidence, approved for the integration record and tested as appropriate.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Explore REEID Translate for multilingual WordPress workflows.
REEID separates factual plugin intelligence from evidence-backed translation scope.
No specific visitor-facing content values are currently approved for this integration.