# What's in the box

> Every module that ships with nexxus, grouped by the area of the menu where you find it. For each one, what it does, its menu entries and routes, the permission that opens it, and which area switch turns it off.

nexxus ships with a set of business modules that are built into every installation: time tracking and absences, customers and projects, invoices, information security, files, the content of your website, the AI assistant and the administration around them. You don't install them. You decide which ones your tenant uses, and roles decide who in your team sees what.

Each module has its own version and its own changelog. Admins find the list under <MenuPath to="Administration > Operations > Modules" />: <Ui>Every module has its own version and its own changelog. Choose a module to see what changed.</Ui>

<Screenshot src={shot_modules_overview} url="/modules" alt={"The module overview with versions and a changelog"} caption={"Every module has its own version and changelog."} />

Search with <Ui>Search modules</Ui>, or narrow the list to one area with <Ui>All areas</Ui>, Start, Organisation and the other area buttons. The list shows <Ui>Module</Ui>, <Ui>Area</Ui>, <Ui>Version</Ui> and <Ui>Last changed</Ui>. Click a module to open its changelog on the right: which modules it needs (<Ui>Requires</Ui>), the changes that are built but not part of a version yet (<Ui>Not released yet</Ui>), and then every version with its date. The changelog entries themselves are written in German. Modules installed as an NXM package carry the chip <Ui>Package</Ui>, and the tab <Ui>Packages</Ui> lists the packages; see [Modules (NXM)](/modules/overview/).

## What's new

After an update, nexxus opens a window once on your next visit: <Ui>What’s new</Ui>, with the release notes of the new version. The main new features come first, with a picture or a small animation, followed by the other changes by module. You do not see sections about areas that are switched off or modules you have no rights for. <Ui>Got it</Ui> closes the window. Afterwards the release notes stay in the window behind your avatar at the bottom of the rail, <Ui>What’s new</Ui>, and a dot on your avatar marks a version you have not read yet. If you have never seen the window, you get the newest version only. The AI Assistant answers "what's new?" with the same release notes. You get them in the language the app shows you, else in English, else in German. English release notes exist from version 0.13.0 on, older versions show in German. A version without Polish release notes shows its English ones to a Polish reader.

Every release has a release note. The module changelogs above remain the detailed record of every single change.

When a process is unique to your company, you add to these in two ways: with [apps](/apps/overview/), small apps your team builds with the AI Assistant, or with [NXM modules](/modules/overview/), full business modules that developers package and install in a tenant.

## Two switches decide what someone sees

<Hub
  inputsLabel="Switches"
  inputs={[
    { icon: 'toggle-right', title: 'Areas of the tenant', text: 'An admin switches whole areas on or off, for everyone' },
    { icon: 'shield-check', title: 'Roles of the person', text: 'Each page opens with a permission' },
  ]}
  core={{
    title: 'Built-in modules',
    text: 'The same in every installation',
    items: ['Time', 'Projects', 'Billing', 'ISMS', 'Files', 'AI'],
  }}
  outputsLabel="Shows up in"
  outputs={[
    { icon: 'list-tree', title: 'The menu', text: 'Only entries you may open, from areas that are on' },
    { icon: 'sparkles', title: "The AI Assistant's tools", text: 'It only uses what you could use yourself' },
  ]}
  caption="A switched-off area disappears from the menu, from the API and for the AI Assistant. Its data stays."
/>

**Areas** are switched in the setup, step Areas, or later under <MenuPath to="Administration > Operations > Setup" /> (see [First run](/setup/first-run/#step-3-areas)). Twelve can be switched off; what one needs, nexxus switches on with it:

| Area card | Modules it switches |
|---|---|
| <Ui>Time tracking</Ui> | Time tracking, Working time account |
| <Ui>Absences</Ui> | Absences |
| <Ui>Customers & suppliers</Ui> | Partners |
| <Ui>Projects</Ui> | Projects |
| <Ui>Invoices</Ui> | Invoices, the billing roles of Organisation |
| <Ui>Contingents & credit</Ui> | Contingents, Credits |
| <Ui>Teams & working time models</Ui> | Teams and working time models of Organisation |
| <Ui>Files</Ui> | Files |
| <Ui>Information security</Ui> | ISMS |
| <Ui>Apps & workspace</Ui> | Workspaces, apps |
| <Ui>Chat</Ui> | Team chat |
| <Ui>Content</Ui> | Content |

Everything else is always on: the dashboard and the desk, the AI assistant with its knowledge, schedules, skills and connectors, users and roles, settings and notifications.

**Roles** carry permissions. Each page below names the permission that opens it; the role editor under <MenuPath to="Administration > Users & access > Access Roles" /> finds a permission by its key. Pages marked *admins* open only for administrators. Details in [Roles and permissions](/setup/roles/).

## Start

| Module | What it does | Menu entry and route | Opens with |
|---|---|---|---|
| Dashboard | Start page with greeting, key figures and the way into the assistant | <Ui>Dashboard</Ui> `/dashboard` | everyone signed in |
| Reports | The query layer behind the key figure tiles: figures from projects, time, absences, ISMS and more, always with the reader's rights. Also the tile assistant and the AI Assistant's report tools. | Tiles on the dashboard | `core.analytics.read` |
| Desk | What lies on your own desk today: tasks, approvals and AI avatars in one place | <Ui>Desk</Ui> `/schreibtisch` | `workspaceItem.read` or `ai.session.use` |
| Calendar | Holidays, vacation, absences, your own appointments and the dated records of installed modules in one calendar | <Ui>Calendar</Ui> `/kalender` | `calendar.use` |
| Workspaces | Boards with Kanban, tasks, assignees, comments and <Ui>My tasks</Ui> | <Ui>Workspace</Ui> `/workspace` | `workspaceItem.read` |
| Apps | Small apps whose documents live in Files, plus your own apps as `.nxa` packages | <Ui>Apps</Ui> `/dms-apps` | `dmsApps.read` |

More: [Build your dashboard](/use/dashboard/), [Calendar](/use/calendar/), [Apps](/apps/overview/).

## Organisation

### Time

| Module | What it does | Menu entries and routes | Opens with |
|---|---|---|---|
| Time tracking | Time entries, monthly timesheets with approval, and the sync with Toggl | <Ui>Monthly timesheets</Ui> `/monthlyTimesheet`, <Ui>Toggl sync</Ui> `/togglSyncLog` | Your own months: `timesheet.monthlyTimesheet.use`; everyone's: `timesheet.monthlyTimesheet.read`. Toggl sync: *admins* |
| Absences | Vacation requests, vacation quotas, public holidays and the team calendar | <Ui>Vacation requests</Ui> `/vacationRequest`, <Ui>Public holidays</Ui> `/holiday` | `absence.vacationRequest.use`; holidays: `absence.holiday.read` |
| Working time account | Working time agreements and overtime bookings per person | No menu entry of its own. Admins see it in the user record, tab <Ui>Time & vacation</Ui>. | via <Ui>Users</Ui> (*admins*) |

### Business

| Module | What it does | Menu entries and routes | Opens with |
|---|---|---|---|
| Partners | Customers and suppliers with branches and contacts. Your own companies are partners too. | <Ui>Customers</Ui> `/partner/customers`, <Ui>Suppliers</Ui> `/partner/suppliers`, and under Administration <Ui>Own companies</Ui> `/own-companies` | `partner.partner.read` |
| Projects | Projects with groups, assignments, rates and links | <Ui>Projects</Ui> `/project` | `project.project.read` |
| Invoices | Invoices with positions, PDF with ZUGFeRD | <Ui>Invoices</Ui> `/invoice` | `billing.invoice.read` |
| Contingents | Contingent agreements with customers. A monthly run creates draft invoices. | <Ui>Contingents</Ui> `/contingentAgreement` | `contingent.agreement.read` |
| Credits | Credit accounts and their transactions | <Ui>Credit accounts</Ui> `/creditAccount` | `credit.account.read` |
| Organisation | Teams, work schedules, billing roles, skill levels and employee profiles | <Ui>Billing roles</Ui> `/billingRole`, and under Administration <Ui>Teams</Ui> `/team` and <Ui>Work schedules</Ui> `/workSchedule` | `organisation.billingRole.read`, `organisation.team.read`, `organisation.workSchedule.read` |

Invoices need the modules Projects and Partners.

Partners, projects, invoices, opportunities and every record of an installed module have the tabs <Ui>Tasks</Ui> and <Ui>Timeline</Ui>. Under <Ui>Tasks</Ui> you add tasks that belong to exactly this record. They also show in <Ui>My tasks</Ui>, with a chip for the record. The tab is there while the area <Ui>Apps & workspace</Ui> is switched on. The <Ui>Timeline</Ui> keeps what happened: a note, a call, an email, a meeting or a status update, newest first. Both are as open as the record itself: whoever may see it may read them, whoever may edit it may write. You can change and delete your own timeline entries, not those of others.

## ISMS

| Module | What it does | Menu entries and routes | Opens with |
|---|---|---|---|
| ISMS | Information security under ISO 27001, NIS2 and Art. 32 GDPR: compliance programmes per framework with their Statement of Applicability, assets with their protection needs, risks rated by the tenant's risk method and recorded in risk assessments, measures with executions and evidence, self-declarations collected in campaigns, and security incidents with their reporting deadlines | <Ui>Compliance programmes</Ui> `/ismsProgram`, <Ui>Assets</Ui> `/ismsAsset`, <Ui>Risks</Ui> `/ismsRisk`, <Ui>Risk assessments</Ui> `/ismsRiskAssessment`, <Ui>Measures</Ui> `/ismsMeasure`, <Ui>Declaration campaigns</Ui> `/declarationCampaign`, <Ui>Self-declarations</Ui> `/ismsDeclaration`, <Ui>Security incidents</Ui> `/ismsIncident`, <Ui>Risk method</Ui> `/ismsRiskMethod` | `isms.program.read`, `isms.asset.read`, `isms.risk.read`, `isms.riskAssessment.read`, `isms.measure.read`, `isms.declarationCampaign.read`, `isms.incident.read`, `isms.riskMethod.read`; your own declarations: `isms.declaration.use`; reporting incidents and seeing your own reports: `isms.incident.report` |

## Documents

| Module | What it does | Menu entry and route | Opens with |
|---|---|---|---|
| Files | Documents and folders with shares, versions, attributes, public links and preview | <Ui>Files</Ui> `/dokumente` | `dms.document.read`; what you see inside is decided by the shares of each document |

More: [Files](/use/files/).

## Chat

| Module | What it does | Menu entry and route | Opens with |
|---|---|---|---|
| Team chat | Channels and direct messages for the team, replies in threads, mentions, reactions, files with preview and code blocks. Notifications come for mentions, direct messages and replies. | <Ui>Chat</Ui> `/chat` | `teamChat.read` to read, `teamChat.write` to write |

The chat is an area of its own. Switched off, it disappears from the menu, and its messages stay.

## Website

| Module | What it does | Menu entries and routes | Opens with |
|---|---|---|---|
| Content | A headless CMS for your own website. Blocks define which fields a content type or a block has. Entries sit in a folder tree and have a draft and a published state; translations sit next to their field. Images and files come with it. Your website fetches published content with a delivery token from `/api/content/v1`. | <Ui>Content</Ui> `/content`, <Ui>Blocks</Ui> `/content-blocks`, <Ui>Media</Ui> `/content-assets`, <Ui>Delivery</Ui> `/content-delivery` | `content.entry.read`; Blocks: `content.block.read`; Media: `content.asset.read`; Delivery: `content.settings.read` |

Website is an area of its own, and its card is called <Ui>Content</Ui>. Switched off, it disappears from the menu and for the AI Assistant, the delivery answers with 404, and the content is kept.

## AI

| Module | What it does | Menu entries and routes | Opens with |
|---|---|---|---|
| AI assistant | The assistant beside every page, conversations, avatars, models and providers, tools and usage | <Ui>AI sessions</Ui> `/ai`, <Ui>Avatars</Ui> `/ai-avatare`, <Ui>AI Providers</Ui> `/ai-providers`, <Ui>MCP overview</Ui> `/ai-mcp`, <Ui>AI usage</Ui> `/ai-usage`, <Ui>AI actions</Ui> `/ai-actions` | `ai.session.use`; providers: `aiAssistant.providerConfig.read`; MCP overview, AI usage, AI actions: *admins* |
| AI knowledge | Knowledge entries the assistant finds and learns from conversations | <Ui>Knowledge</Ui> `/ai-knowledge` | `ai.knowledge.read` |
| AI schedules | Tasks for the assistant on a schedule or when an email arrives | <Ui>Schedules</Ui> `/ai-schedules` | `ai.session.use` |
| Skills | Reusable instructions for the assistant, with files and shares | <Ui>Skill Management</Ui> `/ai-skills` | `ai.session.use` |
| Connectors | Integrations, skills, tools and your own MCP connections for the assistant | <Ui>Connectors</Ui> `/plugins` | `ai.plugin.read` |

The AI assistant is always on and cannot be switched off for a tenant. Who may use it is decided by roles. The last four modules need the AI assistant. More: [Connect your AI](/setup/connect-ai/), [Work with the AI Assistant](/use/assistant/), [Connectors](/plugins/overview/).

## Administration

These modules are always on.

| Module | What it does | Menu entries and routes | Opens with |
|---|---|---|---|
| Users and rights | Users, roles and permissions, business units, tenants, invitations, and acting as another person for support | <Ui>Users</Ui> `/user`, <Ui>Access Roles</Ui> `/accessRoles`, <Ui>Business Units</Ui> `/businessUnits`, <Ui>Tenants</Ui> `/tenants` | Users and Tenants: *admins*; `authentication.accessRole.read`, `authentication.businessUnit.read` |
| Sign-in | Sign-in with password, sign-in link, second factor, trusted devices, single sign-on and Microsoft Entra ID | The sign-in page, the tab <Ui>Security</Ui> in your profile | everyone |
| My profile | Name, picture, password, your own activity, notifications, your own notification rules and personal API tokens | <Ui>My profile</Ui> `/profil`, from your avatar | everyone signed in |
| Setup and system configuration | The setup in eight steps, areas, appearance, logo and the settings of the tenant | <Ui>Setup</Ui> `/einrichtung`, <Ui>System configuration</Ui> `/system-config` | *admins* |
| Email and notifications | Outgoing email, templates, system mails, mailboxes and the notifications in the bell | <Ui>System Mails</Ui> `/system-mails`, <Ui>Mailboxes</Ui> `/mailboxes`, <Ui>Email delivery</Ui> `/emails` | `communication.systemMail.read`, `communication.email.read`; Mailboxes: *admins* |
| Form builder | Forms with categories, field templates, filled-in records and locks | <Ui>Forms</Ui> `/form`, <Ui>Field templates</Ui> `/form-field-template`, <Ui>Categories</Ui> `/form-category`, <Ui>Records</Ui> `/form-record` | `formBuilder.read`, `formBuilder.fieldTemplate.read`, `formBuilder.category.read`, `formBuilder.record.read` |
| Tags and text blocks | Tags for records and reusable text blocks | <Ui>Tags</Ui> `/tags`, <Ui>Text Blocks</Ui> `/textBlock` | `communication.tag.read`, `core.textBlock.read` |
| Logs and operations | Audit log, application and event logs, cron jobs, migrations and the vector viewer | <Ui>Audit Log</Ui> `/auditLogs`, <Ui>Event logs</Ui> `/eventLogs`, <Ui>App Logs</Ui> `/appLog`, <Ui>Cron Jobs</Ui> `/cronJob`, <Ui>Migrations</Ui> `/migrations`, <Ui>Vector Viewer</Ui> `/vectorViewer` | *admins* |
| Platform | What every module stands on: the permission check, uploads, activity, comments, search, number sequences, custom fields, PDF rendering and the module overview itself | <Ui>Modules</Ui> `/modules` | *admins* |

How to connect a mailbox, including Microsoft 365, is described in [Connect mailboxes](/setup/mailboxes/).

## Where the AI Assistant fits in

Every module above is also available to the AI Assistant, within the same limits. It sees the areas that are switched on and uses only tools whose permission the asking person has. A switched-off area is invisible to it, and a person without the permission for invoices cannot have the AI Assistant read or change an invoice either. Before it changes anything, the server builds a confirmation that you approve.

## Next steps

<CardGrid>
  <LinkCard title="First run" description="Switch areas on or off and create the first roles." href="/setup/first-run/" />
  <LinkCard title="Roles and permissions" description="Every permission, what it opens and how roles add up." href="/setup/roles/" />
  <LinkCard title="Modules (NXM)" description="Package your own business module and install it in a tenant." href="/modules/overview/" />
</CardGrid>