# IFS Cloud Report Builder, Appearance Designer, Custom Menus and Approval Templates

> Source: https://netray.co/erp-help/ifs-cloud-report-builder-appearance-designer-custom-menu
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: ERP Help

## Short answer

There is no single report builder in IFS Cloud. Formatted documents come from the report designer for your release (Crystal only on older layouts), ad hoc lists come from Quick Reports, and the look and layout of pages is adjusted with the page designer tools, custom menus and approval templates. Use the supported tools and keep customization small so updates stay easy.

## Kind

how-to

## System

ifs

## Erp

IFS Cloud

## Module

UI customization / Approvals

## Query

ifs cloud report builder

## Alternate Queries

- ifs cloud appearance designer
- ifs cloud custom menu
- ifs cloud approval template
- ifs cloud crystal report

## Applies To

IFS Cloud 21R1 and later. Tool names and locations differ between releases and editions, so verify them in your documentation.

## Steps

### How to approach UI and report customization

**Items:**

- List the actual business need: a different field order, a new menu entry for a role, a changed approval chain, or a new document.
- For documents, copy the standard report layout and edit the copy. See the report designer comparison page for the full choice.
- For page appearance, use the designer provided for Aurena pages to hide, move or relabel elements for a role and save it as a customization.
- For navigation, create a custom menu entry or a favorites style grouping for the role instead of training users to search.
- For approvals, build an approval template that defines the steps, approvers and amount or condition limits.
- Test as a typical user of the target role, then transfer the configuration through your normal process.

## Sections

### Page appearance customization

**Body:**

Aurena pages can be adjusted within the limits the platform allows: showing or hiding elements, changing labels, reordering groups, adding configured fields and adding saved filters. These changes are stored as configuration, not code, which is why they usually survive updates better than modifications to the application itself.

Apply changes by role or user group and avoid personalization that only one person has, since support staff then see a different page from the user who reports a problem.

### Custom menus

**Body:**

Custom menu entries give a role a short list of the pages they use daily. They are a navigation aid and do not change security, so a user still needs permission for every page in the menu. If an entry is visible but the page fails to open, check the user's permission sets first.

Name entries for business tasks and keep the structure shallow. Review them after a release for pages that were renamed or moved.

### Approval templates and reports

**Body:**

Approval templates describe who approves what, in which order, and under which conditions such as an amount threshold or an item group. They depend on the supervisor and role data of your employees, so inaccurate organization data shows up as approvals that stall or go to the wrong person.

For formatted output, use the report designer route for your release. Crystal-based layouts are a legacy path some customers still maintain, so avoid adding new ones unless your version requires them.

## Pitfalls

- Building personal page layouts that make support and training harder.
- Treating a menu entry as a security control.
- Designing approval templates before cleaning up supervisor data.
- Customizing standard report layouts instead of copies.
- Skipping a post-update review of custom menus and layouts.

## Ai Angle

Customization sprawl is a documentation problem as much as a technical one. An assistant that reads your exported configuration on your own servers can list which pages, menus, layouts and templates were changed, by whom, and which users depend on them. That makes update planning much faster. It reads and reports; your team decides what to change.

## Faq

### Does IFS Cloud have a report builder?

**Answer:** It has several tools rather than one: Quick Reports for lists, a report designer for formatted documents and analytical tools for dashboards. Which designer applies depends on your release.

### Do UI customizations survive an update?

**Answer:** Configuration-based changes are designed to carry forward, but you should still run regression tests on customized pages after each update, because underlying pages can change.

### Can a custom menu give access to a page?

**Answer:** No. A menu only provides navigation. Access is controlled by permission sets, so the user needs the right set for the page that the menu opens.

### Why do approvals go to the wrong person?

**Answer:** Usually the template conditions, the employee's supervisor setting or an inactive approver. Check the template steps first, then the organization and supervisor data of the requester.

## Search terms

ifs cloud report builder, ifs cloud appearance designer, ifs cloud custom menu, ifs cloud approval template, ifs cloud page designer, ifs cloud ui customization, ifs cloud crystal report, ifs aurena customization

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json