> For the complete documentation index, see [llms.txt](https://docs.ib.b2core.b2broker.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ib.b2core.b2broker.com/for-brokers/back-office-guide/interface-overview.md). # Interface overview The Back Office user interface is uniform across all pages, ensuring consistent look and feel and featuring a common set of basic options. ## The top bar options At the top of a typical Back Office page, you can find a top bar with the following elements: *

— click it to expand or collapse the main menu. *

— click it to see the events that were scheduled for Admins in the **Event Calendar**. The number of upcoming events is displayed on a counter badge. *

— click it to see pending client requests. The number of new requests is displayed on a counter badge. * **Language** **menu** — click it to select the interface language. * **User profile pane** — click this panel to access the **Log out** button. ## Common buttons and icons The following buttons can be found on most Back Office pages. * the **Create** button — used to add a new entry. * the **Export** button — used to export table data to a CSV file. * the **Import** button — used to import an XLSX or a CSV data file. *

— used to apply custom filters. *

— used to reset custom filters. *

— used to access details. *

— used to delete an entry. Page elements may serve as hyperlinks which can be clicked to drill down to details. Access to this data is maintained based on the permissions assigned to a particular user group. ## Filtering Throughout the Back Office, the data is typically organized in tables that can be filtered. You can specify multiple criteria for filtering column data. When filtering is available, the appropriate input fields are displayed in column headers. The inputs vary depending on a data format, such as text, number, date, time, or list. To facilitate filtering by date, two fields for the start and end dates may be displayed so that you can define a time period. To enable or disable filters, click

and

buttons. ## Sorting In the Back Office, you can sort the data available in tables. The columns by which you can sort data are marked with

displayed in column headers (no arrows are displayed when sorting isn't available). You can click these arrows to sort data in an ascending (

) or descending (

) order, by a single column at a time. ## Pagination You can display table data across multiple pages and specify how many records to display on a page. You can also view the total number of records found. To open the previous or next page, click the left or right arrow. ## Export and import Some Back Office pages support data export to CSV files. This option is available on pages that contain an **Export** button above the data table. The data in a resulting file matches the applied sorting and filtering criteria. To export page data to a CSV file, click the **Export** button. Some Back Office pages also support importing of CSV and XLSX files. This option is useful when you need to update the symbol settings for a partnership program. To import data, click the **Import** button, choose the file that you want to import and click **Open**. ## Localizations In the B2CORE Back Office, you can configure fields that support localizations to have multiple language options in the B2CORE UI. Using the **localization** buttons, you can set translations for these fields into different languages. To set localizations, click the **Localization** button next to the field, enter the translation in the supported languages and click **OK**. Note that only enabled localizations are displayed. You can enable or disable localizations in the **System** > **Localizations** section. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.ib.b2core.b2broker.com/for-brokers/back-office-guide/interface-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.