Skip to content

Interfaces

Every role sees exactly what it needs

Whether a digital process is adopted depends a great deal on the interface. If people have to work through fifteen fields when twelve of them do not concern them, they go back to the spreadsheet. In nexxcite, you therefore set up separate forms, lists and start pages for each role.

  • Role-based views
  • Usable on any device
  • Own branding per role
  • Light and dark
Book a live demo Areas and themes

Adoption

Clear interfaces for every role

Fewer fields Only what concerns the role Whoever raises a purchase request sees a short form. Supplier, budget and internal notes are for procurement.
Every role Its own way in Its own start page, navigation and lists. Nobody clicks through features that have nothing to do with them.
Any device One configuration Desktop, tablet and phone use the same design. There is no second version and nothing to install.

The key point

The same record looks different to each role

The requester sees a short form with four fields. The reviewing department sees the same data and also internal notes. Audit additionally sees the complete history.

Besides permissions, this is also a matter of design: which blocks appear, in what order, with which labels and under which conditions.

Portals for external users work the same way. A customer sees her own cases without any insight into your internal structure.

  • Own form version per role
  • Fields that appear or disappear depending on the case's status
  • Read-only depending on role, status or a data value
  • Own start page and navigation per role
  • Theme and logo per role, separately for light and dark
  • Portal views for people outside your organisation

Areas

Each department gets its own application

You divide nexxcite into areas, such as IT, HR, procurement or a portal for your customers. Each area has its own roles, navigation, design and logo, and sees only its own data. To users they are separate applications; for your IT it remains one platform.

Choose an area

Invisible to this role: HR files, purchase orders, customer data

Invisible to this role: IT tickets, purchase orders, customer data

Invisible to this role: IT tickets, HR data, customer portal

Invisible to this role: Everything internal and every other customer

Its own look

Colours, logo and light or dark display per role. The customer portal appears in your brand, IT service in its own design.

Its own navigation and home page

Every role gets its menus and its entry point. Nobody clicks through features that don't concern them.

Strictly separated data

Reading, creating, editing and deleting are controlled down to the individual record. One area cannot see another area's data.

Its own assistants

Each area gets the AI assistants and tools that suit it. They only work with that area's data.

Three kinds of view

Forms, lists and dashboards

Built from blocks, tied to conditions and different for each role. You design them in the editor or, if you wish, let the AI create a draft.

Forms

Where the work happens. Built from blocks you arrange and tie to conditions.

  • Input fields, labels, text, images, files
  • Tabs and multi-column layouts
  • Embedded lists of related records
  • Buttons and toolbars that trigger flows
  • Visibility and read-only per role and status

Lists

The overview. Columns, sorting, grouping and filters, saved as a view per role.

  • Columns from own and related fields
  • Filters as saved queries
  • Bulk actions across several records
  • Export to Excel and CSV
  • Paged queries even for large data sets

Dashboards

The start page. Assembled from building blocks and different for each role.

  • Charts and figures from your data
  • Calendar and catalogue views
  • Search boxes and short lists
  • Embedded pages from other systems
  • Assistant block for questions about your own data

Optional: with AI

If you wish, the AI sets up the views

  1. 01

    You describe the views

    "Requesters only see description, quantity, amount and reason on the form. Procurement also sees supplier, product group and internal notes."

  2. 02

    The AI creates them in a draft

    Two form versions, the matching visibility rules and a list for procurement. Each change can be traced on its own.

  3. 03

    You review and adjust

    In the editor you move blocks, change labels or give the AI another instruction.

  4. 04

    You approve

    From now on, every role sees its own version. If something is not right, you can return to the previous state.

The limit

Interfaces are built from the platform's building blocks. You can arrange them, label them, tie them to conditions and style them in your own branding. You cannot, however, program your own controls.

For business processes, that is rarely a problem. For an application aimed at customers that needs its own design language, a development platform is the better tool. We would rather tell you up front.

Standard features

What works without extra effort

  • Usable on every device: the same configuration for desktop, tablet and phone, with no second design.
  • Light and dark mode follow the operating system setting.
  • Nothing to install on end devices. A browser is enough, as the interface is generated on the server.
  • Multiple languages via translations you maintain yourself, including your own field labels.
  • Search across all permitted areas, with the rights of the person searching.
  • Custom CSS and JavaScript per role, when your branding needs more than colours and a logo.

FAQ

What business teams often ask

Can we apply our corporate design?

Yes, per role: a theme with its own colours for light and dark, a logo in both variants, its own navigation and start page. Where that is not enough, add your own CSS and JavaScript.

Does it work on a phone?

Yes. The same configuration adapts to desktop, tablet and phone, with no second design and no app to install.

Can customers and suppliers use the interface?

Yes, through portal views with a role of their own. External users only see their own cases and nothing of your internal structure.

Do we need a developer for forms?

No. Forms, lists and dashboards are built in the editor or, if you wish, by asking the AI. You cannot program your own controls, though. For that, a development platform is the right tool.

Live demo

In the demo, we rework one of your forms

Live in the session, in the editor and with AI if you wish. You will see how a form changes when every role only sees what it needs.

Book a live demo On to flows and rules
  • Your form, not an example
  • A view for every role
  • Remote or on site