This article is also available in:

Access New Render - What are the changes?

To optimize rendering performance for Poool Access SDK elements, our team has developed a new rendering engine: "NEXT".

The primary goal is to integrate server-side rendering to improve the overall display performance of Access walls and their related features.

This new architecture creates a scalable technical base shared across all our products (Access and Engage), facilitating the deployment of future features.

This change only applies to Access, as element rendering in Engage already uses this new version.

Is it necessary to switch to the new rendering mode?

The NEXT rendering engine allows you to take full advantage of the latest features developed for Poool Access (e.g., dark mode). We encourage you to gradually transition to the new rendering mode whenever possible.

However, please note that this change is not mandatory; the older LEGACY version remains fully functional.

How to switch to the NEXT rendering mode

The rendering mode can be selected in your SDK settings. By default, the configuration is set to "Legacy". You simply need to select "Next" to benefit from the new rendering engine.

Important Note: This change affects the structure of advanced Access appearances that contain custom CSS. Before switching to Next mode, you should verify that your appearance designs still display correctly with the Next rendering.

Here are the steps to follow:

Go to the 'Appearances' section > 'Preview' > Rendering engine > Select "Next" to preview the final appearance with the new rendering mode.

Once you have confirmed that all your appearances look correct, you can enable the "Next" rendering mode in the "Settings" section > SDK Settings.

When making this configuration change, be sure to double-check the active elements on your site, as well as the templates you use for your wall variations.

Congratulations, you are now using the optimized version of Poool Access walls! 🎉
This change will apply to all appearances in your Dashboard and any future ones you create.

Fixing Access Appearances

What if the rendering is incorrect with the new version?

Because certain style elements were modified to be compatible with Next rendering, some CSS settings in your appearances may need to be adjusted.
Here are the elements that may require rewriting:

Default font: The font must be applied to the body .p3-app class.
Deprecation: The .p3-element classes no longer exist.
Margins: Margin adjustments may be necessary.

Please don't hesitate to reach out to us if you encounter any difficulties making these corrections.

When you are ready to switch to the new render mode, feel free to contact our support team to assist you with this transition.

Updated on: 05/10/2026

Was this article helpful?

Thank you!