Element displays Matrix rooms available to the signed-in account. Direct conversations also use rooms even though Element places them under People. A room records membership and messages. Its access rules determine who can enter or read earlier events.
Each login creates a Matrix device entry with its own encryption state. In this context, a device means a session rather than one physical phone or computer. Signing in again can therefore add another device even on hardware that the account used before.
The password and recovery key solve different problems
The account password authenticates a login. It does not recreate a missing message key. An encrypted message remains unreadable when the current device lacks its key, even after the user enters the correct account password.
Element can obtain a missing key through encrypted key backup. It can also request the key from another device or import a manual backup. Trusted devices may share keys automatically. An untrusted requesting device can need manual approval.
The recovery key verifies a new device and unlocks the encrypted key backup. It is separate from the account password. An already verified device can repair recovery when the original recovery key no longer works. If neither route remains, resetting the cryptographic identity loses access to the earlier encrypted history and tells contacts that the identity changed.
Room history has two independent gates
A room setting determines which earlier events a new member can read. Restricting that setting later does not retract history that the room already exposed under the previous rule. A person who read those events keeps that knowledge, and any separate copy remains outside the later restriction.
Encryption adds another gate. Permission to see an event does not supply the message key required to decrypt it. A member can therefore enter the room and still see an unreadable event when the current device lacks the corresponding key.
Matrix does not move communication history automatically when the user creates an account on another homeserver. The new account does not carry the old rooms or encrypted keys into its session.
Encrypted search runs only through a narrower path
Element searches encrypted-room content only in the desktop client. The user must enable Message search under Security & Privacy first. The search index belongs to that local client path. A search that works in an ordinary room does not prove that the current device has indexed an encrypted room.
Logging out destroys that Matrix device entry. A later login creates another one, so the replacement session must regain the message keys before it can read or search the same encrypted history.
The right panel can create copies outside the room
The room right panel lists members and shared files. Authorized administrators can also reach room settings there. Optional bridges and widgets use the same panel. Bots can also appear there. Each integration adds a data path outside the room’s encryption boundary.
Element can export a room conversation as HTML or plain text. JSON is another export choice. The export becomes a local file outside the room. Later membership or history changes do not withdraw that saved copy, so an export has a different access boundary from the live room.
Spaces organize rooms, while Favorite and Low Priority change where one room appears in the list. Those controls reorganize navigation; they do not merge the rooms or give one room access to another room’s history.
