# Admin UI > Source: https://docs.recombee.com/admin_ui > For the complete documentation index, see [llms.txt](/llms.txt). **Table of contents** * [Sections](#sections) * [My Dashboard](#my-dashboard) * [Database](#admin-ui-database-sections) * [KPI](#kpi) * [Items and Users](#items-and-users) * [Series](#series) * [Scenarios](#scenarios) * [Business Rules](#business-rules) * [Segmentations](#segmentations) * [No-Code Widgets](#no-code-widgets) * [Catalog Feed](#catalog-feed) * [Settings](#settings) * [Organization](#organization) * [Invites & Access Levels](#invites-access-levels) * [Access to Database](#access-to-database) * [View](#view) * [Edit](#edit) * [Access to Organization](#access-to-organization) * [View](#view) * [Edit](#edit) * [Finance](#finance) * [Success Metrics in KPI](#success-metrics-kpi) * [Estimated Metrics](#estimated-metrics) * [Reported Metrics](#reported-metrics) # Admin UI Recombee Admin UI is available at [admin.recombee.com](https://admin.recombee.com) * On registration an **Organization** is created for your company. * An Organization can contain multiple **Databases**, each with separate data and recommendation models. * Two Databases are created on registration - one for development purposes and one for production usage. [![KPI console in the ,[object Object]](/img/gui/kpi.webp)](/img/gui/kpi.webp) KPI console in the [Admin UI](https://admin.recombee.com) ## Sections ### My Dashboard * Place for pinning the widgets that are the most important for you, so you see them right after logging in. * Use the star symbol for pinning. [![Pin widget to My Dashboard](/img/gui/pin_to_dashboard.webp)](/img/gui/pin_to_dashboard.webp) ### Database #### KPI Console that contains widgets showing important data such as number of recommendations, number of ingested interactions or success rate of the recommendations per [scenario](/scenarios). Read more about the [success metrics](#success-metrics-kpi). #### Items and Users Catalog of the items and users that are contained in the Recombee database with their properties. [![Items Catalog](/img/gui/items_catalog.png)](/img/gui/items_catalog.png) Items Catalog #### Series Catalog of uploaded [Series](/api#series). Series are used in use-cases such VoD to express the order of episodes. #### Scenarios Section for setting behavior of recommendations in each [scenario](/scenarios). Read more about the scenarios [here](/scenarios). [![Setting Logic to a Scenario](/img/gui/set_logic.png)](/img/gui/set_logic.png) Setting Logic to a Scenario #### Business Rules Section for creating your custom [business rules](/reql#business-rules) that can be then applied to your [scenarios](/scenarios). Read more about the business rules [here](/reql#business-rules). #### Segmentations [Segmentations](/segmentations) are used for recommending categories, genres, brands, artists, etc. #### No-Code Widgets Section for creating [No-Code Widgets](/scenarios#scenarios-html-widget) that are used for displaying recommendations at your site. #### Catalog Feed Section for setting a [catalog feed](/catalog_feeds), which can be used for synchronizing the items to Recombee. #### Settings Section for getting Database ID & tokens for connecting to the Recombee API and managing access to the Database (_Manage Access_ button). ### Organization Section for admins of the Organization for managing access (_Manage Access_ button), getting information about limits/usage on Organization level and about selected [Billing Plan](https://www.recombee.com/pricing). ## Invites & Access Levels Colleagues can be invited to the whole Organization or just particular Database (use the _Manage Access_ button in _Settings_). Optionally, it is also possible to integrate Recombee Admin UI with your SSO provider - see [Third Party Login / SSO](/third_party_login_sso) for details. [![Manage access](/img/gui/manage_access.webp)](/img/gui/manage_access.webp) ### Access to Database #### View * Can view the Database (see KPI, Items & Users, Scenarios ...) but cannot change any settings * Cannot see the API tokens for manipulating the Database #### Edit * Can make changes to the Database * Can see the API tokens for manipulating the Database ### Access to Organization #### View * Can view all the Databases in the Organizations but cannot change any settings * Cannot see the API tokens of these Databases #### Edit * Can make changes to all the Databases in the Organizations * Can see the API tokens for manipulating these Databases #### Finance * Can see and change the billing info of the Organization. ## Success Metrics in KPI You can see in the KPI how many clicks / purchases / bookmarks etc. were based on the recommendations. For each of the metrics there are **estimated** and **reported** values. [![Reported vs. Estimated metric](/img/gui/estimated_reported.webp)](/img/gui/estimated_reported.webp) Reported vs. Estimated metric ### Estimated Metrics * Estimates are based on a _time window_: If an item is recommended to a user, and this user subsequently interacts with that item within a time window, it is considered a successful recommendation * These metrics don't need any implementation and usually give reasonable estimates of the success. However, they don't work for example in case of emailing (users look at the recommendations usually hours later, so their clicks are not counted as they are out of the the time window) or at sites where items can be easily found by different means than recommendations. In these cases explicit reporting of recommendations' success is a must. ### Reported Metrics ![](/img/gui/reported-metrics.png) * Successful recommendations explicitly reported to Recombee. * Each recommendation request returns a unique `recommId` (e.g. _3f6ad2f2-a3f1-4ba1-a690-f4f01f76d4eb_) that can be passed to `recommId` parameter of an interaction (Detail View, Purchase, etc.) in order to mark that interaction as based on recommendation. * When properly integrated, the reported metrics should give you exact numbers about successful recommendations. * Therefore we suggest to implement sending of `recommId` in interactions whenever possible.