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.
Areas and themes
IT works in a compact service console, HR in a clearly organised application of its own, and your customers in a portal that reflects your brand. Everything runs on one platform, and everyone sees only what concerns them.
Per area
Areas
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.
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
Colours, logo and light or dark display per role. The customer portal appears in your brand, IT service in its own design.
Every role gets its menus and its entry point. Nobody clicks through features that don't concern them.
Reading, creating, editing and deleting are controlled down to the individual record. One area cannot see another area's data.
Each area gets the AI assistants and tools that suit it. They only work with that area's data.
Why areas
When every department needs something different, another tool is often introduced. The follow-on costs for licences, operation and interfaces become apparent later.
Each department has its own system, with its own sign-in, its own permission model and its own data.
Every area works like an application of its own, but uses the same data model and the same permission check as all the others.
What's included
A theme sets the colours of the entire application frame: navigation, surfaces, buttons and status indicators. You design light and dark mode separately, and the logo too. Anything the theme does not set stays at the default, so a theme that only sets the brand colour consists of a single entry.
Menus per role, with exactly the entries that role needs.
The service desk lands in its ticket list, management in the dashboard.
Global search only covers the areas that concern each role.
Optional AI assistants are assigned to areas, each with defined data access.
For details of your corporate design, you can store custom styles per role.
In practice
In the editor, you set up a new area in a manageable amount of time. If you wish, the AI creates it from your description as a draft for you to review.
The role is the area: it bundles what its members see, may do and how it looks to them.
You set which data this role may read, change, delete and create, phrased as a rule such as “only cases of our own company”.
Theme, logo, navigation and start page. A customer portal in your brand, an internal console in your house colour.
You set which AI assistants and search sources this area uses. No others are available to it.
Like every configuration change: review in a draft, publish together and undo if needed.
Combining roles
The procurement team lead is also a member of the project portal. The IT colleague looks after the vehicle fleet on the side. Areas have to reflect that without anyone needing two logins.
In nexxcite, roles can include other roles, across several levels. Permissions add up, and so do search sources and assistants. For the look, priority decides: the most important role sets theme, navigation and start page. The colours of two roles are never mixed.
Typical set-ups
IT, HR, procurement, quality and facilities as separate applications, with shared master data such as employees, sites and cost centres.
Several subsidiaries in one installation, each with its own logo and strictly its own data, and the holding with the overall view.
Internal processing and the portal for customers or suppliers work on the same data. External users only ever see their own cases.
Separate applications for users, one platform for IT
One operation, one update and one central permission check, while every area still gets the application it needs.
See areas in a demoQuestions
No. Other areas' records appear neither in lists nor in search, and their data objects do not appear in the navigation. Through the API the system reports “not found” rather than “forbidden”.
Yes, deliberately. Master data such as employees, sites or cost centres is shared by all areas; cases stay separate. Access rules define what is shared.
No. You license the platform and the number of users signed in at the same time, regardless of how many applications or areas you have. Further areas need no further licence.
Yes. Permissions apply to the configuration itself as well, so separate administration per area is possible.
Yes. A customer portal is an area like any other: its own role, its own theme in your brand, its own navigation and access to its own cases only.
Live demo
In the demo we set up a platform for your organisation, with two areas, their own themes and separated data.