Help center support eXpress
We've collected answers to popular questions to make eXpress easy and convenient to use. Didn't find the answer to your question? Contact our support team.
- Welcome to eXpress
- eXpress Support
- Introducing eXpress & Glossary
- Installation & Updates & Requirements
- Registering & Logging In
- User Profile
- Chats, Channels & Threads
- Contacts
- Tags & Tabs
- Files
- Calls & Conferences
- Push Notifications & Counters
- Fixing Background Work on Mobile
- Bots & SmartApps
- Diagnostics, Logs, and Cache
- Admin Panel
- Admin Panel: General Information
- Users
- Chats
- Open Chats
- Calls
- Conferences
- Profile Change Request List
- Logout List
- Administrators
- Servers
- Bots
- Internal Bots
- External Clients Users
- UI Alerts
- Containers
- Audit
- Stickers
- Call Backgrounds
- Catalog
- Statistics
- Role Model
- Role Model Rules
- User Groups
- Call Reports
- Call Recordings
- Transcribings
- SMS Statuses
- Administrators Authentication
- Audit Settings
- Global Chat
- Global Bots
- Links to Chats/Calls
- Push Service
- File Service
- User Session
- Registration Settings
- Active Directory
- E-mail: self-registration
- OpenID
- Personal Data Visibility
- E-mail: sending emails
- Getting Started Instruction
- Blocked Users
- VoEx
- Server
- Support Info
- Security (CTS)
- Registration Instruction
- SmartApps
- Mobile Menu Configuration
- Activations
- SMS
- Adapters
- Masks
- Security
- CAPTCHA
- Reserved Phone Numbers
- Suggests
- Kerberos Settings & Kerberos Suggests
Logout List
- Logout Reasons
- Accepting Logout Request
- Bulk Processing of Logout Requests
- Automatic Logout Request Confirmation
- Deleting an Account After Logout
This section displays a list of users for whom a logout request has been sent:
- by the user;
- via the corporate server administrator;
- due to an event in the corporate directory.
Here, you can view user information, check the logout reason, and Accept or Reject the request.
Why Aren't Logout Control Buttons Working?
The Accept and Reject buttons work only if the admin panel is opened via the server FQDN.
Logout Reasons
| Reason | Description |
|---|---|
user_request |
The user sent a logout request: they clicked Leave the server in their profile on one of their devices. On other devices, they will continue working as usual. Clarify the reason from the user. If the request was sent by mistake, the user can log in again with the same credentials. Then the logout request will disappear automatically after the admin page is refreshed. You can also reject the request manually. |
pwd_last_set_changed |
Logout due to a password change in AD. All user sessions are terminated. The “Incorrect Login or Password” error will occur when trying to sign back in using AD credentials. When the user logs in with a new password, the logout request will disappear automatically after refreshing the admin page. If there are problems signing in, click the Clear cache button in the user profile in the admin panel. |
account_disabled |
The account was disabled in AD. All user sessions are terminated. The “Incorrect Login or Password” error will occur when trying to sign back in using AD credentials. When the account is enabled and the user logs in to the server again, the logout request will disappear automatically after refreshing the admin page. |
account_deleted |
The user deleted the account. Deletion cannot be canceled, even if you withdraw the logout request with this reason. To release the corporate account from being linked to the deleted account, confirm the request or enable auto-confirmation for this type of request. For details about auto-confirmation, contact eXpress support. |
lockout |
The user is blocked in AD. All user sessions are terminated. The “Incorrect Login or Password” error will occur when trying to sign back in using AD credentials. When the user is unblocked and logs in to the server again, the logout request will disappear automatically after the admin page is refreshed. |
password_expired |
The password expired in AD. All user sessions are terminated. The “Incorrect Login or Password” error will occur when trying to sign back in using AD credentials. When the user logs in with a new password, the logout request will disappear automatically after refreshing the admin page. If there are problems signing in, click the Clear cache button in the user profile in the admin panel. |
account_expired |
The account expired in AD. All user sessions are terminated. The “Incorrect Login or Password” error will occur when trying to sign back in using AD credentials. When the expiration date is extended or a new account is created and the user logs in to the server again, the logout request disappears automatically after the admin page is refreshed. |
admin_request |
A logout request from an administrator. When this request is submitted, user sessions will not be ended. |
excluded_from_search_filter |
In the Active Directory/OpenID section, the Logout request on exclusion from AD sync selection or Logout request on exclusion from OpenID sync selection checkbox is selected, and the user is excluded from the selection. For example, the user was removed from the AD synchronization group or their OpenID token is inactive. All user sessions are terminated. The user can sign in again, but the sessions will end again during the next synchronization. This will continue until an AD group is added or the token is reactivated. The user will need to log in to the server from scratch. |
user_account_disabled |
The account is disabled in AD LDS: its msDS-UserAccountDisabled attribute is equal to TRUE. The request is created if in the Active Directory section, the User Account Disabled (AD LDS) checkbox is selected. |
openid_user_disabled |
Account is blocked in OpenID. The request is created if the Logout request when user is blocked check box is selected in the OpenID section. |
openid_missing_required_role |
The user does not have the role specified in the OpenID required role field. A request is created if the Logout request due to missing OpenID role check box is selected in the OpenID section. |
user_deleted_in_openid_provider |
The user was removed in the OpenID provider. This is a system reason: its checkbox in the OpenID section cannot be disabled. |
Why Didn't the Logout Request Disappear After Unblocking in AD?
The logout request disappears in two cases: the server administrator accepted or rejected it, or the user logged in to the app. Synchronization with AD does not remove the request.
If an AD account was enabled, unblocked, or had its role restored, ask the user to log in to the app. The request will disappear after refreshing the administrator page. If the user cannot log in yet, click Reject.
Accepting Logout Request
After clicking Accept, the user's corporate account is detached from the personal account and changes to the unregistered status.
Bulk Processing of Logout Requests
Starting with server software version 3.27, you can select several logout requests using checkboxes. To select all entries with the top checkbox in the first column, first specify the logout reason in the filter. Without a filter, bulk selection is unavailable, and records will have to be marked manually.
Automatic Logout Request Confirmation
Logout requests can be confirmed automatically (since version 3.47). For more details, see the authentication methods description: Active Directory | OpenID.
Deleting an Account After Logout
After logout, the account remains in the list in the “Users” section. The deletion method depends on the account type:
| Account Source | Deletion |
|---|---|
| Manually created in the admin panel | Deleted via the trash icon in the Users list. |
| Synchronized from the AD corporate directory | Disappears after deleting the synchronization group in Active Directory. |
| Synchronized from OpenID | In server software versions before 3.40, deletion is not possible. In versions after 3.40, deletion is possible if the Delete user profiles when logout is confirmed checkbox is selected in OpenID synchronization settings. |