| Enterprise | Within Shibumi, the Enterprise is the unique workspace (tenant) for your team. This is typically scoped to an organization, but could be your region, your department or even just your working group. |
| App | Within an enterprise, admins build Apps. An app is a container allowing you to manage a solution on the Shibumi platform. It is configured using Shibumi templates, roles, sections, etc. |
| Template | When you configure an app in Shibumi, you do so using Templates. These are building blocks that define the hierarchy of a solution and that enable collection and review of data. App Admins are responsible for configuring the layout, attributes, metrics, roles, and logic on the templates. Administrators create customized templates to address the unique requirements of their solutions. |
| Instance | A specific occurrence or representation of a work item that is derived from a template. Each instance embodies the structure, attributes, and content layouts defined by the template, but with its unique set of data and information pertinent to that particular work item. |
| Attribute | A value or values that can change. These are the variables in Shibumi templates used to store data or calculations based on other data. |
| Association | A link, stored as an Attribute, to another instance of a Template. |
| Calculated Attribute | An attribute that obtains its value by using a formula expression. |
| Child Type |
A definition of which templates can be added as children. Adding Child Types to a template defines the hierarchy. |
| Dashboard | A UI element that allows users to add sections in a previously created instance. Most sections are configured in the Templates. A typical use for Dashboards is for ad-hoc reporting and ad-hoc charts. |
| Environment | Shibumi is a cloud-based, SaaS solution. Shibumi maintains multi-tenant Environments in North America, Europe, and Asia Pacific. These are hosted in the Amazon Web Services Cloud. |
| Layout | The design structure used on tabs within templates to determine how content is presented and arranged on an instance. Layouts play an essential role in organizing and displaying information within a tab by defining where sections/elements appear and when. |
| Metric | KPIs that can have different datasets tracked over time. E.g., the Metric “Revenue” would have a Target, Forecast, and Actual dataset. The values for each dataset can be entered into a time-based array. E.g., in January the Target value = 100, Forecast value = 110, Actual value = 105. In February the Target value = 110, Forecast value = 110, Actual value = 115. This ability to enter and aggregate value over time is a key differentiator for Shibumi. |
| Presentation | A special UI element that allows users to create slide shows from Dashboards, or configure custom slides with sections. The users can then present these slide shows with live data directly from Shibumi, without having to copy the charts and data into a tool such as PowerPoint. |
| Role | A way of grouping users that perform a common function or need similar access to various data. There are predefined roles as well as custom roles in Shibumi. |
| Section | A distinct component on a layout, dashboard, or presentation slide that can display different types of content. Sections are the building blocks that make up the structure of pages where you can present information in various formats. |
| Tab | Tabs are a navigational component within templates, serving as a means to segregate and organize content into different areas for easy access and management. |