Active Sessions
The Active sessions page lists the users who are signed in to Weissr right now, and lets you end a user's session. It is managed in Administration → Security → Active sessions and covers the whole environment. This guide is for administrators who are responsible for access to their Weissr environment.
Before you start
You need the Administrator or Superuser permission, which grants access to the Administration page.
📌 Note: Ending a session signs the user out. It does not disable, lock or delete their account, and they can sign in again straight away.
What the page shows
The page lists every user with a session open at the moment you loaded the page.
Column | What it shows |
|---|---|
ID | The user's ID in Weissr. This is the user ID, not a session ID. |
Username | The username the person signs in with. |
Full name | First name and surname. Hover over it to see the ID and username together. |
Expire | A button that ends that user's session. |
Users are listed by full name. One row means one user, however many browser tabs or devices they have open, so ending a session from here ends all of that user's sessions at once.
💡 Tip: The list is a snapshot taken when the page loads, and it does not refresh by itself. Reload the page to see who is signed in now.
The page does not show when someone signed in, when they were last active, which device or browser they used, or which address they connected from.
Ending a user's session
Go to Administration → Security → Active sessions.
Find the user in the list.
Click Expire on their row.
Confirm in the dialog that appears.
📌 Note: The confirmation dialog is titled Delete user session and its confirm button is labelled Delete. Nothing is deleted. The user's session ends and their account is untouched.
What the user experiences
Ending a session is not instant, and the user is not warned.
Nothing changes on their screen at the moment you click. Their session ends the next time their browser contacts Weissr, which happens as soon as they click anything.
At that point they are returned to the sign-in page. If they have a page open that keeps a live connection, they see the message Session expired. Refresh page to log in.
Anything they had not saved is lost. There is no warning and no draft is kept.
⚠️ Warning: Check with the person first where you can, particularly if they may be part-way through editing a request. Ending a session discards unsaved work without asking.
They can sign in again immediately. If you need to stop someone getting back in, disable their user account instead.
Users who sign in through SSO
Users who sign in through an identity provider such as Entra ID appear in this list like anyone else, and Expire works on them.
What it ends is their Weissr session. It does not sign them out of your identity provider.
📌 Note: An SSO user whose session you end is usually signed straight back in when they return to Weissr, because their identity provider still considers them signed in and does not ask for a password again. To remove an SSO user's access properly, revoke it in your identity provider, or disable their Weissr user account.
👉 Learn more about SSO configuration
When sessions end on their own
You do not have to end most sessions by hand. A session also ends in these cases:
Inactivity. A session that goes unused for a set period ends automatically. The exact period is set for your environment, and thirty minutes is typical. Any activity resets it.
Signing in somewhere else. Your environment limits how many sessions one user can have at once. When someone signs in past that limit, the new sign-in succeeds and their oldest session ends. In an environment with a limit of one, this means signing in on a second device signs the person out on the first.
A Weissr server restart. Sessions are held in server memory, so a restart or an upgrade signs everyone out.
In all three cases the user sees the same thing described above: they land back on the sign-in page, and anything unsaved is lost.
💡 Tip: Users who report being signed out "for no reason" while working on a second device are usually hitting the concurrent-session limit, not a fault.
Troubleshooting
Symptom | Likely cause | What to do |
|---|---|---|
A user who is working right now is not in the list | The list is a snapshot from page load | Reload the page |
A user is still in the list after you expired them | The list had not been reloaded, or they have signed in again since | Reload the page, and check whether they signed back in |
An SSO user is signed back in seconds after you expired them | Their identity provider still considers them signed in and does not prompt again | Revoke access in your identity provider, or disable the Weissr user account |
A user reports being signed out while working on another device | Their environment's concurrent-session limit was reached, so the older session ended | Expected behaviour. Ask them to work in one place at a time |
A user lost unsaved work after being expired | Sessions end without warning and nothing is kept | Nothing can be recovered. Warn people before ending their session where you can |
The page shows column headings and no rows | Nobody is signed in at the moment, other than possibly yourself | No action needed |