DynamicForm Start free trial
Step 7 of 15 · Menu Configurator · topic 1 of 5

Build · Menu Configurator

Menus are the front door — for web and phone, for every role

Decide what each person sees when they sign in: a web sidebar and a phone home screen built from the menus their roles allow. Drafted by AI from your requirement, fine-tuned by hand.

One menu tree becomes a web sidebar and a phone home screenA tree of menus — loans, credit and field items — turns into a sidebar on the laptop and a grid of tiles on the phone for the items marked for mobile.MenusLoansNew applicationAll applicationsCreditCredit queueApprovalsFieldNew leadMy leadsWeb sidebarPhone home screenLoansNew applicationAll applicationsCreditCredit queueApprovalsHome
A menu tree folding into a phone home screen of tiles on one side and a laptop sidebar on the other.
In short

The Menu Configurator decides what each role sees on the web sidebar and the phone home screen. Items open new entries, work lists or reports, or start a process in one click.

Show people the functions their roles allow. Product menus are shared by every company, while each application has its own menus. Platform operators maintain the shared product menus; application menu choices organise work inside the application.

A menu appears only to roles holding the required permission. This behaviour stays the same on the web, on Android and offline. End users keep the same permission boundaries as they move between devices or lose connectivity.

A role can reach menus in several applications. Use its application tabs to choose menus separately for each application. Explore Company Admin to review permissions, application access and record scope together.

End user roles connect permissions, application access and record scope to the work and functions the person can reach.
Roles bring responsibilities, application access and record scope together.

Read the menu table

Bring the planned navigation into requirement intake. DynamicForm can take application menus from the requirement document's menu table, giving designers a stated starting point for review.

Use that table to describe how people should reach the work in the application. Review it alongside the document's role and screen-permission tables, so navigation and access describe the same responsibilities.

Anything unclear in requirement intake becomes a listed gap. Explore AI Core for the design review and Configuration document for the recorded menus and lists.

Build your first app free

All platform features, hosted by us for 120 days. For testing and evaluation, subject to our Fair Use Policy.

Updated 16 November 2026