Yes. Visitors can connect an XWMS account to a shop so protected and user specific features can work on the website.
powered by xwms
Yes. The website can send the visitor into a dedicated XWMS connect flow to link the account with the shop.
Yes. The account icon can trigger a server backed connect flow instead of exposing a simple public link.
Yes. The connect flow is built around secure server side state and token based intent handling.
Yes. The admin includes a shop user resource where the shop owner can view linked shop accounts.
Yes. Certain actions such as protected downloads, forms, or bookings can require a connected shop account.
The website can direct the visitor into the XWMS account connection flow and then return the visitor back to the shop.
Yes. The connect flow supports return URLs so the visitor can continue from the same shop page after login or account connection.
Yes. The shop account flow uses a dedicated connect page with the same sign style layout as the main authentication experience.
Yes. The connect page supports the same eight language set used by the main sign interface.
Yes. A shop account is effectively the link between an XWMS user and a specific shop.
Yes. Shop user relationships are handled as account and business data, while website design data stays in the builder and snapshot layers.
Yes. Runtime templates can show account required states so visitors understand when login or connection is needed.
Yes. Templates can render buttons, chips, and action states that route visitors into the account connect flow.
Yes. File delivery can be restricted to connected shop users and handled through a controlled download flow.
Yes. A form can be placed behind a shop account requirement when that is needed for the workflow.
Yes. File access can be restricted to one or more users linked to that shop.
Live support
Start a conversation
You must be logged in to start a support ticket.
Log inWelcome back. Start a ticket or leave your question.
