Manage devices, seats and permissions

A connection is one person's account on one device connected to one store. A seat provides capacity for that connection. For example, the same store on two phones needs two connections; two independent stores on one phone also need two connections.

The store administrator controls what connected devices may do in the PrestaShop module. The account portal manages subscription capacity and assigned seats. These are different controls: buying capacity does not, by itself, grant editing permission in a store.

Connect a colleague

1. Ask the colleague to install PrestaOne and sign in with their own account on their phone. If you are providing the seat, allocate it to that exact account email using the steps below. Do not share your app sign-in code or your Back Office password.
2. In the store's module, open Connections & Access and generate a fresh pairing code while the colleague is ready to connect.
3. Have the colleague follow Connect your store. If the app reports that no seat is available, resolve the seat assignment or capacity first.
4. Reload Connections & Access. Identify the newly connected device and account before changing permissions.
5. Grant the editing areas and Live Chat access that this person needs. Save and wait for confirmation.

The connection list may group or label devices by account. Always check the actual device row: the current controls apply to that connection, not to an unrelated device with a similar name.

Provide a seat from your account

Your own devices take available seats automatically when you connect a store in the app. Allocate a seat is for letting another person use your capacity.

1. Sign in to the account portal as the account owner providing the seat, then open Seats.
2. In Allocate a seat, enter the colleague's PrestaOne account Email and the public Store URL they will manage. Use the email shown in their app Settings, including an Apple relay address if that is their account email.
3. Choose Allocate. Wait for the seat list to refresh and check the recipient, store and status. If capacity is full or allocation is paused, open Billing to review the reason before trying again.
4. The colleague can see the allocation under Seats provided to you in their account portal. They must still pair the store from their phone; allocation alone does not connect a device.
5. After pairing, check the device in the seat list and configure its store permissions in the module.

Allocate a separate seat for each device if the same person will connect to the same store from several phones. If your own account has no subscription or trial yet, the portal explains whether to connect your first store in the app or open Billing before allocating seats.

Choose viewing and editing access

Every active connection can view the store's orders, products, customers and statistics. The three editing permissions add write access; switching them off does not hide the corresponding data.

For a colleague who should only review the store, leave all three editing permissions off. This is viewing access to the business data, not a restriction to selected orders or selected customers.

After selecting permissions, choose Save and wait for Permissions updated. If the module says settings were saved locally but have not reached the app, reload and retry as directed. A local checkbox change alone is not confirmation that the phone's effective access has changed.

Ask the colleague to return to the store in the app and refresh. Verify the intended result: view-only data still opens, while editing controls are unavailable in the areas you disabled.

Choose who receives customer conversations

Enable Live Chat access only on the connections responsible for answering shoppers. Then configure the store's widget under Live Chat. Both parts matter: a widget enabled in the module can remain hidden when there is no eligible recipient.

Phone alerts have an additional layer. On each recipient's phone, review Settings → Notifications → Push notifications and the operating system's notification permission. The separate New messages choice controls PrestaShop customer-service alerts, rather than Live Chat recipient access. A person can have access to a conversation while their phone alerts are muted. Follow Set up Live Chat for a full test.

Add another store or replace a phone

To add an independent store, install the module in that store and use Settings → Manage connections → Add store. Check the active store before working: changes are made in the currently selected store, and store settings do not automatically apply to all connections.

To move to a new phone, sign in to the intended PrestaOne account on that phone and pair the store. With free capacity, this may create a separate connection. When the app offers Replace device access, check the old device and confirm only if it should lose that store's access.

Replacement concerns the connection shown in the prompt. Do not assume it transfers every store from the old phone. Check each required store after the move.

Disconnect or release an unneeded connection

There are three places to start, depending on what you control:

Select the intended connection and read its confirmation before disconnecting. Afterward, refresh the relevant list and confirm the final state. If a cleanup or retry message remains, follow that message rather than assuming that the operation has finished.

In the account portal, Release on an unused allocation returns it to available capacity without disconnecting a phone. On an occupied seat, Disconnect and release removes that device's store access, including when the store is offline. The person's other devices keep their own connections. Releasing a seat does not reduce your subscription quantity or bill; review Billing separately if you want to change purchased capacity.

Disconnecting does not delete core PrestaShop orders, products or customers. It also does not cancel your external subscription. Removing the last eligible chat recipient can hide the widget, and removing the connections that provide service access can pause chat or cart recovery. Review the module's Overview after changing access.

When the list does not match what you expected

Check the signed-in app account, the selected store and the device name first. In the account portal, verify that you are signed in to the account that owns the relevant seats. A colleague's assigned connection and the account paying for capacity need not be the same identity.

If the app still reports No free seats after a change, refresh the connection/seat status and resolve any pending operation. Send the exact status to support if the lists remain inconsistent; avoid disconnecting additional working devices just to experiment.