# Glossary ### **Host** A host in Termius represents a remote machine that can be accessed via multiple protocols, such as SSH, Telnet, etc. It is defined by an IP address and includes metadata, such as labels and tags, for easier search and navigation. You can configure multiple protocols for a single Host. For example, you can set up SSH with a port, credentials, and a jump host; enable Mosh when you need connection stability while changing networks; or configure Telnet with a different port and credentials. ### **Group** A group is a labeled collection of Hosts that share a common characteristic, such as a customer, location, or environment. A nested structure helps organize Hosts and simplify navigation. All hosts in a group inherit the group settings unless they are overridden. ### **Key** A key in Termius is a labeled secret container that holds private and public keys, certificates, and passphrases. ### **Identity** An identity in Termius holds a username, password, and key. It links to hosts and groups to eliminate credential duplication. ### **Snippet** A snippet is a labeled shell script for easy repeated executions. ### **Snippet package** A snippet package is a collection of related snippets. It allows you to organize your snippets by type, target system, or domain. ### **Known hosts** A known host in Termius stores the remote machine's public key. It is used to verify the host's identity on connection, to prevent man-in-the-middle attacks. ### **Port forwarding rule** A port forwarding rule in Termius stores information about remote, local, and dynamic port forwardings so you can get them up in one click. ### **Vault** A vault is the top-level organizational unit, designed for access control. It's an end-to-end encrypted storage for all your data in Termius: Hosts, Groups, Keys, Snippets, Port Forwarding rules, and Known Hosts. Vaults let you give different members access to different resources. ### **Local vault** The local vault stores data only on the current device, without syncing or sharing it across devices. Data in the Local Vault is not backed up. If you don't have a subscription, log out of your Starter account, or the app removal will lead to permanent deletion of unsynchronized changes. ### **Personal vault** The personal vault is created automatically when you sign up. It can be used for items not meant to be seen by the team, such as credentials or test and work-in-progress servers. Data in the Personal Vault is protected by your encryption password and is not accessible without it. ### **Team vault** The team vault is created automatically once you invite your first teammate. This vault is shared with everyone on the team, enabling your team to manage infrastructure together. ### Custom team vaults The custom team vaults are additional vaults when your company requires **granular permissions** and controlled access to information across team members. Use them to separate data by team, project, or environment, and define who can access each vault. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.termius.com/getting-started/glossary.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.