Read-only demo account

For merchants

When you hand a demo shop to a prospect, you want them to click through every screen of the Administration without being able to break anything. The plugin creates exactly that login.

Create it

bin/console kmh:demo-data:user                        # create the account, print the password once
bin/console kmh:demo-data:user --show                 # show what exists, change nothing
bin/console kmh:demo-data:user --rotate-password      # set a new password
bin/console kmh:demo-data:user --email x --username y # use your own login name and email
bin/console kmh:demo-data:user --password '…'         # use a chosen password instead of a generated one

Or from Settings → Extensions → Demo data, with the Manage user permission.

The password is generated, shown once and stored only as a hash. There is no way to read it back — use --rotate-password if it is lost.

What the account can do

• It is an ordinary user with one role that holds every read permission in the installation (including other plugins' entities), plus the viewer permissions the Administration needs to draw its screens.
• It has no create, update or delete permissions, and it is not flagged as an administrator (administrators bypass permissions entirely).

What it cannot see

Four areas stay closed however broad the role is, because reading them would reveal the shop's credentials:

• system configuration (every plugin's settings, including payment secret keys),
• integrations,
• user access keys,
• password-recovery records.

Additional permissions such as clearing caches, managing plugins or system settings are not granted either.

Side effects to expect

The Administration saves per-user interface preferences (grid columns, favourites). For this account those saves are denied like any other write, so an occasional error notification may appear. That is the price of a role with no write access at all.

Safety

A login the plugin did not create is never modified. Pointing the command at an existing account reports a conflict instead of resetting that person's password.