- \n
- Add and remove other participants<\/li>\n
- Delete messages<\/li>\n
- Assign moderators<\/li>\n
- Change the chat name and avatar.<\/li>\n<\/ul>\n
The owner<\/strong> is the chat creator who has all the rights of a moderator and can also:<\/p>\n
- \n
- Delete the chat for all participants<\/li>\n
- Transfer the owner role to a different user.<\/li>\n<\/ul>\n\n
\nA detailed guide on how to work with a group chat can be found in the client application documentation<\/a>.\n<\/p>\n<\/div>\n
The loss of owner rights can result in the loss of control over the group chat, especially if there are no other moderators in the chat.<\/p>\n
Causes of the problem<\/h2>\n
A group chat can lose its owner can occur due to two related factors:<\/p>\n
- \n
- Technical binding to TrueConf ID<\/a>
\nIn TrueConf Server, the chat owner is not just a role, but the user (an account on the video conferencing server) with the unique TrueConf ID. Even if the account is deleted from the system, chats remain linked to this ID.\n<\/li>\n- Organizational oversights
\nWhen a user account was deleted (e.g., in case of employment termination), there was no mandatory review of the group chats owned by this person and owner rights were not transferred to other chat participants.\n<\/li>\n<\/ul>\nWhy is the issue relevant for all types of accounts?<\/h2>\n
Regardless of whether TrueConf Server is run in Registry mode (internal database) or integrated with an LDAP corporate directory, the chat owner remains linked to TrueConf ID.<\/p>\n
- \n
- Registry<\/a>: deletion of a user account from the TrueConf Server database does not affect his\/her chats.<\/li>\n
- LDAP<\/a>: even when TrueConf Server is synchronized with directory services (MS Active Directory, OpenLDAP, etc.), chats remain linked to the TrueConf ID, not the LDAP login.<\/li>\n<\/ul>\n
Below we will show how to restore access to the management settings of a group chat.<\/p>\n
How to restore access to the chats of a deleted user<\/h2>\n
\n\nIf the LDAP<\/a> user data storage mode is activated, account recovery is performed on the side of the directory service. The problem-solving logic is the same for both Registry<\/strong> and LDAP<\/strong>.\n<\/p>\n<\/div>\n
The solution described here is also suitable for an address book working in Registry<\/a> mode. Take the following steps to restore access to the management settings of the chat owned by the person whose account was deleted.<\/p>\n
- \n
- In the TrueConf Server control panel, go to the Users<\/b> \u2192 User accounts<\/b> section and click the Add a user<\/b> button.<\/li>\n
- Enter the TrueConf ID<\/strong> of the user whose account was deleted and fill in the required fields.
\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2025\/05\/user_account2.png\" "\\"\\"")
<\/a><\/li>\n- Run any TrueConf client application and log in with the created account.<\/li>\n
- When you sign in, all user chats will be available to you. <\/li>\n
- Go to the group chat for which you need to restore access. Open the participant list by clicking the icon
![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2025\/05\/participants_button.png\" "\\"\\"")
.<\/li>\n- Right-click<\/b> to select the new chat owner and choose Appoint as owner<\/b>.
\n![\"\"](\"https:\/\/trueconf.com\/blog\/wp-content\/uploads\/2025\/05\/participants.png\" "\\"\\"")
<\/a><\/li>\n<\/ul>\nCongratulations, you have changed the owner of the group chat. At this point, you can delete the account of the previous group chat owner.<\/p>\n
\n\nTo prevent the loss of access to group chats, we recommend notifying users in advance<\/i><\/strong> about the need to transfer ownership rights to a different chat participant if their account is going to be deleted.\n<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
Users of a corporate TrueConf server may lose access to the management settings of a group chat. For example, they may be unable to assign new moderators or delete the chat for all participants. This problem can occur if the chat owner’s account is deleted, for example, if the employee no longer works in the […]<\/p>\n","protected":false},"author":75,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[260],"tags":[231,186],"class_list":["post-35423","post","type-post","status-publish","format-standard","hentry","category-knowledge-base","tag-troubleshooting","tag-administration","wpautop"],"_links":{"self":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/35423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/users\/75"}],"replies":[{"embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/comments?post=35423"}],"version-history":[{"count":7,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/35423\/revisions"}],"predecessor-version":[{"id":40737,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/posts\/35423\/revisions\/40737"}],"wp:attachment":[{"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/media?parent=35423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/categories?post=35423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/trueconf.com/blog\/wp-json\/wp\/v2\/tags?post=35423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
- Enter the TrueConf ID<\/strong> of the user whose account was deleted and fill in the required fields.
- LDAP<\/a>: even when TrueConf Server is synchronized with directory services (MS Active Directory, OpenLDAP, etc.), chats remain linked to the TrueConf ID, not the LDAP login.<\/li>\n<\/ul>\n
- Organizational oversights
- Technical binding to TrueConf ID<\/a>