I4A SINGLE SIGN-ON
i4a Single Sign-On compatibility with REEID Translate
i4a Single Sign-On compatibility with REEID Translate is being evaluated from available plugin evidence. Provides bidirectional single sign-on between WordPress and i4a association management software, allowing users to authenticate with i4a credentials. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for i4a Single Sign-On.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
i4a Single Sign-On is documented in the Membership category with 6 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How i4a Single Sign-On compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
Plugin capabilities
- Provides bidirectional single sign-on between WordPress and i4a association management software, allowing users to authenticate with i4a credentials.
- Enables automatic login synchronization across sites sharing the same root domain via shared cookies, eliminating the need for separate logins.
- Restricts access to WordPress content based on imported i4a Member Types and Contact Types, which are mapped to custom WordPress user roles.
- Automatically creates WordPress user accounts upon first successful authentication without storing passwords in the WordPress database.
- Syncs user membership status (active, expired, or non-member) and associated roles from i4a to WordPress during each login event.
- Offers optional configuration to allow non-members and expired members to log in with a specific 'i4a: Non-member' role, distinct from subscriber privileges.
CONTENT BOUNDARY
i4a Single Sign-On capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
i4a Single Sign-On and REEID Translate FAQ.
What does i4a Single Sign-On do according to the available plugin evidence?
i4a Single Sign-On has 6 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for i4a Single Sign-On?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for i4a Single Sign-On?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate i4a Single Sign-On in a multilingual WordPress workflow.
REEID documents i4a Single Sign-On functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.