# XML v1.0 (deprecated) {% hint style="warning" %} This XML version has been deprecated in favor of [XML v2.0](https://dev.ubidots.com/apps/custom-sidebar/xml-v2.0) {% endhint %} The XML v1.0 syntax allows to customize the sidebar elements described below. ## XML syntax The custom sidebar uses XML to map UI elements to code, which is the engine that allows the creation of a sidebar tailored to a specific application. The available UI elements, and their hierarchy, are: ``` ├── tree │ ├── menu │ │ ├── toggle │ │ │ ├── icon │ │ │ ├── label │ │ │ ├── chevron │ │ ├── collapsable │ │ │ ├── menulink │ ├── link │ │ ├── icon │ │ ├── label │ ├── paragraph │ ├── divider ``` Using these XML elements comes with rules that are enforced by the editor and warns you of errors in the syntax: 1. The XML needs to start with:\ `` 2. The `` element is mandatory. It must have at least 1 or more `` or `` elements. 3. The `` element must have at least 1 `` and 1 `` elements. 4. The `` element must have at least 1 `` element. 5. The `` element must have at least 1 `` and `` elements. Here's a quick summary of the available elements, but you can click the links and read more details:

Sidebar element	Description	Properties
tree	Root element. All other elements must be inside.	–
menu	Allows creating dropdown menus.	defaultShow: determines whether the dropdown is open or closed when loading the app.
toggle	Comprises the dropdown itself.	–
icon	Represents the icon the dropdown.	name: name of icon from Fontawesone.
label	Text in the dropdown menu.	–
chevron	Arrow icon in the dropdown menu.	–
collapsable	Comprises a parent element for all the options in the dropdown.	–
menulink	Actual options displayed under a dropdown menu.	path: where the menulink redirects to upon clicking. permissions: list of end-user permissions under which the menulink will be visible. tags: list of end-user tags under which the menulink will be visible. open: open link in same tab or redirect. exact: highlights the menulink when in the exact path defined by path.
link	Creates direct access to links.	path: where the menulink redirects to upon clicking. permissions: list of end-user permissions under which the menulink will be visible. tags: list of end-user tags under which the menulink will be visible. open: open links in same tab or redirect. exact: highlights the menulink when in the exact path defined by path.
paragraph	Creates titles of different sizes. It helps in creating defined sections in the sidebar.	type: determines the size. It can be "h1", "h2", "h3", "h4", "normal" or "bold".
divider	Creates horizontal lines that serve as section separation.	–

### tree Parent element where all `` and `` reside: ```xml ``` ### menu, toggle, icon, label, chevron, collapsable and menulink Elements used to create dropdown menus: ```xml Settings Datasources Custom dashboards ``` This will create a dropdown menu, with its options, as follows:

These are the properties of the `` element:

Property	Description
path	This is a path in Ubidots to either a direct resource, for example "/app/dashboards/663d484aaa8d92005751b2e2", or a module "/app/dashboards/", or a full URL in Ubidots or an external website.
permissions	Comma separated list of permissions associated with the path. An end user will only see this menulink option if its permissions match.
tags	Comma separated list of tags. This adds a visibility layer to the sidebar. An end user will only see this menulink option if its tags match. See also here.
open	Available options are: - "tab": link opens in a new tab. - "redirect": link opens in the same tab.
exact	"true" or "false". Highlights the menulink when in the exact path defined by path.

### link Element to create shortcuts, in other words, direct access to modules or resources: ```xml Home ``` This will create a direct link, as follows:

The properties of the `` element are the same as the `` ### paragraph and divider Title/label element and horizontal separation line. ``` SECTION 1 SECTION 2 ``` This will create the following:

## Permissions With permissions, the `` and `` elements will only appear to those end users whose assigned permissions match that of the element configuration. The available permissions for each possible path that's exposed to the end users in the application are:

Module	Path	Permissions
Devices	"/app/devices/"	"ubi_datasource.view_device"
Device groups	"/app/device-groups/"	"ubi_datasource.view_devicegroup"
Dashboards	"/app/dashboards/"	"ubi_dashboards.view_dashboardpg"
Events	"/app/events/"	"ubi_events.view_eventpg"
Reports	"/app/data-analysis/"	"ubi_data_analysis.view_report"
Organizations	"/app/organizations/"	"customuser.view_organization"
Users	"/app/organizations/users"	"customuser.view_user"

## Filter elements by tags The `` and `` elements receive a "tag" property that adds a visibility layer on top of the permissions assigned to an end user. The way it works is by matching the tags of an end user with those specified in the `` or `` (learn [more about tag filtering](https://help.ubidots.com/en/articles/8063141-ubidots-basics-tags)). Simply put, if there's at least one match between the user tags and the element's, it means the element will be visible to the user. This filtering by tags allows customizing the sidebar based on the user accessing the platform. For example, say you want to create a direct link that takes users to their own home dashboard, you would create an XML as follows: ```xml Home Home ``` Let's assume 2 end users, with tags "tag1" and "tag2", respectively. Note that there are 2 home links in the XML, however, since they have different tags ("tag1" and "tag2"), each home link will appear to the respective user. Likewise, this will preview the following sidebar. We have marked what each user would see:

--- # 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://dev.ubidots.com/apps/custom-sidebar/xml-v1.0-deprecated.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.