Concurrent users
Your license sets how many people may use My Schedule project data at the same time. This page explains what counts as a connection, when one is taken and released, and what to do when the limit is reached.
The limit applies to My Schedule only. Projects that do not use My Schedule — an Auto MPS project, for example — are not affected by it.
What counts as one connection
A connection is one signed-in session that is opening My Schedule project data. In practice:
- One person signing in once uses one connection, no matter how many browser tabs or windows they open, or how many views they load. It is not one connection per request or per view.
- What decides this is where the browser keeps the sign-in, not how many windows are on screen. Ordinary tabs and windows of the same browser share one sign-in, so they share one connection. Anywhere that has to be signed into separately uses a connection of its own — a private or incognito window, a different browser, a separate browser profile, or another device. The same person, at the same desk, can therefore hold two connections by opening the site in a private window alongside their normal one.
- Simply being signed in does not use a connection. One is taken the first time the session opens project data.
- Requests that Asprova itself makes through the My Schedule plugin — uploading a plan, downloading results — do not use a connection.
The two limits
There are two separate allowances, and they do not draw on each other:
| Projects | Connections allowed |
|---|---|
| Free plan | 1 for the whole server, regardless of your license |
| Standard and Viewer plans | the number your license grants, shared between the two plans |
So a license granting five connections allows five people in standard- and viewer-plan projects in any mix, plus one person in free-plan projects.
When a connection is released
A connection is given back when:
- the user signs out — immediately;
- the user is removed from the server — immediately;
- the session has not opened project data for 15 minutes — automatically;
- the server is restarted — all connections are cleared.
Closing the browser without signing out does not release a connection straight away. It is released by the 15-minute inactivity rule instead, so a connection can stay counted for a short while after someone has stopped working. Asking people to sign out when they finish keeps the count accurate.
Private and incognito windows deserve particular care here. Closing one discards its sign-in without signing out, so the connection it took is held for the full 15 minutes — and reopening one starts another sign-in, and another connection, rather than returning to the first. Repeatedly opening the site in private windows can therefore use up the licensed connections with only one person working.
When the limit is reached
Someone opening project data beyond the limit is refused, and their browser reports that the maximum
number of concurrent users has been reached
(error:license:max-ccu-exceeded). Everyone already connected is unaffected —
existing users are never disconnected to make room for a new one. The next person is admitted as soon
as a connection is released.
If this happens more often than the number of people actually working suggests, the usual cause is sessions still inside the 15-minute inactivity window. If it happens consistently, the server needs a license granting more connections.
Checking current usage
Every signed-in user can see the current and maximum connection counts for the standard/viewer allowance in the user menu in the top-right corner of the screen.
For a longer view, enable usage logs. They record each connection accepted, each one refused at the limit, and each one released — by sign-out, by user removal, or by expiry — which is what you need to size a license against real use.