# Hidden Notes
For easy extensibility, a lot of features in Trilium make use of actual notes to store information as opposed to having them stored in a separate location in the database. This allows some functions such as AttributesRelations or even Search and Links to be able to operate on them. As the name suggests, these notes are hidden to the user by default to prevent cluttering the note tree and to prevent them from being accidentally deleted. The hidden notes are stored in the user's Database just like normal notes, but they have a unique Note ID which allows them to be distinguished from the normal ones. ## Accessing the hidden note tree From the Global menu, select _Advanced_ → _Show Hidden Subtree_. ## Contents of the hidden note tree Here is a brief summary of all the notes within the hidden tree:
NoteDescription
Note Map

This note is actually opened when the Note Map feature that is accessed from the Launch Bar.

It is possible to create any child notes in it without any additional meaning. For example, it can be used to store a list of note maps which can be linked to from other notes or bookmarked.

SQL Console History

When SQL queries or commands are executed in the SQL Console, they are stored here, grouped by month. Only the query is stored and not the results.

This section can be accessed without going to the hidden tree by simply going to the Global menu and selecting Advanced → Open SQL Console History.

Notes can be added as children of this tree, but it's generally not recommended to do so to not interfere with the normal history process.

Search History

Whenever a search is executed from the full Search, the query will be stored here, grouped by month. Only the search parameters are stored and not the results themselves.

This section can be accessed without going to the hidden tree by simply going to the Global menu and selecting Advanced → Open Search History.

Notes can be added as children of this tree, but it's generally not recommended to do so to not interfere with the normal history process.

Bulk Action

This section is used for Bulk Actions. The last configuration for bulk actions will be stored as part of this note, each action in its own action label.

Notes can be added as children of this tree, but there won't be any benefit in doing so.

Backend Log

This note corresponds to the backend log feature (see Error logs).

This item can be accessed without going to the hidden try by going to the Global menu and selecting Advanced → Show backend log.

User HiddenThis section can be used by scripts to create their own notes that should not be directly visible to the user. The note can be identified by scripts by its unique ID: _userHidden
Launch Bar Templates

This section contains the templates for the creation of launchers in the Launch Bar. It is not possible to create child notes here.

Theoretically some of the notes here can be customized, but there's not much benefit to be had in doing so.

Shared Notes

This tree lists all of the notes that are shared publicly. It can be useful to track down which notes are shared regardless of their position in the note tree.

This section can be accessed without going to the hidden tree simply by going to the Global menu and selecting Show Shared Notes Subtree.

Sub-notes cannot be created here.

Launch Bar

The tree contains both available and displayed items of the Launch Bar.

This section can be accessed without going to the hidden tree by:

  • Going to the Global menu and selecting Configure Launchbar.
  • Right-clicking an empty space on the Launch Bar and selecting Configure Launchbar.

Sub-notes cannot be created here.

Options

This section stores the list of Options.

This section can be accessed without going to the hidden tree by:

Mobile Launch Bar

This is very similar to the Launch Bar, but is dedicated for the mobile UI only.

Accessing it outside the Launch Bar is the same as the Launch Bar, but needs to be done so from the mobile interface.

User GuideThis is where the note structure for the User Guide is actually stored. Only the metadata is stored, as the help itself is present as actual files in the application directory.