Overview
Understand the System menu and find every global setting in its feature chapter
System contains settings that affect not just your own account, but Artwork for many or all users. The menu items you see depend on administrative permissions and enabled modules. Responsibilities can therefore be separated: someone may manage rooms without having access to branding or budget master data.
This chapter contains only organisation-wide Tool settings. Feature settings live directly in the chapters where users apply them. Shift templates therefore sit with the duty roster and budget master data with projects instead of being repeated in a second settings collection.
Check global impact before saving
Changes to modules, master data, event types, shift rules, file formats or budget columns affect existing workflows. Agree the purpose, owner and timing within your team and test critical changes with a manageable example where possible.
System-menu guide
| Menu item | What is managed | Detailed manual |
|---|---|---|
| Tool Settings | Appearance, communication, season, external user sources, interfaces, modules and file rules | Tool settings |
| Shift settings | Workflow, crafts, qualifications, working-time models, templates and rules | Shift settings |
| CRM Settings | Contact types, properties, visibility and maintenance model | CRM settings |
| Inventory | Categories, properties, statuses, tags and numbering | Inventory settings |
| Material Sets | Reusable collections of inventory articles | Material sets |
| Rooms | Areas, rooms, properties, capacities and booking rights | Rooms & booking rights |
| Projects | Categories, statuses, roles, tabs, builders, print layouts and BI configuration | Project settings |
| Calendar | Day window and calendar foundations | Calendar settings |
| Events | Event types, statuses, properties, defaults and BI tags | Event settings |
| Checklists | Global templates for recurring task sequences | Checklist templates |
| Sources of funding | Categories for filtering and consistent assignment | Funding-source settings |
| Budget | Column names, accounts/cost units and budget templates | Budget settings |
Global setting, master data or personal preference?
| Type | Example | Effect |
|---|---|---|
| Global setting | Hide a module, define the season | Entire organisation or feature area |
| Master data | Event type, project status, contract type | Shared selection used by many records |
| Template | Shift, checklist or budget template | Copied or used as a starting point |
| Personal setting | Email frequency, calendar display | Your own user account only |
Personal notification delivery is configured in the notification centre, not under System. Personal account and work details are maintained under My account.
Recommended ownership
- System administrators maintain branding, modules, file rules and technical integrations.
- Feature administrators own room, event, project, shift, inventory, CRM or budget settings.
- Privacy and IT should be involved in external user sources, API keys, interfaces and global announcements.
- Key users review changes from an end-user perspective before broad rollout.
Administrators should document not only how an option is changed, but why it applies and who will maintain it in future.