Choose “Save as PDF” in the print dialog. Enable background graphics so callouts and tables keep their colours.
Manual
The artwork manual as a single document
11 November 2026 · Based on the online edition at wiki.artwork.software
Introduction
What Artwork is and how these docs are organized
Artwork is a project and event management platform for cultural institutions:
theatres, concert halls, museums and festivals. It brings everything around a
production into one tool: projects, the room and event calendar, staff scheduling
(shift plans), inventory, budgets, contracts and contacts.
Artwork is modular. Administrators can enable or disable entire modules
(e.g. Inventory, CRM, BI), and what you see also depends on your role and
permissions. Your sidebar may therefore show fewer items than these docs
cover. The User manual entry at the bottom of the sidebar is visible to
everyone; it opens this documentation.
Recycle bin
Deleted projects, events, shifts, rooms, articles, CRM contacts and master
data can be restored for about 30 days in the
recycle bin. This requires the permission Open
trash. Permanent deletion cannot be undone.
Getting started
What is artwork?
What cultural organisations use artwork for, which modules it has and how this manual accompanies you from your first day to everyday routine
artwork is the shared workspace of a cultural organisation: a theatre,
concert hall, museum or festival uses it to plan its productions, book its
rooms, schedule its staff and manage material, budgets, contracts and
contacts. The benefit comes less from any single module than from how they
connect: an event in the calendar is also the frame for shifts, a project
brings together events, team, budget and documents, and whoever enters a
piece of information once does not have to repeat it anywhere else.
Looking for a specific task? The index
How do I …? takes you straight to the right
place in the module chapter. The module chapters themselves remain the
reference.
Unsure about a term? The glossary
explains each term in one sentence and links to the chapter about it.
The organisation decides which modules are visible and how artwork presents itself externally
artwork has no prescribed interpretation
A project can be a production, an event, a series or a festival. Tabs,
components, contact types, event types and crafts can be named freely. The
use cases show proven set-ups; what matters is
that your organisation chooses a convention and records it during setup.
Rooms and event types are the foundation of the calendar. Without them
there are no events.
An event takes place in a room, can belong to a project and helps
define the project's period. It can carry sub-events, a timeline and
shifts.
Crafts and functions are the foundation of the duty roster. A shift
belongs to a craft, needs functions and is filled with people whose work
profile matches.
A project brings together events, shifts, budget, documents, contacts
and tasks. Its team decides who may see and edit it.
Permissions and modules determine what each person sees. A missing
feature is usually a question of permissions or module visibility, not of
the version.
Getting started (this section): orientation, setup, paths by role,
use cases and the task index. These pages explain little themselves;
instead they lead you to the right place.
Working with Artwork: one chapter per module, each with an
Overview, the individual features and the related settings. This is
where you look things up while working in the software.
Administration: system menu, tool settings, Artwork API and recycle
bin.
Release notes: the changelog of each version with links to the
affected chapters.
The search at the top left finds headings and paragraphs on all pages. If a
search term leads to the wrong page, the index
How do I …? helps.
Getting started
Getting Started
Log in, understand navigation, prepare your account and start using Artwork safely
This chapter takes you from your invitation to your first working day in
Artwork. Your interface may differ from examples in the manual: modules are
enabled organisation-wide and roles additionally determine which data and
actions you can see.
An authorised person usually creates your account and sends an invitation to
your email address. The invitation link is valid for seven days. Open it
promptly and complete the personal details requested. If the link has
expired, Artwork shows a notice page; ask the inviting person for a new
invitation. Use the email address for which the invitation was issued. After
registration you are signed in straight away and land on the dashboard;
there is no separate email confirmation step.
When setting your own password, fixed requirements apply: at least ten
characters with upper- and lower-case letters and at least one digit. Use a
password unique to Artwork and store it in a password manager.
Some organisations use central login instead. The login page then offers
Sign in with … for the configured identity provider. Use your
organisational account; a separate Artwork password may not be required. Once
the session expires, sign in again through the identity provider.
Open your organisation's Artwork address in a browser.
Enter email and password or choose the offered central login.
Use Remember me only on a personal, protected device.
After login, check that your name and expected menu items appear.
Show password lets you check your entry briefly. Do not use it where other
people can see your screen.
If your organisation is connected to an LDAP directory, you sign in through
the same form with your email address and directory password. Accounts with
OIDC use the central sign-in button only; the password form rejects them.
Select Forgot your password?, enter your email address and request the
reset link. Artwork confirms the dispatch regardless of whether the address is
known and limits the number of requests. Open the email and use its link to
set a new password; the same password requirements as at registration apply.
If no email arrives, check the spam folder and spelling, then contact your
Artwork administrator.
With central SSO, the password is managed by the identity provider. Use its
reset process or contact your IT team.
If two-factor authentication is enabled, Artwork asks for a code from your
authenticator app after your password. You can alternatively use a previously
stored recovery code. A recovery code cannot be reused once consumed.
The left sidebar is the main navigation. It can show only icons in compact mode
or icons and names when expanded. Areas with several pages open a submenu:
Calendar, Shift plan, Inventory System, Documents and System.
The main areas appear in this order:
Area
Purpose
Dashboard
Your personal working status for today
Projects
Productions, teams, events, budgets and project components
Calendar
Submenu with Calendar, Planning Calendar and Event Verifications
Shift plan
The duty roster. Submenu with Duty rosters, Shift plan list view, My operational plan, Work time change requests, the approval pages, Week status and Compensation days overview
Inventory System
Submenu with Inventory, Article Planning and Material Issues
To-dos
Personal tasks, checklists and templates
BI Dashboard
Organisation-wide figures and production comparisons
Sources of funding
Grants and cross-project budgets
Users
People, teams, roles and work data
CRM
Contacts and their project relationships
Documents
Submenu with Contracts and Document requests
System
Global configuration for authorised administrators
Recycle bin
Restore deleted objects (permission Open trash)
User manual, Notifications and your profile menu are at the bottom.
User manual opens this documentation in the language of your interface.
A dot on the bell indicates new notifications. In the profile menu, Your
account opens your own account and Logout signs you out.
Which submenu items you see depends on your permissions. An area without
any visible submenu item does not appear at all.
A missing menu item is not automatically an error
The feature may be hidden for the organisation
(module visibility) or
unavailable to your permissions. Ask the responsible feature administrator if you need it for a
specific task. A direct link does not bypass permission checks: without the
required permission, Artwork shows the error page No permission.
After login, Artwork usually opens your personal dashboard. It shows today's
events from your projects, your shifts and individual times, unread notices
received today and a selection of your next tasks. Use its quick links to open
the full feature area.
The dashboard is a personal daily summary, not a replacement for the complete
calendar, task or shift view. See Dashboard.
Open Your account through your profile picture and check:
first and last name,
position, email address and phone number,
profile picture and short description,
application language,
teams and other work details where visible.
A complete profile makes assignments and collaboration easier. Teams and
administrative work data can only be changed by authorised people. See My
account.
You can change your password in your personal account. If enabled in your
installation, set up two-factor authentication, scan the QR code with an
authenticator app and store the recovery codes. Keep those codes outside
Artwork in a protected password manager.
Log out through the profile menu after work, especially on shared computers.
If you suspect unauthorised access, change your password, log out other
browser sessions under
My account and inform your
administrator.
Text stays text: in comments, chat messages, text components,
inventory descriptions, timelines and manufacturer details, HTML is not
interpreted as formatting but shown as text; line breaks are preserved.
Excel exports: cells whose content starts with "=", "+", "-" or "@"
are exported as text so spreadsheet applications do not execute them as
formulas.
PDF exports are downloaded by your browser as soon as they have been
created. artwork cleans up the copy on the server after one day; for a new
state, export again.
Page expired: if you submit a form that has been open for a very long
time, Artwork may report "Page expired". Reload the page and submit again.
The notification centre groups notices by topic and provides direct actions.
In the Settings tab you decide for each notification type whether you
additionally receive an E-mail and a Hint in artwork, and whether
email arrives immediately or as a summary.
Start with enough time-critical messages enabled and adjust after a few working
days. See Notifications.
Set a strong password and, if possible, two-factor authentication.
Open the dashboard, calendar and task overview.
Verify that expected projects, teams and shifts are visible.
Adjust e-mails and hints in the notification settings to your
responsibilities.
Review an existing record before creating new data yourself.
If permissions are missing, describe the concrete work need instead of
requesting general administrator access.
Do not alter live data just for practice
Artwork contains shared production, staffing and financial data. Use a
designated test project or coordinate exercises with the team. Deletions,
acceptances, approvals and commitments can directly affect other people.
Getting started
Setup for administrators
For each module, what is essential for it to work, and what you can add optionally and what it is meant for
This page is the roadmap for the initial setup – and the checklist when an
organisation starts using another module. For each module it first lists
what is essential (without it the module does not work in a meaningful
way), and then what is optional and which use case it is meant for.
All essentials together take about half a day for a medium-sized
organisation; optional items follow step by step as the need arises.
Where the settings are
You will find almost everything on this page in the System menu (only
visible to admins and people with the relevant settings permissions).
Every settings page has an expandable banner at the top, How does this
area work?, describing the intended workflow. The order and dependencies
across all areas are explained in System & administration.
Branding: big logo (login, emails), small logo (header), login
illustration – so that artwork is recognisable as your tool.
Branding
Communication & Legal: organisation name, page title, business and
invitation email (the sender of all emails), links to legal notice and
privacy policy, the season window (basis for BI and season-related
figures).
Communication & Legal
Mail: SMTP access and test email, otherwise invitations and
notifications will not arrive. Mail
Module visibility: hide modules your organisation does not use. They
disappear from the navigation for non-admins; admins still see them.
Module visibility
Optional – what it is for
Adjust the file settings if you want to upload video, audio or larger
files; the default lists cover documents, office files and images.
File settings
Regional formats (number format, currency, date format) define how
numbers, amounts and dates are displayed for everyone.
Regional formats
External user management (LDAP/Active Directory, OIDC/SSO) if your
IT runs a central login.
External user management
Interfaces: API keys for your own reports, webhooks for other
systems, Sage for matching booked invoices in the budget.
Interfaces
Letterhead for the per diem statement of artist residencies (under
Communication & Legal).
At the top of the Tool Settings page you find the Installed
version with a link to the changelog. This shows whether an update is
already live on your installation.
Create permission presets or check the supplied role presets (Basis,
Production management, Disposition / room planning, Duty roster
planning, HR administration, Accounting / controlling, Contract &
document administration, Warehouse / inventory, Artist relations / CRM,
Box office / admission). This turns every invitation into the question
"which role preset?" instead of "which 80 checkboxes?". There is no
role preset for system administration; that is what the admin role is
for.
Roles & permissions
Invite users – by email, the invitation is valid for 7 days; if
needed, with teams and permission preset right away.
Accounts & invitations
At least two admins, so that nobody gets locked out.
People who leave the house are deactivated instead of deleted:
permissions and all assignments to projects and shifts are kept.
Deactivate account
Areas and rooms: areas as a building, site or floor; rooms with
colour, Relevant for disposition (only these rooms appear in
calendars, the duty roster and exports) and room admins (individual people or whole teams) who
answer booking requests. Then
Sort rooms, because the order applies in all calendars.
Rooms, areas & booking access
Event types with colour and abbreviation (performance, rehearsal,
setup, blocker …). They shape the calendar tiles, the filters and shift
planning. Event types
Decide on the booking model: should everyone book directly
(Events always bookable directly), or should room admins approve
booking requests? Standard values
Optional – what it is for
Activate event statuses (requested, confirmed, cancelled …) if the
confirmation state of an event matters more than its type – tiles can
then be coloured by status.
Event statuses
Event properties (supplied are Publikum, "audience", and Laut,
"loud") to mark events and filter the calendar by them.
Event properties
Room categories and room attributes (stage, rehearsal stage, grand
piano, dance floor …) as filters for "find free rooms".
Capacity per room if you want to evaluate utilisation, and
Adjoining rooms as information on the room. There is no automatic
check for loud events in an adjoining room.
Verification mode per event type if certain events (such as
performances) are to be approved for content.
Event verifications
Enable the planning calendar (module visibility and permissions) if
scheduling staff are to pre-plan seasons without colleagues seeing the
drafts. The permissions are separate: View planning calendar only
allows viewing, Plan directly in the planning calendar allows
creating, and Edit planned events allows changing, moving and
deleting. Planning calendar
Switch off Project creation possible when creating events in the
calendar settings if projects should not be created in passing from the
event dialog. Events can then only be linked to existing projects.
Import holidays & school holidays so that they are visible in the
calendar and duty roster and count as special days in working time.
Holidays & school holidays
Activate the admission field if admission times are maintained on
the event.
Day remarks column for notes on the whole day (such as house
information for all crafts).
Calendar settings
Set the hidden hours of the daily view: Hidden from and Hidden
untilComing with the next update delimit the part of the day that the
daily view hides on days without an event in this range. For performances
with late-night shows until 02:00 and a start at 08:00, enter 02:00 under
Hidden from and 08:00 under Hidden until.
Timeline presets for recurring daily schedules (get-in, admission,
start, end).
The detailed path with stages, visibility, documents and print layouts is
described in Setting up the project view.
Essential
Check the tab settings: the default tabs (project information,
schedule, to-do lists, shifts, budget, comments) can be used right away;
decide whether you divide tabs by department or by phase. Create tab
from template restores missing default tabs.
Tabs & components
Project statuses (in planning, confirmed, cancelled …) so that lists
and calendars can filter by them; mark planning statuses as Project
counts as "in planning". The mark presets the toggle for planned events
in the project's event entry; it does not change existing events or
events created in the calendar.
Project statuses
Optional – what it is for
Categories, genres, areas as project properties if you evaluate by
division or want to colour tiles by main category.
Project creation settings: which fields are asked for when creating
a project (status, project manager, artists, budget deadline, cost unit)
and whether CRM contacts in the project team are allowed.
Project creation settings
Project roles (director, production manager …) as labels in the team
– they do not grant permissions.
Project roles
Custom components (text fields, select fields, checkboxes, folders)
for information your organisation needs for each project.
Print layouts to hand project data to external partners as a PDF
without revealing internal content.
Print layouts
Project overview builder to define the columns of the project list.
Artist residencies (general defaults for per diem and breakfast
deduction) if you handle guest performances with travel and hotel
planning. You maintain the accommodations for them on the
Accommodations page, not with New contact in the CRM.
Accommodation and room types
BI settings (audience categories, BI fields, BI tags) if you want to
record visitors, revenue and utilisation.
The detailed path in three stages – staffing shifts, calculating working
time, checking rules – is described in
Setting up the duty roster.
Essential
Functions first (master, specialist, assistant …), because every
shift asks for slots per function and the craft dialog only offers
existing functions.
Functions and qualifications
Crafts with abbreviation and colour (sound, lighting, stage,
admission …), usually along the house's departments; per craft the
functions and who may plan the craft. Crafts
Work profiles of the people: May be assigned to shifts, crafts and
functions. Otherwise nobody appears in the workforce panel.
Work profile
Permissions: Plan shifts and Commit duty rosters for the
planners, plus the release in the respective craft.
Optional – what it is for
Time presets and shift templates (with template groups) if the
same shifts come up again and again – one click instead of ten dialogs.
Templates
Working-time planning: work time patterns (daily target per
weekday) and user contracts (vacation days, days off, overtime rule),
assigned to people under Contract & working hours. Only then are there
time accounts, target/actual, overtime and key figures. If you do not
need this, switch off Work time accounting.
Work time patterns & contracts
Rules & violations if you want to track working-time law and
collective agreements: daily and weekly maximums, rest periods, days off,
Sunday work – with Create legal default rules as a starting point.
Violations appear in the duty roster and in the overview of substitute
days off.
Rules & violations
Shift groups if rest periods between shift types (such as evening →
early) are to be checked; a prerequisite for the corresponding rule.
Night work period so that night hours are counted separately.
Day services (key service, standby) that are assigned to a person
for a day without a shift.
Approval workflow if craft managers submit their weeks for approval
and a second person approves them; plus request deadlines per craft.
Committing & approval
Shift confirmation by employees if people are to accept or decline
their duties.
Project assignments to assign people to a production bindingly or as
a wish; can be switched off if you do not need it.
Allow overbooking, sorting by first or last name, calendar feed
with or without provisional shifts according to your house rules.
Miscellaneous toggles
Properties first (lumens, weight, serial number, condition … with
data type), then categories and subcategories to which you assign the
matching properties – so a lamp asks for lumens and a shoe for its size.
Inventory settings
Check the statuses (ready for use, defective, on loan …) and their
colours; only the status ready for use counts as available quantity.
Permissions: Create & edit inventory for maintaining the
catalogue, Inventory disposition for article planning and material
issues. Without Inventory disposition, these two menu items are
missing.
Optional – what it is for
Tags and tag groups for cross-sections across categories
(production, location, ownership).
Material sets for packages that are always issued together (projector
set, microphone case). Material sets
Manufacturers as CRM contacts of the contact type Manufacturer if
you want to record them on the article and filter by them.
Inventory number prefix and Detailed articles always with quantity
1 if you keep individually tracked articles with numbers.
Maximum size per article image (MB) for article photos.
Check and extend the contact types. The system contact types for
artists, accommodations, manufacturers, freelancers, service providers
and users are supplied. You create further ones such as agency, company
or promoter yourself. Decide per contact type which fields are
mandatory, shown in the list and filterable.
CRM settings
Optional – what it is for
Confidential property groups (bank details, terms) with group
permissions so that only finance can see them.
Import from Excel/CSV to take over existing address data.
Import contacts
Enable external access (System → External access, admins only)
so that companies and artists fill in their data and project inquiries
themselves; this requires the permission Invite externals and the tab
template Production inquiry. If externals should upload files, also
switch on Allow file upload for external accesses.
External access
Allow CRM contacts in the project team to list external partners as
team members with a role.
Only if you store contracts in artwork: contract types, company
forms and currencies in the project settings, so that the contract
form offers suitable values.
Other project-related master data
Sources of funding with categories if grants are assigned to
projects. Sources of funding
Ask for the budget deadline when creating a project if you want to
use the budget export by deadline. The tab only appears in the export
of the project list once this creation setting is on, and only for people
with Global budget accessComing with the next update, which the export
requires.
Checklist templates for recurring routines (premiere, guest
performance, get-out) with relative deadlines.
Checklist templates
Notifications: each person sets E-mail and Hint in artwork
per notification type themselves; as an
admin you take care of the mail account and can set a central banner
with Notification to all. Notifications
BI: season window, BI tags on event types and the BI component in a
project tab, so that the dashboard shows values.
BI dashboard
Walk through the whole process once with a test project: create an event, fill a shift, issue material, upload a document.
Check with a person without admin rights what they see – only then do permission presets become truly visible.
Show the display settings for the calendar and the duty roster to the different roles; they are personal and often overlooked in the introductory session.
The guided path for admins – in three stages from "plan and staff shifts" via time accounts to rules and violations, with everything you can leave out
The duty roster is the module with the most settings. This page walks
through the setup in the order in which the parts build on each other.
Each stage can be used on its own: a house can plan productively after
stage 1 and switch on stages 2 and 3 later or never.
Stage
What you can do
What you need
1 – Plan and staff shifts
Create shifts, assign people, commit, send out operational plans
Functions, crafts, planning rights, work profiles
2 – Calculate working time
Target and actual hours per week, time account, overtime, work time overview
Work time patterns, user contracts, assignment per person
3 – Rules and violations
Check working time law, collective agreements and house rules, manage substitute days off
Stage 2 (contracts), rules, shift groups where needed
In addition there are features you can switch on at any time, regardless
of the stage, such as templates, the release workflow or shift
confirmation. They are listed under Available at any time.
Where the settings are
Everything on this page is under System → Shift settings (permission
Shift settings) and in the person's profile under Users (permission
HR administration). The Shift Settings tab is a long page. At the
top are the permission model, shift confirmation, the release workflow
and the night work period, below them Crafts, Global
qualifications, Craft functions and Time presets for
shifts. At the very bottom follow sorting, the shift plan
subscription, overbooking, project assignments and Work time
accounting. The other tabs are Day Services, Work Time
Pattern, shift groups, User Contracts, shift templates,
Shift preset groups, Rules & violations and Open violations.
If several people maintain the settings
In simple mode, the permission Shift settings opens all tabs. Admins
can switch the Permission model at the top of the Shift Settings
tab to granular permissions. Then a separate read and edit permission
decides per tab, for example so that HR only maintains user contracts
and work time patterns.
Permission model
After this stage you can create shifts, assign people by drag & drop and
commit weeks. The order matters: the craft dialog only offers functions
that already exist.
Create functions. In the Shift Settings tab, further down in the
Craft functions section, with New qualification: name and icon,
for example Master, Specialist, Assistant, Rigging. Functions are
the slots a shift offers ("2 × specialist, 1 × master"). artwork ships
Mitarbeiter (worker) and Meister (master); Mitarbeiter cannot be
deleted because it serves as the fallback function.
A function applies to every craft you assign it to. Create it in
general terms (Specialist), not per craft (Lighting specialist).
Is taken into account for new shifts has only a small effect: it
controls the function columns in a project's personnel plan export. The
shift dialog always offers all functions of the craft.
The drag & drop order sets the order in shifts and in the workforce
panel.
Create crafts. At the top in the Crafts section with New
Craft. Crafts usually follow the house's departments: stage, lighting,
sound, video, props, make-up, costume, front of house.
Name, abbreviation (at most four characters) and colour.
Abbreviation and colour appear on every shift card.
Universally applicable for special cases: people of this craft can
be assigned to shifts of all crafts. Typical for apprentices, floaters
or a general event technology team. The person still needs a matching
function in the other craft; the functions they hold in the universal
craft count.
Days until notification if shift not fully staffed can stay at 0.
Assign functions to the crafts. In the craft dialog under
Functions, select the functions used in this craft. Only these can be
requested in the craft's shifts.
Decide who may plan. Planning requires two things:
the permission Plan shifts on the person (through a permission
preset such as Duty roster planning or individually), and for
committing also Commit duty rosters;
the release in the craft under Shift planning permissions: Can
be scheduled by all shift planners (default) or Allocable to a
limited extent with a list. The list only offers people who already
have Plan shifts. A restricted craft without entries can only be
planned by admins.
The craft manager is optional: they are highlighted in the workforce
panel and receive notifications when no planner is listed. You add them
in the same dialog under Craft manager, when creating the craft or
later via Edit.
Make people assignable. For every person under Users → person →
Work profile:
Switch on May be assigned to shifts.
Assign the crafts under Can be used in the following crafts.
Under Craft functions, switch on the functions the person can take
on in each craft.
Freelancers and service providers have the same Work profile tab on
their profile page. Crafts are assigned to people only here; the craft
dialog has no list of people.
Trial run. Create a shift in the duty roster (craft, time, demand per
function), drag a person from the workforce panel onto it, commit. If
this works, stage 1 is done.
Creating shifts ·
Assigning staff
A person does not appear or cannot be assigned
For a person to be dragged onto a shift, all of this must be true: May
be assigned to shifts is on; the craft is assigned to the person (or
they belong to a universally applicable craft); the function is switched
on for the person in this craft; the craft has the function; the shift
still has a free slot for this function. Without a craft the person
does not appear in the workforce panel at all.
Without a work time pattern, artwork shows "–" in the calendar week column
and the hint Work time pattern missing. If you do not want to keep time
accounts, switch off Work time accounting at the
very bottom of the Shift Settings tab. Then:
the calendar week column shows only the planned hours of the week;
the time account, target hours, overtime, the nightly booking, the
Work Times and Overtime tabs in the profile, the Work Time Pattern
tab in the shift settings and the work time overview export are
removed;
stored patterns, contracts and time accounts are kept. When you switch
it back on, artwork continues from the next day; days while the
calculation was off are not booked afterwards.
With this stage every person gets a target per day and week that is
compared with the planned and booked hours. It requires stage 1 and
Work time accounting switched on.
Create work time patterns.Work Time Pattern tab: per pattern a
name and the daily target in hours per weekday (not clock times), for
example Full time 39 h with Mon–Fri 7:48 or Part time 20 h. A pattern
describes how many hours are owed on which weekday.
Create user contracts.User Contracts tab: templates for the
contract terms, for example TV-L full time, NV Bühne, Temporary
staff. A contract contains among other things full and half days off per
week, vacation days, the special day rule, the compensation period, the
three-month average, season key figures and the overtime rule with its
deadline.
Assign the package to the person. Under Users → person → Contract &
working hours with Plan change: from a date, choose a contract
(template or individual values) and a work time pattern (or individual
weekly hours). The previous period ends automatically on the day before.
This way artwork also handles contract changes during the season
correctly.
Contract & working hours
Check. In the duty roster the calendar week column now shows the
difference to the target, the person tile shows the time account. Booking
runs every night at 23:59; the time account therefore shows the state up
to yesterday.
Check the Night work period (default 22:00–06:00): hours in this
window are booked as night hours.
Take over opening balances at go-live via Work Times → Book working
hours in the profile.
A person without a work time pattern has no target and no booking; a
person with a pattern but without a contract has a time account but no
overtime rule.
With this stage artwork checks working time law, collective agreements
such as TVöD or NV Bühne and your own house rules while assigning, and
manages substitute days off. Rules are attached to contracts: on a given
day a rule only applies to people whose contract valid on that day is
assigned to the rule Coming with the next update. Without stage 2, no rule
applies.
Start with the legal default rules.Rules & violations tab →
Create legal default rules. In the dialog, all nine rules and all
user contracts are preselected; you can deselect individual ones. So
create the user contracts first (stage 2). artwork creates the selected
rules as active:
Rule
Value
Legal daily maximum
10 h
Legal weekly maximum
48 h
Legal rest period
11 h
Legal maximum of consecutive working days
6
Sunday work (substitute rest day)
1 substitute day off within 14 days
Work on a special day (substitute rest day)
1 substitute day off within 56 days
Legal free Sundays per year
15
Legal weekly average
48 h over 24 weeks
Legal night work maximum
8 h
Clicking again creates nothing twice; it only assigns existing rules to
the contracts that are still missing.
Add your own rules.Create new rule for collective agreements and
house rules: rule type (cannot be changed later), limit, period, default
substitute days off and deadline, warning colour.
Assign contracts and set recipients. Under Assign contracts,
choose the contracts the rule applies to; under Notify on rule
violation, the people who are informed.
Meet the requirements of individual rule types.Rest time between
shift groups needs shift groups set on the shifts. Night work rules
use the Night work period. The overtime deadline rule needs work time
accounting switched on.
Violations appear in the duty roster as a coloured marker, under Open
violations and in the Compensation days overview.
The Rules & violations and Open violations tabs also require the
permission Plan shifts.
Freelancers and service providers are not checked.
Small house: one craft Technology with the functions Specialist
and Assistant, all planners may plan, work time accounting off. Set up
in an hour.
House with apprentices: a craft Apprentices, Universally
applicable, with the function Assistant; apprentices can then be
assigned to assistant slots in every craft.
House bound by collective agreements: stage 2 with one contract per
pay group, stage 3 with the legal default rules and additional
agreement rules assigned to the same contracts.
The guided path for the project builder – components, tabs, visibility, documents, print layouts and project list, with everything you can leave out
The project view is a building kit: admins decide which tabs exist, which
building blocks (components) sit on them and who sees what. The settings
apply to all projects. This page walks through the setup in the order in
which the parts build on each other.
Where the settings are
Everything is under System → Projects (permission Project
settings) in the tabs Component Settings, Tab Settings, Print
Layout Settings and Project overview builder.
Create building blocks: text fields, drop-downs, checkboxes, multiple choice, titles, links, folders. They are only created here; they become visible once they are placed.
Tab Settings
Build the project page: create tabs, drag components into them, fill sidebars, set visibility per tab.
Print Layout Settings
Arrange components for PDF exports.
Project overview builder
Arrange components as columns of the project list.
The special components that ship with artwork (calendar, shifts, budget,
project team, artist residencies, BI key figures …) bring their own logic
and cannot be deleted.
A new house has six ready-made tabs: Project information,
Schedule, Checklists, Shifts, Budget and Comments.
With these, the project view can be used without further setup.
Check which tabs your house does not need and delete them. Create tab
from template brings missing default tabs back at any time.
Decide which tab opens first when a project is opened (Default
switch on the tab). Without a choice it is the first tab the person may
see.
Create components.Component Settings → Create a new component:
choose the type (cannot be changed later), give it a name to find it
again (it does not appear in the project) and fill in the fields: label,
pre-filled value, Placeholder, the Options for drop-downs and, if
needed, Allow multiple selection, font size and Section bar for
titles.
Create tabs.Tab Settings → Create tab: name and visibility. Put
components from the palette on the right into the tab by drag & drop or
with the plus on the component. Group related items in a folder
(collapsible section) and write hints into the Tooltip text of the
placement.
Use the sidebar. Every tab can have a narrow sidebar on the right with
its own sub-tabs. It suits information you need alongside the main area,
such as the project team or shift information. Folders cannot go into the
sidebar.
Check with a real project – with a project team member with and
without write access.
The same component may sit in any number of tabs. In each tab it shows
the same record of the project: what someone writes into the field
Technical requirements in the Technology tab appears immediately in
the Production tab. Each piece of information is thus maintained in
exactly one place, even when several departments need it.
Especially useful with department tabs and restricted visibility:
shared fields sit in several department tabs, confidential ones in only
one.
The palette shows with Used: N how many tabs a component is in.
Permissions belong to the component, not to the placement. If you need
different rights in one place, create a second component.
Folders share their content too: the same folder shows the same
components in every tab.
Visibility works on three levels that must all apply:
Project access – being in the project team or holding global
project rights.
Tab visibility – Visible for all or only selected users and
teams. Restricted tabs cannot be opened through a direct link either.
Component permissions in the component settings – No further
restriction, Visible to everyone with project access, but editing
is additionally limited to … or Only visible to the following ….
They only restrict and never extend; editing always requires write access to the
project.
Admins see all tabs and components. For people with Write permissions
for all projects only the editing restriction of the components they can
see is lifted. Only visible to the following … and the tab visibility
apply to them as well. artwork also enforces these rules on the server:
anything a person may not see is never sent to their browser.
The File upload component (called Documents up to version 1.8)
shows the files of the tabs you select when placing it (Only include
current tab or Select tabs). Every placement in a tab or folder is
its own upload area. A new file first appears in all areas that
include the tab in which it was uploaded. This lets you protect sensitive
files:
The restricted tab Administration has a File upload component that
only includes this tab. Contracts and calculations uploaded there appear
in no other tab.
The general tab Project information has a File upload component that
includes Project information, Technology and Press, but not
Administration.
All Documents shows all files of the project from the tabs the
person may see. All Comments and All Checklists behave the same
way.
The tab selection of a placement can be changed via Edit (row
Shows documents from tabs).
Via Upload settings on the placement you limit, per area, the
allowed file types, the maximum file size and the maximum number of
files per project. The limits apply in addition to the
file settings and also
to external accesses.
In the project, the distribution can be changed per file when there are
several upload areas: before uploading via New files visible in,
later on the file via Visible in. A badge on the file shows Only
here or the number of other areas. This requires write permission in
the project.
Restricted tabs stay protected
If a File upload component includes a restricted tab, that tab's files
are only shown there to people who may also see the restricted tab.
Everyone else only sees the files of the other tabs. Downloading a file
also requires access to one of its tabs (the tab of the upload or the
tab of an area in which it was explicitly made visible), unless the
file was explicitly shared with the person.
Comments and Checklist work the same way: when placing them, you
choose which tabs they collect content from, and each person only sees the
content of the tabs they may see. This also applies to components inside
folders. To change the selection, remove the component and place it again.
When a tab is shared with external people, they see all externally
displayable components of this tab, regardless of internal permissions.
Create a separate tab for this, most easily via Create tab from template
→ Production inquiry.
External access
Print layouts turn project data into a PDF. Several standardised exports
for fixed purposes have proven better than one general layout. Each layout
stays short, and the person printing does not have to choose anything.
Create the layout.Print Layout Settings → Create print layout:
name, description and the number of columns for the header (1–5), body
(1–3) and footer (1–5). The column counts are fixed after creation. Use
one column for the body: with several columns the large components that
do not fit into a sidebar either cannot be used, for example Shifts,
Bulk Event Create Component, Artist residencies, Project material
issue, Business Intelligence and the All … lists.
Arrange components. Drag components from the palette into header,
body and footer; the body adds a new empty row automatically. Header and
footer only take the small components (your own components and
everything that also fits into a sidebar, such as Project Title or
Project period); the large ones belong in the body. Header and
footer can also carry free notes, for example "Internal version". The
header offers one note field per column, and so does the footer
Coming with the next update.
Release it. Switch on Should this print layout be available?. Only
active layouts can be chosen in the project.
Print. In the project, choose a layout via the printer icon in the
header and click Print. artwork opens a window with the browser's
print dialog; choose Save as PDF there. An active pop-up blocker
prevents the window.
Your own components (except folders) and most special components can be
printed. Components with a tab selection (File upload, Comments,
Checklist), Calendar, Budget (the table) and the Sage invoice
overview cannot; for lists, use the variants All Documents, All
Comments and All Checklists.
The print layout palette shows newly created, changed and deleted
components immediately Coming with the next update.
Print layouts respect visibility
A print layout only outputs what the printing person may also see in the
project view. Components set to Only visible to the following … and
components that only sit in tabs invisible to that person stay empty in
the PDF. All Documents, All Comments and All Checklists only
contain content from tabs the person may see. The same layout can
therefore be more or less complete depending on who prints it.
The Project overview builder sets the columns of the project list for
all users, for example genre, project management or a drop-down
Contract status. Project title and actions are fixed; each component can
appear once as a column. Columns from components with restricted
visibility are only shown to people with the right.
Project overview builder
A tab is visible to nobody: restricted, but without selected people
or teams. The tab card then shows No access configured.
A field is empty in one tab and filled in another: they are two
different components with the same label. The number under Used
shows whether a component is placed more than once.
A document has "disappeared": it is in a tab that the File upload
component does not include, in a tab the person may not see, or it was
limited to other upload areas via Visible in.
Deleting a component also removes all values already entered in
projects.
For each typical role in your organisation, the most important pages, the first tasks and the settings that help
artwork shows each person only what their permissions and the enabled modules
allow. That is why getting started looks different for room scheduling than
for someone who only reads their operational plan. Pick the page closest to
your job – many people in an organisation combine two roles and read two
pages.
Every role page has the same structure: Your most important pages, The
first tasks, Settings that help you and Permissions you need. The
permissions are named after the role preset from the
permission presets,
so your administration can grant them exactly like that.
If a menu item is missing
A missing area is almost always a missing permission or a module that is
switched off for your organisation. Tell your administration the specific
task, not a blanket "admin rights" – see
Getting started.
Getting started
Room scheduling
Book rooms, create events and series, answer requests and plan seasons ahead
You plan what takes place when and in which room. Your tool is the calendar;
the project gives you the context, and the duty roster follows your events.
The setups Weekly scheduling view and Season overview under
Recommended settings.
Repeat event and Project status on the tiles, so you recognise
series and uncertain projects immediately.
Show planned events to see the planning calendar and the calendar in
one picture.
Switch off Hide empty rooms so that free rooms stay in the grid, and
filter by the event property for loud events (the supplied one is called
Laut, "loud") when you are looking for a room for a loud event. Filters
Project search in the function bar to edit only one production in its
period.
Role preset Disposition / room planning: Plan events directly (or
Request room occupancy if room admins approve), for provisional planning
View planning calendar (view only), Plan directly in the planning
calendar (create planned events) and Edit planned events (change, move,
delete, confirm), and if applicable Room
administration and Event settings if you maintain rooms and event types
yourself. Details under
Calendar & events.
Typical pitfalls
An event has "disappeared": check the filter, Hide empty rooms and
the period, then the recycle bin.
Events without a room after a cancellation: the amber chip in the
function bar lists them.
Getting started
Duty rostering
Create shifts, assign staff, commit calendar weeks and keep an eye on working time rules
You staff the events of your organisation or your craft. The duty roster is
your main view; events come from the calendar, people and their contracts
from user management.
Weekly grid with rooms and days, the workforce panel below: The duty roster view
Shift plan → Shift plan list view
All shifts as a list, remaining demand at a glance
Shift plan → Week status
Which calendar week is open, requested or committed per craft: Week status
System → Shift settings → shift templates
Recurring shifts as a template; requires the permission Shift settings: Shift templates
Shift plan → Work time change requests
Handle correction requests from staff
Shift plan → Shift plan Change list
What has changed in committed weeks. The menu item only appears with an active release workflow and only for approvers and admins: Committing & release
Shift plan → Compensation days overview
Open and granted compensation days of all people; requires Plan shifts: Rules & violations
Set up the workforce panel. Craft filter on your crafts, Group by
function on, and if needed Show freelancer.
The workforce panel
Create a shift – craft, time, break, demand per function – on the event
or freely in the room cell. Creating shifts
Assign staff by drag & drop and read the conflict check: availability,
double booking, rule violations.
Assigning staff
Work through the remaining demand with Only show shifts that are not
fully staffed and the traffic light in the craft row of the workforce
panel (display setting Show staffing per craft).
Commit the week – or, with the workflow active, submit it for approval.
Changes are traceable afterwards.
Committing & approval
Distribute the plan: PDF notice (rooms by day or staff overview) and the
staff's calendar subscription.
Exports
Role preset Duty roster planning: View duty rosters, Plan shifts
(entered as planner in the respective craft), Commit duty rosters, Manage
availability of others for other people's availability, and View hour
accounts for time accounts. Details under
Duty roster.
Typical pitfalls
A person is missing from the workforce panel: their work profile needs
May be assigned to shifts and the assignment to your craft.
You may not edit a shift: you are not entered as planner of this craft –
Crafts.
Target and actual hours do not match: the person has no work time
pattern or contract –
Contract & working hours.
Getting started
Production management
Run a project from creation to settlement – team, events, budget, documents, contacts
You are responsible for a production or a series. Your home is the project:
it bundles everything that belongs to it, and you decide who in the team may
see and change what.
Create the project – as a single project or in a project group
(festival, series). Creating a project
Put the team together and set permissions per person: write permission,
budget access, project management, project roles.
Project team
Create events – individually in the calendar or many at once in the
schedule; the project period is calculated from them.
Creating several events together
Build the budget, ideally from a template, and have main positions
verified.
Table structure
Role preset Production management: Create own projects, Can be
project manager, read or write permissions for other projects depending on
your organisation's rules, contract permissions as needed, and budget access
in the project team for budgets. Details under
Projects and
How project permissions work together.
Typical pitfalls
A team member cannot see a tab: check the tab or component visibility in
the tab settings.
The budget is missing: budget access in the team is a separate checkbox.
The project period is wrong: it follows the events with a
period-relevant event type – Event types.
Getting started
Staff
Read your own operational plan, enter availability and absence, confirm shifts, complete tasks
You work in a craft or a department and use artwork mainly to know when and
where you are assigned, and to tell your organisation when you are
available. Much of this also works on your phone.
Check your profile: name, phone, photo, language – and whether your
e-mail address should be visible to others. My account
Set up notifications: which notifications also arrive as an
E-mail (immediately or as a summary) and as a Hint in artwork.
There is no push message to your phone.
E-mail & push
Enter availability and absence: type Available or Absent, for a
day, a period or repeating weekly. You do not choose a kind of leave here;
an absence counts as not available in planning. Planning sees this
immediately.
Subscribe to your own operational plan, so your duties appear in your
phone or Outlook calendar. Calendar subscription
Accept or decline shifts if your organisation uses shift confirmation,
and request a work time change if needed.
Accepting or declining shifts
Enter your own times without a shift (office, training, travel day)
if you have the permission Enter own individual times: in the
operational plan via the plus on the day, once or as a series, from today
on. The entries apply immediately, without approval.
Entering your own individual times
Role preset Basis (all staff): View own roster, Subscribe to roster
calendar, Read all projects, Request room occupancy, View day
remarks, View contract modules and View inventory. If applicable,
Accept or decline shifts and Enter own individual times are added;
neither is part of the role preset, both are granted individually. You
need nothing more for your own work; if you plan, read
Duty rostering.
Typical pitfalls
A shift is missing from your operational plan: depending on your
organisation's rules, provisional shifts may be hidden until the week is
committed.
You cannot see a project: without Read all projects you can only
open projects whose team you belong to; ask the production
management.
Your hours are wrong: with the permission Enter own individual times
you enter individual times (office, training) yourself, otherwise the
planners do. Past days are always maintained by the planners. For a
shift, you request a work time change.
Getting started
Technical & stock
Maintain inventory, issue material for productions, check availability and read your own craft in the duty roster
You are responsible for technical equipment, stock or a workshop. artwork
helps you know what is where and when, and reserve material bindingly for
productions and external parties. On top of that, you often look at the
duty roster of your craft.
Hide article images in overview if you prefer to see many rows;
Show inventory number as name for individually tracked articles.
Only planned articles in article planning to see only material that
is in use.
Only overdue returns in the external issue log.
In the duty roster, the setup Staff only if the event tiles get in
your way –
Recommended settings.
In the duty roster, the filter Only show shifts that are not fully
staffed. The calendar does not have this filter; there Show
shifts only displays the shifts.
Role preset Warehouse / inventory: Create & edit inventory,
Inventory disposition (opens the menu items Article Planning and
Material Issues); for settings (categories, properties) the
Inventory settings permission. For the duty roster, View duty rosters or,
as head of a craft, Plan shifts. Details under
Inventory & material issues.
Typical pitfalls
Availability is 0 although there is stock: only the quantity in the
default status (shipped as Einsatzbereit, ready for use) counts as
available.
An article does not ask for the right property: the property is not
assigned to the category – Inventory settings.
A manufacturer is missing from the selection: manufacturers are CRM
contacts of the contact type Manufacturer.
Getting started
Administration & finance
Review budgets, assign funding, file contracts, request missing documents and evaluate working times
You work in accounting, controlling, contract administration or HR
administration. Productions create their budgets, contracts and working
times in artwork; you review, approve, assign funding and evaluate – without
figures having to be copied back and forth between spreadsheets.
Define the budget structure: names of the first columns, centrally
maintained accounts and cost centers, a budget template from a clean
project budget. Budget settings
Review budgets: have main positions verified (the requested person
confirms with Mark as verified), commit positions, mark the
budget-relevant column. Verifying
and committing record the state but do not lock any cells; later changes
are highlighted in red. Only Lock in the column menu prevents them
technically. All three require the permission Remove verifications &
locks.
Verifying & committing
Assign Sage bookings if the interface is active: drag bookings that
were not assigned to a row automatically into the budget rows and use the
Sage invoice overview in the project. You only see the blocks with the
open bookings with the permissions Project Sage data and Global Sage
data.
Sage integration
Create funding and release it to the funded projects, then assign
budget items to the source; set reminders for expiry and remaining budget.
Projects & budgets
File contracts with contract type, amount, artists' social security
(KSK) and tax details and targeted access; pass missing paperwork to the
production as a document request.
Uploading a contract
Evaluate: budget export by deadline for the premieres of a period, BI
dashboard for the season, contract list as Excel.
Assign contracts and work time patterns to each person under
Contract & working hours; only then are there target hours, actual
hours and overtime.
Contract & working hours
Book hours retroactively, credit or deduct them, and check the time
account. Work times
Role presets Accounting / controlling (budgets and sources of funding),
Contract & document administration (contracts and document requests)
and HR administration (profiles, contracts, working times). Access to
all project budgets requires Global budget access; otherwise budget access
in the respective project team. Sage data has its own permissions. Details
under
Budget & funding,
Documents & contracts
and Staff.
Typical pitfalls
A budget is missing from the list: budget access is a separate checkbox
in the team per project, or Global budget access is required.
The budget export is empty: the projects have no budget deadline.
The tab Budget export by deadline is missing under Export
project list: the creation setting Budget deadline is off, or you
lack Global budget accessComing with the next update. The Project role
overview requires Read all projects.
Getting started
Administration
Set up your organisation, grant permissions, look after modules and interfaces and help colleagues get started
You have the artwork admin role or the settings permissions of
individual areas. You always see everything – which is exactly why it pays
to look through the eyes of a role without admin rights.
The specialist areas: events, calendar, rooms, shift settings, projects, inventory, CRM settings, budget, sources of funding, to-do lists, external access: System menu guide
Users
Accounts, invitations, freelancers, service providers, teams, permission presets – Users & teams
Users → Person → User permissions
Permissions per module, applying presets, copying the permissions of another person: Roles & permissions
Recycle bin
Restore deleted items before they disappear for good after 30 days – Recycle bin
System → Tool Settings, line Installed version
Which version runs on your installation, with a link to the Changelog. If the changelog lists a newer version, it is not live on your installation yet
Create permission presets or review the role presets, and use a test
person without the admin role to check what they see.
Role presets and permission presets
Invite users, with teams and permissions right away (quickest via a
permission preset). The work profile is not part of the invitation: you
maintain it afterwards in the person's profile, otherwise they cannot be
assigned to shifts. Accounts & invitations ·
Work profile
Hide modules your organisation does not use, and check the file
rules. Module visibility
Test the mail setup and get to know Notification to all for
organisation-wide information. Mail
After every update, read the changelog and inform the affected roles;
notes for admins are listed there separately.
The How does this area work? banners on most settings pages; they
name dependencies between areas.
The Permissions explained page (in user management) as a printable
reference of all permissions for training.
Deactivate account instead of deleting when someone leaves the
house: the person can no longer log in, their assignments are kept.
Deactivate account
Same rights as another person when no role preset fits. By default
only the missing permissions are added; only with Also remove
permissions this person does not have are they copied 1:1.
The Change history of each person's permissions when questions come
up.
Set the season window deliberately at the change of season – it
drives BI and key figures.
The artwork admin role includes all permissions. For specialist
administrators without full access, there are settings permissions per area
(Event settings, Calendar settings, Room administration, Shift
settings, Project settings, Inventory settings, Manage CRM, Tool
settings, HR administration …) – see
System settings and interfaces.
What you do not see as an admin
Personal display settings, saved filters and notification preferences
belong to each person. If someone "sees nothing", first check permissions
and module visibility, then filters, period and Hide empty rooms in
the view in question – the
display settings
are the most common cause.
Getting started
Use cases
Cross-module workflows from the everyday life of a cultural venue, step by step with links into the module chapters
The module chapters explain each function on its own. In daily work, however,
several modules interlock: a guest performance needs the calendar, project,
duty roster, CRM and inventory at the same time. The use cases walk through
such workflows once from start to finish – as a starting point you adapt to
your organisation.
Every use case has the same structure: Situation, People and
permissions, Workflow with links, Pitfalls and Variants. If
your organisation handles a workflow differently, the relevant section of the
module chapter is the right place to look things up.
Getting started
Planning a performance with shifts
From the event in the calendar through the shifts per craft to the committed duty roster and the notice board printout
A production has three performances in the Main Hall. Each performance
needs stage, lighting, sound and front of house with fixed staffing; the
technical team also has a set-up on each performance day. In the end,
everyone should know when they are on duty, and the plan should hang on the
notice board.
Create events. In the calendar or in the project's schedule, create the
three performances with the event type Performance and the set-up with
Set-up, each in the Main Hall and assigned to the project. A series is a
good fit for the run of performances.
Creating events ·
Event list in the project
Create shifts. In the shifts tab, create the shifts per craft on each
event with times, break and demand per function. With three identical
performances, a template group ("Performance Main Hall") covering all
crafts pays off – one click instead of twelve dialogs.
Creating shifts ·
Planning many shifts with templates
Assign staff. In the duty roster, open the week, set the craft filter
and drag people from the workforce panel onto the shifts. The conflict check
reports absences, double bookings and rule violations; the traffic light
in the craft row (display setting Show staffing per craft) shows what
is left.
Assigning staff
Close the remaining gaps. Switch on Only show shifts that are not fully
staffed or use the list view. If someone has declined, an icon with
the tooltip Find replacement for … appears next to the decline icon on
the assignment; it suggests suitable free people.
Find replacement
Commit. Per calendar week and craft, Commit duty roster; with the
workflow active, Submit for approval instead. Assigned internal staff
are notified and, if set up, can accept or decline. Freelancers and service
providers receive no notification; give them the plan as a PDF.
Committing & approval
Notice board and subscription. The PDF export Rooms by day for the
notice board, Personnel overview for the question "who works when"; staff
subscribe to their operational plan on their phone.
Exports
Event missing in the shifts tab: the event is not assigned to the
project. The list Relevant Dates For Shift Planning in the project is
only a hint for planners and does not filter the shifts tab.
Person missing in the workforce panel: work profile without May be
assigned to shifts or without this craft.
Change after committing: possible; the internal staff affected are
informed. Before committing, assigning or removing someone triggers no
notification.
With an active release workflow it also appears under Duty roster →
Shift plan Change list. Only approvers and admins see this menu item.
Changing a committed shift
Set-up on the previous day running past midnight: shifts across
midnight occupy both days; rest period rules check this.
Without a project: shifts can also be created freely in the room cell
of the duty roster, for example for building services. Every shift
needs a room.
Shifts without a room or event
With the approval workflow: the craft lead submits, operations
management approves; the Week status shows which weeks are still open.
With working time planning: contracts and work time patterns turn the
plan into time accounts and overtime.
Contract & working hours
Getting started
A festival as a project group
Many individual events under one roof – project group, budgets, calendar, team and evaluation
A ten-day festival with thirty events in five rooms. Each event has its own
artists, dates and budget; the festival as a whole needs an overall view, an
overall budget and a team that sees everything.
Create the project group. When creating, choose Project group; it
gets a status, category and team just like a project.
Project groups
Create the individual projects, directly from the group with Create
project in this group, or add existing projects with Add projects to
group. A project can belong to several groups.
Book the events. Each individual project gets its events; in the
calendar, Show project group shows on every tile that it belongs to the
festival, and the Project status filter hides cancelled programme items.
Display settings
Manage budgets. Each individual project has its own budget. The
group's budget combines them row by row: create rows there with the same
KTO and KST values as in the individual projects. For each such row, the
project group aggregation pulls in the values of the matching rows of
all individual projects, taken from their Relevant for budget column.
Rows without KTO or KST are left out. Create funding as a source of
funding and release it to the projects.
Project group aggregation ·
Projects & budgets
Team and visibility. Whoever is in the group's team sees the group – not
automatically every individual project. Production managers belong in the
team of their individual project; the festival management in all of them, or
it gets Read all projects.
How project permissions work together
Publish the programme. The Season schedule projects (PDF) shows all
programme items in wall-calendar style; the Excel event list provides the
data for the website and print.
Season schedule projects (PDF)
Evaluate. Record BI data per individual project; the BI dashboard
compares the productions by audience, revenue and effort.
Business intelligence in the project
The project list only shows the group: check the filter Project
groups or Show only projects without group.
The overall budget does not add up: per individual project only the
one column marked Relevant for budget flows into the aggregation, and
only from rows whose KTO and KST match a row of the group.
Budget-relevant column
Shifts: they always belong to the individual project, never to the
group; in the duty roster, the project mode per individual project helps.
A company from abroad is visiting with seven people for four days. The
organisation needs riders, travel details, the names of everyone arriving,
image and press material, books a hotel, pays a daily allowance and signs a
guest performance contract.
Create the company in the CRM and link it in the project. The contact
type for artists is supplied; contact types such as Company or Agency
are created by your administration in the CRM settings. You link contacts
of the artist contact type in the Project Artist component via Link
with CRM artist. In a CRM contact list of the project they receive the
special role "Artist" automatically and therefore appear as artists of the
project in the calendar, duty roster and exports. Other contact types also
go into a contact list; they only get the special role if roles are
switched on there and you assign it. If the option CRM contacts in project
team is active under System → Projects, an external team member with
a project role also works.
Link contacts to projects
Create an inquiry tab. In the tab settings, Create tab from template →
Production inquiry: coloured sections for contact and company, artists
(arriving people as a CRM contact list), general information, documents
(this is also where the company uploads the rider), music and rights, texts,
image and video, and sponsoring. The template does not ask for travel
details; add a text field of your own for that. The tab applies to all
projects. Managing tabs
Invite the company. In the inquiry tab, Invite external to this tab:
email, optionally a name, the tab with the access Read and write, and
From and Until. The button only appears if external access is
switched on and you have Invite externals. The person fills it in
without an account, uploads riders and photos (if uploads are enabled) and
creates the arriving people as contacts; with Submit entered data they
report that everything is complete. You confirm or return it for revision.
Only after your confirmation do the people they created count as artists of
the project.
External access
Plan the residencies. In the Artist residencies component, create
one residency per person: arrival, departure, accommodation (a CRM contact
of the Accommodation type with its room types), room type, cost per night and
daily allowance. You pick the person via Assign existing artist; the
arriving people from the inquiry are offered there because the contact list
creates them as contacts of the artist type. There is no bulk transfer from
the contact list. artwork pre-fills the cost per night from the room type of
the accommodation. If a daily allowance and a breakfast deduction are stored
on the accommodation, artwork pre-fills them as well; otherwise the general
default from System → Projects → Artist residencies applies.
Artist residencies
Export. From the component, export the residency plan as PDF or Excel
and the daily allowance statement as Per Diem Export, each in German or
English. The Per Diem Export carries the letterhead from the tool settings.
File the contract under Documents → Contracts or in the project: contract
type (for example Guest performance, if your administration has created
it), amount, currency, foreign tax and KSK details,
access only for administration and project management; request missing
paperwork as a document request.
Managing contracts
Events and shifts. Set-up, rehearsals and performances in the calendar,
shifts as in the use case
Planning a performance with shifts.
The timeline of the performance event records get-in, sound check and
admission.
Externals see too much: the external person sees all components of the
shared tab, regardless of internal visibility settings. That is why you use
a separate inquiry tab, never the internal production tab.
Upload does not work: file upload for externals is a separate switch
in the external access settings.
A residency cannot be created: as long as there is no accommodation,
the dialog shows only a notice instead of the form. It points to the CRM
and leads straight to the contacts of the Accommodation type with Open
accommodations in the CRMComing with the next update. Create the
accommodation there; more under
Accommodation and room types.
Daily allowance without letterhead: name, address and email for the
letterhead are set under Communication & Legal.
A partner venue borrows twelve spotlights, a mixing desk and a set of radios
for two weeks. During that time the material must be blocked for your own
productions, the loan documented and the return recorded with any defects.
Have the contact details ready. You enter the borrowing venue's name,
email, phone and address directly in the issue. The external material issue
has no link to the CRM. A CRM contact is still worthwhile if you also need
the venue for contracts or projects.
Create a contact
Create an external material issue under Inventory system → Material
issues in the External material issue book: name, Material Value,
Issue Date and Return Date, External Name (plus optional email,
phone and address) and the issuing person under Issued By. The issue can
only be saved with a material value greater than 0.
Creating an external material issue
Add articles – via search or from a material set ("Radio set large").
Every article you add shows Available in period; when overbooked, the
conflict banner appears with Automatically adjust quantities.
Selecting articles and checking availability
Print the loan slip.Print → Document preview → Create and attach
document generates the PDF and attaches it to the issue; the venue signs
on collection.
Creating a PDF and printing
During the loan, your own productions see the blocked quantity in
article planning as a striped bar (external issue).
Article planning
Record the return with Enter return and Defects after return;
set defective items in the catalog to the appropriate status. If the return
date is reached without a return, artwork reminds the issuing person once,
on the morning of that day. The notification has two buttons: the green
check mark (Confirm return) and the red X (Not returned yet).
Documenting the return
Availability is lower than the stock: only items with the status
Ready for use count; overlapping issues are deducted with their highest
simultaneous quantity.
No reminder: without an issuing person entered, no return reminder is
sent.
Material stays blocked after the return date: the articles remain
reserved until the return is entered, even past the return date. Enter the
return as soon as the material is back.
Finding overdue loans: filter Only overdue returns in the external
issue book.
Internal issue for one of your own productions: the same route in the
Material issue book or directly in the project's Material issue
component, with project and room reference.
Creating an internal issue
Custom articles for things that are not in the catalog (third-party
loan material, consumables). Custom articles
Recurring loans: Copy material from another material issue takes
over the articles and quantities of an earlier external issue, which you
find by its name.
Getting started
Renting out a room to external parties
Handle a rental from first contact through room booking, contract, technical equipment and staff to billing
A company rents the Main Hall for an evening event. It brings its own
technical equipment but needs front-of-house staff, one in-house technician
and ten standing tables from the stock. The organisation signs a rental
agreement and invoices the rent and the staff.
Create own projects, Plan events directly or Request room occupancy; for planned events View planning calendar and Plan directly in the planning calendar
Create the tenant in the CRM with contact person and billing address.
A contact type such as Organiser or Company is created beforehand by
your administration in the CRM settings; it is not supplied.
Create a contact
Create a project, for example "Rental Company X, 14 Nov", with a category
Rental that is marked as Main. The BI dashboard then evaluates rentals
as a category of their own. The project list does not filter by category; a
separate project status helps there.
Creating a project
Create events: set-up, event and strike in the Main Hall, with the event
type Rental or Set-up (your administration creates both); admission
time on the main event, provided the Admission field is switched on for
your organisation. Anyone who may
not book the hall directly submits a room request in the process.
Creating events ·
Handling room booking requests
Not sure yet? As long as the company has not signed, create the events
as planned events: in the planning calendar, or in the project's event
entry with the toggle for planned events. They are only visible to people
with View planning calendar and do not book the hall bindingly. A project
status with Project counts as "in planning" merely presets this toggle.
Fixed events that already exist and events created in the calendar stay
fixed and visibly occupy the hall. After the signature, request the
verification or confirm the events as fixed events.
Planning calendar
File the contract on the project: contract partner from the CRM, amount,
access only for administration and rentals. Request missing paperwork (such
as proof of insurance) as a document request.
Contracts
Plan staff: shifts for front of house and technical duty on the event,
then staff and commit them as usual.
Planning a performance with shifts
Reserve material: an internal material issue on the project with the
standing tables; article planning shows the booking.
Creating an internal issue
Bill: rent as revenue, staff costs and material as costs in the project
budget. With the Sage interface active and the permission Project Sage
data, you see the project's Sage bookings in the budget tab and assign them
to the budget rows.
Project budget
The hall looks free although it was requested: open room requests are
hatched and marked as requests in the calendar; room admins see them under
Event Verifications. If Events always bookable directly is on,
there are no room requests and this menu item does not exist.
Noisy neighbours: the calendar filter Event properties shows where
loud events are (the supplied property is called Laut, "loud"). Which
rooms adjoin each other is listed on the room page under Adjoining
rooms. There is no automatic warning about loud events in an adjoining
room; check the neighbouring rooms yourself.
Rooms, areas & booking access
Rentals distort evaluations: a separate project category, marked as
Main, keeps them apart as a category of their own in the BI dashboard.
In spring, the artistic direction and the scheduling office plan the next
season: premieres, revivals and guest performances exist only as drafts so
far, and some dates exist in two variants. The technical team and the crafts
should not see the drafts yet, but should later receive a binding plan.
Create projects for the season's productions, with a project status that
is marked as Project counts as "in planning". The toggle for planned
events is then preset in the project's event entry. Events you create in
the normal calendar do not follow the project status, so create drafts in
the planning calendar or in the project.
Projects with a planning status
Plan in the planning calendar: create events with project, room and
times, leave variants side by side, and use multi-edit to duplicate and move
events. Planned events are never room requests: creating them requires
Plan directly in the planning calendar; room admins may do so in their
own rooms without this permission. Plan events directly from the normal
calendar is not enough.
Planning calendar
Check against the real calendar: the display setting Show fixed
events overlays the existing bookings, so clashes with rentals or revivals
become visible.
Planning mode
Provide an overview: for the management meeting, export the calendar
as a PDF and switch on Show planned events under Display settings
in the export, or temporarily use the same option in the normal calendar.
The season schedule (PDF) is not suitable for this: it always leaves out
planned events.
Display settings in the export
Confirm: as soon as a production is fixed, select its events and choose
Request verification in the action bar. Alternatively, set the project
status to a normal status; the dialog then offers Request event
verification. In organisations with "Events always bookable directly",
the action is called Confirm as fixed events in both places. Only
people with Edit planned events can confirm events of others; without
this permission the action bar only works for events you created
yourself, and the route via the project status is not available at all.
From plan to real event ·
Project header
Have them verified: event types with a verification mode go to the
verifiers and become fixed events on approval. Events of event types
without a verification mode become fixed immediately. No room request is
created in the process: the confirmed event is firmly booked and appears
for everyone.
Event verifications
Direct booking in the organisation: with "Events always bookable
directly", verification is skipped; Confirm as fixed events books
immediately.
Events always bookable directly
Festival: the drafts of a project group can be viewed specifically via
the project status filter, see
A festival as a project group.
Getting started
Rehearsal planning with series and timeline
Create a rehearsal period as a series, move single rehearsals, maintain daily schedules as a timeline and staff rehearsals
A production rehearses for six weeks, Monday to Friday from 10 am to 2 pm, on
the rehearsal stage, and in the last week on the Main Stage. Some rehearsals
move, the final rehearsals follow a fixed daily schedule, and the technical
team needs staff for the stage rehearsals.
Create the series: an event Rehearsal on the rehearsal stage, under
Repeat weekly, Monday to Friday, ending on a date.
Repeat
Adjust the stage week: open the first event of the last week, change the
room to the Main Stage and choose This and following.
Editing series
Move single rehearsals: change only this event; it remains part of the
series but deviates from it. With the display option Repeat event you
recognise series events in the calendar.
Visibility & filters
Maintain daily schedules: on the final rehearsals, a Timeline with
admission, start, break and end. Store recurring schedules via Save
timeline as preset in the three-dot menu of the event tile (requires
Plan events directly) and bring them into other events with Import
timeline preset.
Timeline
Sub-events for parallel partial rehearsals (for example a music
rehearsal in the rehearsal room during the scene rehearsal), so that they
are attached to the main event.
Sub-events
Plan staff: in the project's shifts tab, create shifts for the stage
rehearsals from a template and staff them.
Planning many shifts with templates
Distribute the plan: the team subscribes to the calendar or receives the
project's event list as Excel.
Calendar subscription
A change affects too many events: when saving, the choice Only this
event, This and following or Whole series decides. Deviating events
are kept when the series is changed.
Deleted by mistake: series events go to the recycle bin; Restore
series brings all of them back.
Restoring event series
Timeline without permission: anyone who may edit the event (for
example with write permission in the project) or has Plan shifts may
maintain it. Only saving it as a preset requires Plan events
directly.
A technician works 39 hours a week under a collective agreement. She is
assigned to shifts, has office days without a shift, stays longer on
performance evenings and should be able to see her overtime at the end of the
quarter, reduce it or have it paid out.
Create contract and pattern in the shift settings: a User Contract
(vacation days, days off, overtime rule, reduction deadline) and a Work
Time Pattern with the daily target per weekday.
Work time patterns & contracts
Assign them to the person under Contract & working hours, each with a
validity period; a planned change (for example to part-time) can already be
entered in advance.
Contract & working hours
Record work: shifts in the duty roster count automatically; office days,
training or working from home are entered as Individual times, recurring
ones also as a series. This is done by planning or, with the permission
Enter own individual times, by the employee herself in her own
operational plan (from today on, without approval).
Individual working times
Nightly calculation: every night at 23:59, artwork books target, actual
and balance for the day that is ending; during the day the hours account
therefore shows the state up to yesterday. Vacation and sickness are
target-neutral. Special days reduce the target if the contract has the
special day rule active and no work starts on that day. The employee sees
the result under My key figures.
My key figures
Correct: stayed longer? The employee requests a work time change on
her shift; planning approves or declines it. For times without a shift, HR
administration books an adjustment in the time account (add or deduct
hours, with night hours).
Requesting a working time correction ·
Work times
Reduce or pay out overtime: the overtime account shows open hours and
their deadline. Whatever has not been reduced when the deadline expires can
be booked out with Pay out overtime; before that, artwork does not offer
the payout.
Overtime ·
Paying out overtime
Keep the rules in view: working time rules (rest periods, weekly
maximum, free Sundays) check the planning continuously; violations and
substitute days off appear in the duty roster and in the overview.
Rules & violations
Target shows "–" and "Work time pattern missing": no pattern is
assigned to the person, or it does not apply to this period.
Actual differs from the duty roster: a person's individual shift times
count instead of the shift time; an approved time adjustment replaces them.
Vacation or sickness does not change the account as expected: the
day statuses Work-free day (counts like vacation) and Not
available (counts like sickness) are target-neutral. An absence a person enters themselves also
counts as not available. The day status Free changes neither target
nor actual.
Public holiday without target reduction: the holiday is not marked as a
special day, the contract does not have the special day rule active, or
the person worked on that day. The target then stays in place.
Special days
Three-month average instead of daily target: contracts can calculate
the target over a compensation period.
Three-month average
Month-end closing for a whole craft: the tab Excel Work Time
Overview in the export dialog of the duty roster totals target and
actual per craft and month, separately for internal and external staff.
It contains no individual people; read their account in the Work
Times tab of the profile.
Working time overview per craft
Getting started
How do I …?
The task index takes you from the question straight to the right place in the manual, sorted by module
This index is meant for the moment when you are working in artwork and
looking for a specific task. Each row takes you directly to the matching
section. If a task is missing, use the search at the top left; the module
chapters are more complete than this index.
The terms used in artwork explained in one sentence, with a link to the place where they are described in detail
artwork uses some terms differently from what you may know from other tools
or from your own organisation. Each term is listed here with a short
explanation and a link to the detailed chapter. Synonyms in parentheses
also lead to the term in the search.
Working time without a shift, such as office work or training; counts towards the time account. Individual working times
Individually tracked article
An article whose units are managed individually, each with its own inventory number, status and properties. Individually tracked articles
Material issue (loan slip)
A reservation of inventory for a period, internally for a project or externally as a loan slip. Material issues
Material set
A saved collection of articles that are issued together. Material sets
Module visibility
Showing and hiding entire modules for the whole organisation in the Module visibility tab of the tool settings; also blocks the pages of the module for everyone except admins but deletes no data. Module visibility
Operational plan (German UI: Mein Einsatzplan)
The personal view of your own duties, figures and availability. My operational plan
A provisional event in the planning calendar. It is visible only with planning calendar permissions until it is approved or confirmed and thereby becomes a fixed event. Planning calendar
Planning calendar
A separate calendar for provisional planning, kept apart from the binding calendar. Planning calendar
Print layout
A template that outputs selected components of a project as a PDF, for example for external partners. Print layouts
Project (production)
Container for everything about a production or event: events, team, budget, documents, tabs. Projects
A request for a room when the person creating the event may not book it directly. Event verifications
Rule violation
A conflict with a working-time rule, such as a rest period that is too short; marked in the duty roster. Rules & violations
Season window (UI: Playing time window)
Start and end of the season; the default period for BI and season-related figures. Without a valid window the current calendar year applies. Communication & Legal
Series (repeating event)
Several events with the same pattern; changes apply to one, the following or all of them. Editing series
Shift
A time block with craft, room, break and demand per function, filled with people. Creating shifts
Shift group
A label for similar shifts (such as early, evening), required for rest-period rules between them. Shift groups
Source of funding (grant)
A funding pot or subsidy with an amount and a term, to which projects and budget items are assigned. Sources of funding
Special day
A holiday entry with the checkbox Treat as special day. If no work starts on that day, the daily target is lowered, provided the contract uses the special day rule. Special days
Substitute day off (German UI: Ersatzfreier Tag)
An entitlement to a full or half day off with a deadline. Planners credit it when they process a rule violation (such as Sunday or special day work) or create it by hand in the profile. Substitute days off
The daily schedule within an event (get-in, admission, start …). Timeline
Verification
Approval of a planned event by the people designated for its event type; after that it is a fixed event. Events created directly in the calendar do not go through it. The verification workflow for event types
Week status
Overview of crafts and calendar weeks with commit status and staffing. Week status
Work profile
Part of the user profile: whether someone may be assigned to shifts, in which crafts and with which functions. Work profile
Work time pattern
A person's daily target per weekday; the only source of the target and therefore the basis for the hours account and overtime. Work time pattern and target
Workforce panel
The lower part of the duty roster's week view with all schedulable people per craft. The workforce panel
Dashboard
Review today's events, personal working times, tasks and current notices
The Dashboard is your personal Artwork home page. Its main purpose is to
answer: What matters to me today? It combines information from the calendar,
duty roster, tasks and notifications. The dashboard is a working overview;
the underlying information is maintained in the respective feature areas.
The top area links directly to Calendar, Shift plan (the duty
roster), Tasks and Notifications. The duty roster link is only shown
with the permission View duty rosters.
Four figures summarise the current day:
Figure
What it counts
Today's appointments
Events starting today from projects whose team you belong to
Today's shifts
Your shifts starting today and your individual working times for today
Notifications today
Your unread notifications received today
Open tasks
The not-yet-completed tasks shown on the dashboard
These figures are personal. A colleague may see different numbers on the same
day because project membership, staffing, task assignment and read status are
different.
Event cards are sorted by start time. They show the abbreviation of the
event type in its colour, the event title or the project, start and end or
All day, the room and, where maintained, the description. The project
name is a link into the project. Open in calendar takes you to the event
in the calendar, where additional details can be viewed or edited according
to your permissions. to calendar at the top right opens the calendar
without reference to a specific event.
The dashboard does not show every event across the organisation. It shows
events from projects whose project team you belong to. Events without a
project do not appear here. The start is what counts: a multi-day event that
began yesterday and is still running today is not listed. Use the full
calendar to review other projects, days or rooms.
Shifts today shows your assigned shifts and the individual times
applying today in chronological order. Your day services sit above them
as separate bars: one bar per service with icon and name in the colour of
the day service. All-day entries appear at the beginning.
The shift cards match those in My operational plan and show the
context of the shift where maintained: project, event, craft and function,
time, break and room. In addition:
Colleagues: who is scheduled with you in the shift.
Accept / decline: With shift confirmation active you see your reply
status (Requested, accepted, declined). If you hold the permission
Accept or decline shifts, you can accept or decline directly on
the card, optionally with a comment.
Note: Your individual shift note can be edited directly on the card.
Project link: Clicking the production jumps to the day of the shift
in the project's shifts tab; this also works for project team members
without additional duty roster rights.
The counter includes both shifts and individual times. The section may
therefore contain an individual time even if you have no assigned shift.
Select to the shift plan to open the full planning view; the link is
only shown with the permission View duty rosters. A shift counts for the
day on which it starts: a night shift that began yesterday evening is no
longer listed today.
A central organisational announcement may be displayed prominently with a
title, text and image. Below it, Artwork shows your unread notifications
received today. If there are more than five, use the page controls to move
through them.
Notifications can contain links and actions leading to their origin, such as
a project, event or shift process. Go to the notifications opens the full
notification centre with older messages and your personal settings.
The count can change
Once a notification has been read or otherwise processed, it no longer counts
as an unread notice for today. The dashboard is therefore a snapshot of your
personal working status.
Artwork shows up to five open tasks assigned directly to you or belonging to
one of your own checklists. Tasks with a deadline are ordered by the earliest
date first; overdue deadlines are highlighted. You see the task name,
description and, where applicable, its project and checklist context.
Use the checkbox to complete a task directly. The project link opens the
relevant checklist. Select To the task overview for all tasks, filters and
additional editing options.
A missing event may mean you are not in the project team, the event has no
project, or it does not start today.
A missing shift may be caused by its staffing assignment or by the shift
starting on a different day.
The duty roster link is hidden without the permission View duty
rosters.
The dashboard shows only a selection of open tasks, not necessarily every
task.
Read or older notifications are available in the notification centre.
If in doubt, check the relevant feature area first. It provides complete
filters, date ranges and details.
Projects
Overview
What projects are in Artwork and how the module is structured
Projects are the central bracket in Artwork: a production, a concert, a
festival edition or an event series — with its own team, events, budget,
checklists, documents and shifts. Almost everything in the system can be
assigned to a project: calendar entries, shifts, contracts, funding
sources.
A project is therefore more than a digital project folder. Changes made in
one place feed into the connected modules: events define the project period,
shifts appear in the duty roster, budget figures can roll up into project
groups, and documents stay attached to the production. Core information is
maintained once and then shared by planning, technical, administrative, and
communications teams.
The planning unit — from a single event to an entire production.
Project group
A project with a group flag that bundles other projects (e.g. a festival with its individual events). Budget columns can be aggregated across the group.
Project status
Freely definable statuses with a color (e.g. idea, in planning, confirmed, cancelled). A status can be marked with Project counts as "in planning": new rows in the project schedule of such projects are then preset as planned events (see Project status).
Properties
Category, genre and sector: freely definable attributes with an optional main assignment, by which projects can be filtered.
Tab
A page within the project view. Which tabs exist and what they contain is freely configurable.
Component
A content element in a tab — from text fields to checklists to the complete budget.
Unlike most modules, the project view is not a fixed layout:
administrators assemble the tabs from components — standard components such
as calendar, budget, shifts or comments, plus custom fields (checkboxes,
texts, dropdowns, links). Visibility and editing can additionally be
restricted per component. What your project view looks like therefore
depends on your venue's configuration; this documentation describes the
default tabs as shipped.
Create and classify the project. Name, artists, status, properties,
project leaders, and an optional project group provide the shared starting
point.
Set up the team and access. Decide who can view the project, who may
edit it via the Write permission checkbox, who is project management,
who receives budget access, and which project role each person performs.
Plan events and the project period. Add events in the calendar or in the
project table. Relevant event types automatically determine the period.
Work together. Custom fields, checklists, comments, links, documents,
contracts, material issues, and shift information keep the current state in
one place.
Evaluate and share. Budgets, BI figures, history, Excel exports, and
configurable project PDFs support reporting, handovers, and documentation.
Your view may look different
Artwork can be adapted to the workflows of each organisation. Tab names,
order, fields, and visible functional blocks may therefore differ from the
examples in this guide, while the underlying interaction stays the same.
Open and read all projects (otherwise only your own or team projects). Read only: editing requires write permission in the project team or the global write permission.
Create own projects (Eigene Projekte anlegen)
Create projects; the creating person can edit their project afterwards. Deleting is not included.
Write all projects (Schreibrechte für alle Projekte)
Open and edit any project, even without team membership. The editing restriction of individual components does not apply, but the setting "Only visible to the following" still does.
Delete all projects (Löschrecht für alle Projekte)
Move any project to the trash, delete several projects at once, and restore or permanently delete projects in the recycle bin
Can be project manager (Projektleitung sein)
Can be marked as project management in a project team. Grants no access to and no write permission for other projects.
The project list itself is visible to everyone. The permissions control
which projects you can open and edit (see
The project list).
There are additionally rights per project (the checkboxes Write
permission, Project management, Budget access and Permission to
delete — granted via the
project team) and
restrictions per component.
Access: whether a project can be opened is decided by membership in
the project team (person or department) or by the global permission
Read all projects.
Editing: writing in a project requires write permission within that
project — the Write permission or Project management checkbox in
the project team, having created the project, or belonging to an
assigned department. The global permission Write all projects
grants this for every project.
Components: the permission settings of individual tab components
(component settings)
can only restrict these rights further, never extend them.
Read only means read only
Anyone who may only read a project cannot edit its tab components — even
if a component is set to "editable by everyone". The permission Can be
project manager no longer opens other people's projects; anyone who is
meant to work in a project needs a team membership or the global read or
write permission. The rules apply in the interface and on the server
alike.
Projects
Project Overview & Creating
Work with the project list and create new projects or project groups
Open the project overview via Projects in the sidebar.
The overview is the personal starting point for daily project work. Filters
and sorting are saved per user, so production managers can focus on their
current projects while administrators can look specifically for groups,
projects without events, or productions with BI data.
Search: the field Search for projects or their artists finds
projects by their name, by the free text in the artists field and by
linked artists from the CRM.
Pinning — projects can be pinned via the project menu; they then
appear for you at the top in the Pinned section. The section stays in
place during a search as well and shows the pinned projects that match the
search; they do not appear a second time in the normal result list.
Filters do not affect pinned projects: they stay visible whatever the
filter selection is.
Sorting — alphabetically or chronologically, each ascending and
descending. When sorting by project period, projects without events
always come last; the period column shows the date only, without time.
If no sorting is selected, the most recently created projects come first.
Filters: the selection only takes effect with Apply and is saved
per user; Deselect all resets it.
Filter by type: Project groups, Projects. If neither is
ticked, both appear.
Filter by time: Show future projects (at least one event from
today onwards), Show expired projects (at least one event before
today). If both or neither are ticked, there is no time restriction.
Projects without events stay visible in both cases unless you hide
them.
Other filters: Hide projects without events, Show only
projects without group, Only projects where you are in the project
team, Only productions with BI data. The project team filter
only counts whether you yourself are on the team as a person;
membership via a department is not enough.
Project status: only projects with certain statuses
Select multiple projects: with Delete all projects you select
several projects and move them to the trash together. Select all on
this page selects the current page of the list; tick pinned projects
individually.
New browser tab — Ctrl-click (Windows), Cmd-click (Mac) or the middle
mouse button opens a project in a new tab.
Open the project menu via the three-dot menu that appears when you hover
over a row, or by right-clicking. It is only available to people with edit
or delete permission on the project; without one of these you cannot pin
a project either. The first entry, Open, opens the project. Below it,
depending on the permission, are Edit basic data, Pin or Undo pinning,
Duplicate and Put in the trash. Pinned projects carry the
Pinned badge, project groups the Group badge with the number of
their projects.
All events by project (project search, recently opened projects) or by period, with room, area and event filters and selectable columns (event ID, project name, artists, date and times, admission, event type, event name, description, event status, room, project team, project properties). The columns for artists and admission only exist if the respective field is enabled at your venue.
Excel Calendar Export
The calendar grid as a table, using the calendar's display settings.
Budget export by deadline
Only visible if the Budget deadline is enabled in the project settings and you have Global budget accessComing with the next update. Exports all project budgets whose deadline lies between Start date and End date, either aggregated (one row per project with forecast and Sage totals; the forecast values come from the column marked "Relevant for budget") or itemised (one row per budget line and per Sage booking, with cost center, ledger account and position). Columns can be deselected. The download requires the permission Global budget access.
Excel Project Role Overview
Only with Read all projects. A matrix: all productions touching the selected period as columns (with their event period), all people with a fixed project role as rows, and the assigned role in the cells. Quick selection This week, This month, Next month, This year, Next year; up to 36 months. Only people who have default project roles in their user settings and hold a role in at least one project team during the period are listed. Project groups are not exported.
Last visited project takes you straight back to your most recent work;
the Recently opened projects dropdown of the project search lists up to
ten productions. This list is stored in the browser and therefore only
applies to the device on which you opened the projects. Pinned projects are a separate, permanent personal
favourites list.
The overview lists all projects of your venue, including those you are not
allowed to open. You can open a project if you are on its project team (as
a person or via a department) or hold Read all projects or Write all
projects. Rows without access cannot be clicked, and their columns with
content from the project tabs and with budget information stay empty. The
same applies to columns whose component you are not allowed to see.
The New project button opens the creation window (permission Create
own projects). A switch toggles between Project and Project
group.
Besides the mandatory project name, the window asks — depending on your
venue's creation settings —
for:
Field
Contents
Artists
Artists as free text or linked from the CRM
Project properties
Category, genre and sector as an expandable checkbox grid (multiple selection); the main marker sits directly on the respective row
Project status
One of the configured statuses. If Project status as a required field is enabled, a status must be selected — it remains changeable when editing the base data later, only removing it is blocked
Assign the project to an existing group right away. This field is always present.
Mark as Done
The project no longer appears in the project searches, for example when selecting a project in an event. It stays in the project overview. This field is always present.
Anyone who creates projects but does not hold Read all projects is
automatically added to the project team as project management with write
permission. This keeps the project reachable for the person who created
it. With the global read permission you are only on the team if you enter
yourself as project management.
The window has two buttons: Create creates the project and returns to
the project overview, where it appears in the list. Set up events
creates the project and then opens the event entry for this project right
away. When creating a project, only people who may create events directly
see this button (Plan events directly or Edit planned events).
These initial details are not final: authorised users can change them
later via Edit basic data in the project menu. There you can also
upload a Key Visual, the image of the project in the header. The main
content—description, team, events, checklists, shifts, and budget—is then
maintained in the project tabs.
Artists can be entered as a name or linked to an existing CRM contact. A
link is useful when contact details, company relationships, and other
projects involving the same person should remain discoverable. Project
search also considers assigned artists.
A project group is technically a project itself, with a group flag.
Typical use: a festival as the group, the individual concerts as members.
Projects can be assigned to a group at creation or later; the group shows
its members in a dedicated component. When creating a project group you
additionally choose an Icon and a color and add existing projects
right away under Projects of the group. In the
budget the group combines the values of its
sub-projects: it takes the column marked "Relevant for budget" from each
sub-project and adds up the rows whose account (KTO) and cost center (KST)
match a row of the group.
The header of a project group offers additional actions: add existing
projects or create a new project directly inside the group. Member projects
link back to their parent group, making it easy to move between a festival,
season focus, or tour and its individual productions.
In Edit basic data, Convert to project group turns a project into
a group and Convert to project turns a group back into a project. A
confirmation window states the consequences beforehand: if a project group
becomes a project, the connection to its subprojects is lost. The
subprojects themselves remain as separate projects.
Project group or regular project?
Use a group when several independent projects should be navigated or
evaluated together. Several events belonging to the same production will
usually be better represented by one regular project with multiple events.
There is no "project from template" — instead, an existing project is
duplicated via its menu and serves as the blueprint.
Budget templates exist as a
separate concept on top.
A duplicate is an independent new project named "(Copy) …". Only the
project's basic data is copied:
name, project status and number of participants
whether it is a project group
the properties (categories, genres, sectors) and the departments
the project team with all rights and roles. Whoever duplicates the project
and is not yet on the team is added with budget access.
the cost unit including its description Coming with the next update
Not copied:
artists, budget deadline, Key Visual and the membership in
a project group
content entered in the components of the project tabs, such as text
fields, checkboxes, dropdowns, links or CRM contacts
the budget: the copy starts with an empty default budget table
events, shifts, timelines, checklists, files, comments, material issues
and funding sources
Component content is not copied because every venue sets up its tabs and
components differently, so there is no common structure to copy from.
Anyone who may open the project can duplicate it if they additionally hold
Create own projects or Write all projects, or are project management
or have budget access in the project. After duplicating, Artwork opens the
copy in the first tab that contains the shift component. If there is no
such tab, you end up in the project overview.
The duplicate is meant as a starting point. Review its name, team and
status afterwards, and add events and tab content anew. Later changes to the
source and the copy are not synchronised.
Put in the trash removes a project from normal work without deleting
it irrevocably. Anyone who holds Delete all projects or has the
Permission to delete checkbox in the project team may delete. All team
members receive a notification with the number of events deleted along
with it. If a project has events that are on sale via Artwork-Tickets, it
can only be deleted after the sale has been withdrawn.
Deleted projects are in the recycle bin in the
sidebar, tab Projects. The recycle bin is visible to anyone with the
permission Open trash. There you may restore and permanently delete the
projects you would also be allowed to delete; Delete all requires
Delete all projects. Entries in the recycle bin are removed
automatically once the
retention period has passed.
Projects
The Project View
Tabs and sidebars, project team, checklists, comments, documents and contracts
Clicking a project opens the project view. Its structure — which tabs exist
and what they contain — comes from the
tab construction kit; here we
describe the default configuration as shipped.
At the top are the Key Visual, the project name and status, plus the
project actions. Three icons are visible to everyone who may open the
project:
Select print layout (printer icon): opens the selection of
print layouts and generates a
project PDF.
Copy link: copies the direct address of the open project. The
recipient still needs the appropriate access rights.
View history: the project's change log; next to it you see who last
changed the project and when. The entry appears as soon as there is a
first change.
The three-dot menu next to them is only visible to people with write or
delete permission in the project; anyone who may only delete finds just
Put in the trash there Coming with the next update:
Duplicate: creates a copy with the basic data and the team, without
tab content, budget or events. See
Duplicating instead of templates.
Edit basic data: name, properties, status, project group, Key Visual
and the conversion into a
project group.
If you change the status here to one marked as Project counts as “in
planning” in the project settings,
the Project status change dialog asks whether all events of the project
should be converted into planned events
— Convert to planning events affects every event without exception,
including past and fixed ones; with No only the status changes.
Converting requires Edit planned events. In the opposite direction (from
“in planning” to a normal status) the dialog offers Request appointments
verification or Confirm as fixed events. The dialog only appears
when editing via the header, not when changing the status from the project
list or via the status component.
Put in the trash: moves the project to the trash. In the header the
entry appears for admins, for team members with the Permission to
delete checkbox and for people with the global Delete all projects
permission Coming with the next update, as in the project menu of the
project list.
For project groups the menu also provides Add projects to group and
Create project in this group, and the header lists the Projects in
this group. A member project links back to its parent group from the
header.
Clicking the project name opens a quick switcher with a search field. It
lists the current project, for a project group its projects, and for a
member project its group. The switch stays in the tab that is currently
open.
Below the project name are the rooms in which the project has events with
an audience. If there are none, the period from the first to the last
event is shown there. The header shortens long room lists to three rooms
plus "+n". It collapses automatically while you
scroll so the tab content gets more space.
The top tabs switch between major work areas. An optional sidebar keeps
frequently used details such as the team, properties, shift contacts, and
budget information available independently of the current tab. Collapsible
folders help structure longer pages.
The project period is normally calculated from the earliest and latest
events whose event type is marked as relevant. If a project has no event
with a relevant event type, all of its events count. The period drives the project mode of
the calendar and duty roster and updates when relevant events change.
The tab names come from the configuration and can be renamed at any time.
A new instance creates the default tabs in its own language. In brackets
is the German name, in case your instance carries it:
Tab
Contents
Project Information (Projektinformationen)
Short description, website text, press & public relations and the project documents.
Schedule (Ablaufplan)
The bulk event creation: create and edit many of the project's events in one table (see Project schedule).
Checklists (To-do-Listen)
The project's checklists.
Shifts (Schichten)
The shift tab: shift planning within the project period (see Shift Plan).
Every default tab comes with a sidebar: Shifts shows the Shift
information there (relevant event types, contact persons, general shift
information), Budget the Budget information, and all others the
Project Information with project team and project attributes. The
sidebar is expanded and collapsed via the arrow at the right edge.
The team component lists everyone involved. Anyone on the team can open and
read the project. Per person, the project additionally grants via the
permissions menu:
Write permission — may edit the contents of the tab components. New
team members start with write permission set; remove the checkbox
deliberately wherever read-only access is intended.
Project management — marks the person as project management. Write
permission is then set automatically and greyed out; an info icon in
the menu explains the differences (see below).
Budget access — may see and edit the budget table.
Permission to delete — may delete the project.
Project roles — freely definable roles (e.g. direction,
production management), managed in the
project settings. Each user
can have default project roles that are preselected when they are added.
Project roles are plain labels and grant no rights.
You edit the team via the pencil icon on the component (window Assign
project team). The icon is visible to anyone who has write permission in
the project or created the project. The permissions menu Permissions &
Project Roles on the individual people, however, is only visible to
project management, the person who created the project, and admins. Other
people with write permission can add and remove members but cannot grant
rights. The Show names switch on the component shows the names next to
the profile pictures; the setting applies only to you.
Only users with the global permission Can be project manager can be
marked as project management. Project management differs from a team
member as follows:
Always has write permission in the entire project, even without the
Write permission checkbox.
Automatically sees the project's contracts (Contracts component,
separate from the Documents component) and linked funding sources.
Receives notifications for room requests, room changes, unfilled shifts
at the staffing deadline and submissions from
external accesses.
Is shown as project management in the project header, on calendar and
duty roster tiles and in exports.
Depending on the setup, users and departments can be found while editing
the team. Members of an assigned department have write permission in the
project. The checkboxes apply only to this project; house-wide permissions
for all projects are managed in the user rights (see
Permissions). A person may thus be
unable to edit projects in general but receive targeted write or budget
access within one production.
Anyone who joins the team receives the notification “You have been added to
…” — whether when the project is created, via the team component or
automatically through a shift, a task or a checklist. New project managers
receive “You have been appointed as the project leader of …”. As long as an
identical notification is unread, no second one is created.
Without write permission, read only
Team members without Write permission see all components released to
them but cannot edit anything — regardless of the component settings.
Component permissions only restrict write permission further; they never
extend it. Admins and people with Write all projects are exempt.
Access and project roles are different
A project role describes a person's responsibility, such as direction or
production management. Write permission, project management, budget
access and permission to delete determine what that person can do in
Artwork.
If the toggle CRM contacts in project team is enabled in the
project settings,
the team window additionally offers CRM contacts. This lets you record
which external contacts — an agency or a company, for example — are relevant
for the project and assign project roles to them. External team members
appear in the project team and in project outputs with their contact type;
they do not gain access to Artwork through this. If a project role is
deleted, it is also removed from external team members.
Email the entire project team in the team component opens your mail
client with all team addresses as recipients — including in Outlook. People
without a stored email address, or whose address is marked as private, are
flagged accordingly in the component.
The project calendar shows only this project's events. The schedule
table maintains many events quickly: add rows, sort and filter, adjust
column widths, and edit or delete several entries together. Room, event
type, name, dates, times, all-day status, description, and timelines can
all be handled there. You multiply similar events via Copy in the row;
this creates individual events, not a series. A series is created in the
event form.
The shift tab opens the duty roster restricted to the project period and
its events. If shifts of the project lie before or after the project
period, for example for set-up and dismantling, the displayed period
extends to include them. If the project has neither events nor shifts, the
tab only shows a note. Three project-specific components, Contact
persons for shifts, General shift information as free text and
Relevant dates for shift planning (a selection of event types), tell
planners what to include and whom to contact. The selection is a hint for planning; the shift tab
still shows all events of the project.
Via the shift tab's display settings, events and shifts from other
projects can additionally be shown — handy for spotting conflicts with
other productions while planning. The display setting Show project
assignments adds an overview of the
people assigned to the project and project wishes,
including the avatars in the day bars.
Checklists belong to a project (or stand on their own) and contain tasks
with assignees and a done status:
Lists can be private — only you see them.
Tasks can be assigned to users, sorted and moved between lists;
"complete all / reset all" is available per list.
Checklist templates (system settings) fill in recurring workflows
with one click; users stored in the template are assigned to the tasks
automatically and added to the project team if necessary.
Depending on the construction kit, a tab shows one specific list or
all lists of the project.
Checklists in a project follow the project permission: creating,
editing and ticking off require write permission in the project. Without
editing rights the tick-off checkbox is greyed out.
The comment component collects discussions with timestamp and author.
All Comments shows every comment of the project; the Comments
component only shows those of the tabs selected when it was placed, in the
simplest case those of its own tab. Anyone with write permission in the
project sees the input field, and anyone who sees it can also comment
Coming with the next update: the project team, admins and everyone who may edit
the project via a department, as its creator or via Write all projects.
If a comment is rejected, Artwork shows an error message. You can only
delete your own comments; admins can delete any. The delete icon only
appears there.
Project documents — files on the project, as a per-tab component or
as a complete list. Depending on the type, they can be previewed,
downloaded, printed, renamed, or replaced. Files uploaded by an invited
external person via an external access
carry the badge Uploaded externally by ….
Contracts — contracts have their own metadata (contract partner,
contract type, amounts) and are collected project-wide under
Contracts; reusable contract modules are available as downloads.
Access is controlled by dedicated permissions (e.g. view/edit/upload
contracts); project management automatically sees the contracts of its
project.
Document requests — missing files can be requested from users and
tracked with a deadline. The Document request component shows them
together with the contracts in the tabs Assigned to me, Created by me, Unassigned,
Assigned to others and Completed requests (see
Document requests).
Uploaded files remain linked to the request and, where applicable, the
resulting contract.
Keep production folders, ticketing, press, streaming, and approvals with the project.
Artist residencies
Record stays, travel dates, and custom residency details, then export them; the name can be changed directly in the table with a click.
Material issue
Track inventory articles, special items, rooms, periods, notes, and attachments. Visible to everyone with read access to the project; creating and editing require write permission in the project.
Sage invoice overview
All Sage bookings of the project as a table — only with an active Sage integration.
BI figures
Record and evaluate audiences, revenue, occupancy, production attributes, and time efforts.
The BI component combines project and event data with manually maintained
figures. Values can be recorded as a project total or per event (input
mode). Artwork derives KPIs, highlights missing information, and offers
room and event filters. Snapshots compare reporting states with current
figures; reusable column presets tailor Excel exports. See
Business intelligence in a project
for details.
If external access is enabled and you have
the permission Invite externals, every project tab offers the button
Invite external to this tab. Use it to invite a company or agency by
email to read or fill in this tab without an Artwork account. In the
project you recognise the results as follows:
Uploaded files carry the badge Uploaded externally by … in document
components.
Next to the invite button there is a round status icon for each invited
person. Clicking it opens the window External persons in this tab
with the status of each person (invited, in progress, submitted,
confirmed, returned). Everyone who may open the project sees the icons,
even without the permission Invite externals.
When the invited person clicks Submit entered data, the tab is locked
for them, an entry is written to the project history with the external
person as the actor, and the inviting person as well as project
management are notified. Confirm completes the process; the tab stays
locked for the person. Return for revision reopens the tab and lets
you add a comment. This is still possible after confirming. In both
cases the person receives an email. Confirming and returning is allowed
for anyone with write permission in the project or who invited the
person to this tab.
Contacts that externals create in a CRM contact list carry the badge
External · not reviewed until you confirm the submission.
The workflow, the invitation dialog and access management are described on
the page External access.
Via the header you reach the history: who changed what on the project
and when — from base data to events to the team list. Submissions from
external accesses appear here too.
The history is useful for handovers because it shows when and by whom a
value changed, not only its current state. Shifts and budgets provide
additional specialist histories.
Projects
Event list in the project
Create, edit and filter many project events in a table and connect them with the calendar and timelines
The event list (also called schedule) is designed for projects with
many events: rehearsals, setup, performances, guest appearances and strike
can be maintained in a table more quickly than through many separate
calendar dialogs. Every row is a real calendar event. Changes therefore
appear immediately in the main calendar and may affect the project period
and shift planning.
Depending on your configuration, the tab may be called Event list,
Schedule or use a custom name. It must be set up as a component of the
project view and always runs across the full width there.
Each row represents one event. Depending on the configuration and the width
of the view, it includes among other things:
event type, event name and room,
start date, optionally end date,
start time and end time; for all-day events both fields stay
empty,
a repeat icon in front of the start time if the event belongs to a
series,
the description, via the note icon or shown below the row,
Copy and an action menu for editing or deleting.
The event list does not show event properties; you find them in the event
form.
The columns fill the full width of the tab; a configured column width acts
as a minimum width. The column header row stays visible while scrolling in
both directions. Descriptions can be shown or hidden so that either as many
events as possible or more content details are visible.
Recently edited and newly created events are marked by a subtle tint of the
row. The marker switches immediately on saving, even if only the
description was changed. A coloured bar at the start of a row marks a
planned event; the legend directly below the column header explains
all three markers.
Shows the description below each row and makes it editable there
Move the end date along when the start date is changed
When the start date changes, moves the end date by the same span so that the duration is kept. If the switch is off, the end date stays; if it would lie before the new start, it is set to the start day
Switch for planned events
Decides whether new rows are created as fixed or as planned events
Sets the minimum width per column; Reset to default restores the default
Export project list
Opens the export of the event list
Show project period in calendar
Switches to the calendar with the project period
Sorting
Sort by room, Sort by appointment type, Sort by day or Reset sorting; the rows are grouped accordingly
The columns Event Status and Admission only appear if the respective
feature is switched on for the whole house: the event status at the top of
the Event statuses page
of the event settings, admission under
Standard values.
Multi-edit, the end date switch,
the switch for planned events and the plus icons for creating events only
appear if you may edit the component and create events.
The event list uses the same filter as your
calendar: what you set here also
applies in the calendar, and a filter set there hides events here as well.
If events are missing from the list, check the filter first. In the event
list the filters by rooms, areas, room categories, room attributes, event
types and project status take effect; other calendar filters, such as
by event properties, have no effect here. Filter combinations can be stored as saved filters; the active saved
filter is highlighted in green with a check mark, the Deselect filter
icon switches it off, the X deletes it.
Add a new row. The plus icon below the list or below a group
immediately creates an event in the open project. It takes over room, event
type, name and times of the last row of the group and lies one day later;
with Sort by day, on the same day.
Check room and event type. Required fields depend on the event type
configuration.
Enter date and time. Without a time, the event is all-day. For
multi-day events, show the end date column with the switch next to
Start date.
Add name and description. The description is also visible in the
calendar and in the regular event form.
There is no save button in the event list: every change in a row is saved
immediately and appears in the calendar.
Events crossing midnight
If the end time is earlier than, or identical to, the start time, Artwork
can place the end on the following day. Always verify the displayed end
date for night shifts and multi-day bookings.
For similar events, such as a run of performances or several rehearsal
days, use Copy in the row: enter the Count, choose the interval
(Daily, Weekly, Monthly or on the same day; shown in the
language of the interface Coming with the next update) and confirm with the check
mark. The copies take over room, event type, name, times and description
and are created immediately.
Right after creating a project, the same table can open as the Events
window. There you only prepare rows at first; Create then creates all
events together.
Afterwards, or before creating, check:
Are room and event type correct in every row?
Are individual names really required, or is the event type enough?
Are times and end dates in the correct calendar day?
Should all events be relevant for the project period?
Many values can be changed directly in the row. For more extensive details,
the action menu opens the single editor in the event form. For series
events you choose there at the top whether the change applies to Only
this event, This and following or the Whole series — see
Editing series.
With the Multi-Edit switch you select several rows. A bar appears at the
bottom with the number of selected events and three actions:
Edit opens a dialog for event status, event type, room, event name,
day, start and end time. Select fields left at No change and values
that are not filled in remain unchanged.
Convert to planned events turns the fixed events of the selection
into planned events; open room requests are withdrawn in the process. The
button is shown to people with the permission Edit planned events and
to admins.
Delete removes the selected events after a confirmation.
For series events, the action menu of the row additionally contains Edit
all series events and Delete all series events for admins.
Edit series deliberately
A change with Only this event creates a deviating event. Use This
and following or Whole series if the new value should apply to the
run. Deleted events go to the trash; before a
bulk deletion, check whether the series also includes events outside the
currently visible period.
A timeline describes the internal sequence of an event, such as
get-in, soundcheck, doors, performance and strike. The event list does not
show it or edit it row by row; that happens on the event, see
Timeline. The action menu of
a row offers two shortcuts:
Import timeline preset brings a preset into the event.
Save timeline as preset stores the existing timeline of the event as
a new preset. The entry appears for people with the permission Plan
events directly and for admins, and only has an effect if the
event already has a timeline.
The timeline is part of the event but not an additional room booking. If a
section needs its own room or its own approval process, create a separate
event or sub-event for it.
If the list is set to Sort by day, a click on the day heading of a group
opens the corresponding day in the main calendar; with the Ctrl or Cmd key
held down, in a new tab. Use this to check adjacent rooms, parallel
productions and booking conflicts. The option Show project period in
calendar uses the project's calculated period as the visible range.
Events with a type configured as relevant for the project period
automatically move the start or end of the project. The shifts tab shows
all events of the project. If an event is moved or deleted,
therefore also check planned shifts and timelines.
Review conflicts and adjacent rooms in the main calendar.
Then open the project's shift planning.
Projects
Documents, contracts & additional project data
Manage files, document requests, contracts, artist residencies, and material issues
Projects can contain different specialist components. What you see depends
on the configuration and your permissions. This chapter covers the standard
workflows for project documents, contracts and document requests,
artist residencies, and material issues.
Documents can belong to a particular tab or appear in an All documents
component that combines files from across the project. Common examples are
production plans, technical riders, press materials, quotations, and
approvals.
Depending on the file type and permissions, you can upload, download,
preview (images and PDFs), print or delete a document. Visible in
defines in which upload areas of the project a file appears. This setting
only exists if the project has several upload areas; people with write
access to the component and the project management can change it. An
uploaded file cannot be renamed or replaced here: delete it and upload the
new version.
Tab-specific documents keep specialist areas separate; the combined view
supports handover and helps prevent files in another tab from being missed.
If a tab is shared via an external access,
invited people can view and download the tab's documents — and, if file
upload for externals is allowed, upload their own files. Such files carry
the badge Uploaded externally by … in the component.
Contracts are protected project documents with additional structured data:
Field
Purpose
Project assignment and Contract partner
Connects the contract to the project and a CRM contact.
Contract type
Distinguishes guest performance, fee, cooperation, and other contracts.
Comment / Note
Stores supporting information outside the uploaded file.
Amount and currency
Records the fee, contribution, or other value.
KSK-liable, Foreign tax, reverse charge
Records relevant additional amounts and reasons.
Deadline date
Shows when the document or next action is required.
Contract status and Contract status comment
Documents the processing stage.
Document access for
Selects individual users and teams allowed to view the contract.
When uploading, you can also create tasks and assign them to a person who has
document access. Project management automatically sees the contracts of its
project without being released individually.
Check access before assigning tasks
Only assign a contract task to someone who can also access its document.
Contract access and general project access are separate safeguards.
A document request starts the process before the contract file exists. The
Contracts & documents component separates five tabs:
Assigned to me: open requests for which you should provide a file,
Created by me: requests whose progress you follow,
Unassigned: requests of this project without a responsible person,
Assigned to others: open requests of this project assigned to other
people, with Requested by, Assigned to, status and deadline,
Completed requests: finished requests with the uploaded file.
The tabs Unassigned and Assigned to others are visible to people
with the permission to create or edit document requests, and to admins. The
cross-project overview is described under
Document requests.
The button Create document request is shown to people with the
permission Create document requests and to admins. No field of the
window is mandatory.
Select the responsible person who should provide the file (Assign to user). They receive a notification. If you leave the field empty, the request is listed under Unassigned.
Choose the project and contract partner. In the project component the open project is already filled in. You can only choose projects you are allowed to open. Enter the partner as text under Contract partner or take it from the CRM with Link CRM contact.
Prepare Contract value, Legal form, Contract type, tax-related details, Contract status, and comment where known.
Set a deadline and note. If you pick a project with a budget deadline via the project search, Artwork enters it as the Deadline date; it stays editable. When creating from the project component the field stays empty.
Send the request and monitor its status in your created requests.
The responsible person chooses Upload document in the menu of the
request. The upload window is prefilled with the prepared contract data;
only the contract value is not carried over and has to be entered there
again. The requesting person is already entered for document access, and
further people can be added. With the upload the request moves to
Completed requests and links to the resulting contract.
Requests can be edited and deleted via their menu. Both require the
permission Edit document requests and then apply to all requests, not
only to those you created. Use View details to check the responsible
person, deadline, amounts and current status.
The Artist residencies component documents an artist's or CRM contact's
stay and its costs. At least one accommodation must exist first; without
one the dialog only shows a notice that points to the CRM and, with the
permission Use CRM, the link Open accommodations in the CRMComing with the next update. The CRM contacts of the Accommodation type with
their room types and cost per night are offered for selection (see
Accommodation and room types).
You can also create accommodations on the Accommodations page and store
the defaults Daily allowance and Deduction per breakfast per
accommodation there.
The Accommodations page has no menu item
No menu entry leads to the Accommodations page. You
open it by appending /accommodation to the address of your artwork
instance. Two links lead to the page of a single accommodation
Coming with the next update: in the residency dialog below the selected
accommodation, Edit daily allowance and breakfast deduction of this
accommodation (opens a new tab, the entries in the dialog are kept),
and on the CRM detail page of the accommodation, Open accommodation
page. Both only appear if you may open the page. It can be viewed by anyone with the permission Use CRM or
with access to at least one project; creating and changing requires
Manage CRM or write access to at least one project.
In the residency you can then record:
artist or CRM contact,
accommodation and room type,
arrival and departure dates and times,
cost per night,
Daily allowance and Additional daily allowance,
Number of breakfasts and Deduction per breakfast,
description and organisation-specific CRM fields.
The number of nights results from the arrival and departure dates. From
this Artwork calculates:
costs for overnight stays: nights × cost per night,
breakfast deduction: number of breakfasts × deduction per breakfast,
payout per diem: daily allowance entitlement minus breakfast deduction.
The totals are updated with every change. Review arrival/departure days and
breakfast deductions before exporting.
Daily allowance and Deduction per breakfast are prefilled. If the
selected accommodation has its own defaults, these apply; otherwise the
general default from the artist residency settings applies. If you change
the accommodation while creating a residency, both fields are overwritten
with its defaults. For a residency that is already saved, the entered
values stay when you open it.
Do not save artist in database records a residency without creating a
permanent record for the person. If you change details of a linked person
in the dialog, Apply changes to artist in CRM decides whether they are
written back to the CRM contact.
The export offers three types: PDF-Export, Excel-Export and Per
Diem Export (per diem statement as PDF), each in German or English.
You change the name of a residency directly in the table: a click on the
name opens an input field in the cell, Enter saves, Escape
discards. This applies to all residencies; a linked CRM record remains
untouched.
A material issue connects the project with inventory. It can contain
inventory items, custom items, quantities, period, room, responsible people,
notes, tags, images, and other files. In the project view you can expand
issues, filter them by tags and check their article details, images and
files.
If the period of an issue differs from the project period, a warning icon
appears next to its name. The Material issue log (history icon above
the list) records changes and helps trace adjustments to quantities, dates,
or assignments. It opens set to the current project and can be narrowed
down by project, period, search term and issue type. Only people with the
permission Material issue log and admins see the icon.
Material issues are visible to everyone who may read the project. Team
members with write permission in the project can create and edit the
material issues of their project in the project tab, even without the
inventory permission for material issues.
Project view and inventory overview
The project shows the issues of this production. The central
material-issue overview is better for searching or filtering across
projects and rooms.
The budget table — positions, verifying and committing, templates and the Sage integration
Every project has a budget table (default tab Budget). It is only
visible to people with budget access in the project and to users with
global budget access.
Main positions (e.g. income, artistic expenses) contain
sub positions (e.g. fees, technology), which in turn contain
rows with the actual amounts.
The columns are configurable: besides the base columns (KTO, KST,
description), further columns can be created, renamed, colored and
calculated from other columns via formulas. Cells support comments and
calculations; totals run per sub position, per main position and
overall.
Exactly one column carries the flag "Relevant for budget": wherever
Artwork pulls budget data from projects (e.g. in overviews and evaluations),
only this column is used. For newly created columns the flag is set
automatically in a sensible way; it can be moved to another column manually
at any time — info texts in the table explain the behaviour. Assigning it
more than once is not possible.
With the required permissions, positions, rows, and columns can be created,
duplicated, renamed, reordered, and deleted. When reordering via drag &
drop, the message Order saved confirms that the new order has been
applied. Column colours and comments help distinguish plan, actual,
forecast, and explanatory data.
If accounts and cost centers are enabled in
account management,
the KTO and KST cells always show the entry as number – name — in the
budget table, in template and compact view and in the Excel export. There
is no longer a switch between number and name.
The account search in the KTO/KST cell searches number and name and
can be operated with the keyboard:
arrow keys move between results, Enter takes one over, Escape
closes the search. If there is only one result, Enter takes it over
directly. The search term is highlighted in the results; if you
type a number or a unique name exactly, the entry is taken over
automatically when you leave the field. If you leave the field without a
matching result, the previous value stays. In the expenses area the
search only finds expense accounts, in the income area only revenue
accounts (see
account type). The search shows at most 50 results and points out with More
results available – refine your search when there are more.
Cells may contain direct values or calculations based on other cells.
Calculated columns are useful for differences, forecasts, and percentages;
hierarchical totals update automatically. The source remains visible for
Sage postings and other imported values.
The plus icon on a value cell opens the Cell Details with three tabs:
Calculation: you build the amount from individual calculation items,
each with name, value and an optional comment. On saving, the total
overwrites the previous value of the cell; Artwork asks for confirmation
first. The tab only exists in ordinary value columns, not in sum,
difference or Sage columns.
Comment: notes on this item, with the history of previous comments.
You can only delete your own comments.
Linking: connects the value as expense or revenue to a
funding source.
If a cell has comments, a calculation or a link, it shows a small icon
for each; clicking it opens the matching tab directly. In a locked column,
calculation and linking cannot be changed.
The sum cells of sub positions, main positions and the overall total have
corresponding Sum Details with the tabs Comment and Linking.
Rows and whole columns can be taken out of the totals without deleting
them, for example for variants or items that are not yet confirmed. In the
row menu choose Exclude and later Include positions, in the column
menu Exclude column or Include column. Excluded values appear
greyed out, do not count towards SUM and are shown per section in the
separate row SUM excluded items. The switch Excluded items hidden
above the table hides them completely for your account.
Three mechanisms make the numbers binding. Besides budget access, all
three require the permission Remove verifications & locks (module Budget
& funding); admins may always use them.
Verifying: in the menu of a main position choose Get verified by
user and select the reviewing person (a four-eyes principle for the
budget). The position then shows requested to be verified. The
requested person confirms with Mark as verified; afterwards the
position shows verified. The reviewing person needs the permission
mentioned above as well.
Committing: in the menu of a main or sub position, Commitment
records the current state without a second person. Canceling a fixed
term takes this back. Commitment is only offered while the position is
neither requested for verification nor verified.
Locking a column: in the column menu, Lock locks a whole column.
Its cells can then no longer be edited, rows of the table can no longer
be deleted, and the link to funding sources is fixed for this column. The
column header shows who locked it; Unlock removes the lock.
Verifying and committing remember the values at the time of confirmation
but do not lock the cells. If a value is changed afterwards, Artwork
highlights the cell in red, and a verified main position shows a lock with
an exclamation mark. To prevent changes technically, lock the column as
well.
If the requested person does not yet have budget access to the project, the
Grant budget access dialog offers to give them this access together
with the request. An open request is withdrawn by the requesting person or
the project management with Withdraw verification request; a confirmed
verification is removed by the reviewing person or the project management
with Cancel verification. Copied positions and tables taken over from
templates always start unverified.
This allows staged approvals: one section can be closed while others remain
in progress.
A finished table structure can be saved as a budget template and
applied to new projects — so all productions start with the same chart of
accounts. Templates are managed centrally under System → Budget
(permissions View/Edit budget templates; the menu item itself requires
Budget settings); in addition, a project's table can be reset to the base
structure.
The actions are in the three-dot menu to the right of the heading
Expenses above the budget table. Which ones you see depends on whether the table still has the empty base
structure:
Menu item
Visible
Effect
Import template
only with the empty base structure
Takes a central budget template over into this project
Import from project
only with the empty base structure
Takes over the budget table of another project, including values, comments and calculations. The Sage column with its bookings, verifications and links to funding sources are not taken over
Save as template
as soon as the table has content
Saves the table under a name as a central template. Requires the permission Edit budget templates
Reset
as soon as the table has content
Resets the table to the base structure after a confirmation; all links are lost
Restore deleted columns
always
Brings back deleted columns of this table
A template can therefore only be imported into a budget that has not been
edited yet. If an already filled budget should receive a template, reset it
first.
Templates can standardise hierarchy and column logic as well as row labels.
Before resetting a budget, check for project-specific data because the reset
intentionally changes the existing table structure.
Under System → Budget you globally maintain accounts (KTO) and
cost centers (KST) in Account management, which are available for
selection in the budget rows, and the names of the first columns in the
General tab — see Budget settings.
If the Sage100 interface (tool settings) is set up, Artwork pulls
booking data from your accounting: bookings are matched to budget rows
via KTO/KST; bookings that cannot be matched land in a separate list for
manual assignment. Dedicated permissions control who sees project-related
or global Sage data.
Bookings that were not matched automatically are listed above the budget
table in the collapsible blocks Project-related Sage data and Global
Sage data (bookings without a project). Which block you see depends on
the permissions Project Sage data and Global Sage data. You assign a
booking via drag & drop:
onto the Sage cell of an existing row: the booking is counted
towards this row.
onto the line between two rows of a sub position: Artwork creates a
new row there and fills in KTO, KST and booking text.
Bookings that are already assigned can be dragged in the same way from a
Sage cell to another row. If the cell contains several bookings, a dialog
lets you choose which of them move. The trash icon on an unassigned booking
removes it from the list.
Difference and sum columns
that include the Sage column calculate with the assigned bookings from the
start.
The tab component Sage invoice overview (special component in the
tab construction kit)
shows all Sage bookings of the project as a table — those assigned to a
budget cell as well as the project-related ones not yet assigned:
Columns Creditor / name, KTO (general ledger account, otherwise
debit account, with the account name from account management), KST,
Designation, Amount, Document date and a status chip
Assigned or Not assigned.
Group headers per cost center, a total row across all bookings;
collective bookings can be expanded.
A click on a booking opens the familiar booking detail window — read
only for bookings that are not assigned.
The component is only visible with an active Sage integration and requires
budget access to the project as well as the permission Project Sage data.
If one of the two is missing, it shows a note naming the missing permission
instead of the table.
Place the component once
After the update the Sage invoice overview exists as a component but is
not yet in any tab. Drag it once into the desired tab under
Tab settings.
Project budget as Excel — the project's table. KTO, KST and
description are output as text; leading zeros such as "04000" are
preserved.
Budget export by deadline — across projects: all budgets whose
budget deadline falls within the chosen time range (the field from
the creation window).
Because this export reads the budgets of all projects, it requires the
permission Global budget access.
You start the export of the individual table with Excel-Export above
the budget table; it requires budget access to the project or global budget
access.
The project export is intended for one calculation. The deadline export is
a cross-project management tool for a selected planning or reporting period.
The budget of a project group
combines the numbers of its sub-projects in a dedicated column, which is
named Unterprojekte in every interface language. From each
sub-project the column flagged "Relevant for budget" is used; a separate
flag for project groups no longer exists. The values of those rows are
summed whose KTO and KST values match the row of the group.
For a group row to collect values, the following applies in detail:
In the group row the first two columns (KTO and KST) must both be filled.
The exact value is compared.
Expenses are only compared with expenses, income only with income.
In addition to the budget-relevant column, the Sage bookings assigned to
the matching row in the sub-project are counted.
Each value of a sub-project counts only once. If the same pair of KTO and
KST occurs in several group rows, it ends up in the first one.
Only matching sub-project rows are counted Coming with the next update. The
group row's own values and Sage bookings are not included; if no
sub-project row matches, the column shows 0.
If the amount is greater than 0, a list icon appears next to it. It opens
Details of the Selected Cell with a breakdown by project, column and
value.
Projects
Budget settings
Manage standard columns, accounts, cost units and reusable budget structures
System → Budget maintains shared foundations for project budgets. The
menu item requires the permission Budget settings (module System
settings); depending on your further permissions, you see General,
Account management and Budget templates. Changes affect new budgets
or the master data available in existing projects.
Tab
Additionally required permission
General
Global budget access
Account management
Global budget access
Budget templates
View budget templates; for changes Edit budget templates
Because these settings directly control project budget work, this manual
places them in the Projects chapter.
General defines the names of the first three columns in newly created
budget tables. Enter a clear name for each and confirm it with the tick. Empty
names cannot be saved. The names apply only to newly created budget tables;
existing project budgets keep their column names. If account management is
activated, columns 1 and 2 become select fields for accounts and cost
units, and the names entered here then only serve as headings.
Choose terms understood across the organisation. Also consider integrations:
with Sage enabled, the first two columns can represent debit account and cost
unit and their order can be defined in tool settings.
The global switch in Account management determines whether accounts and
cost units are used in every project budget as the first and second columns.
Enable this only when master data is maintained and the budget workflow
requires it. In the budget rows, accounts and cost units then always appear
as number – name; the account search in the cell is described under
Project budget.
An account contains:
account number,
description,
account type Expense account or Revenue account.
The account type controls where the account is offered: the account search
in a budget row only offers expense accounts in the Expenses section
and only revenue accounts in the Revenue section. If an account is
missing from the search, check its account type first.
A cost unit contains a number and description. Both lists can be searched,
extended and edited directly. Numbers and descriptions must be meaningful;
descriptions are limited to 255 characters.
Artwork asks for confirmation before deletion. Deleted accounts and cost units
appear in the tabs Accounts and Cost Units of the
recycle bin, where they can be restored or removed
permanently. You see both tabs with Global budget access; opening them,
restoring and permanently deleting additionally require the permission
Budget settings.
Check usage before deleting
A master-data entry may be used in several project budgets. Before deletion,
check whether historical assignments, imports or evaluations depend on it.
Renaming is more appropriate when only its label needs correction.
Budget templates preserve a reusable table structure with columns, main and
sub-positions, rows and existing calculations and comments. They let new
projects begin with a consistent calculation.
In Budget templates, you can search, expand and edit templates with the
familiar budget tools. New templates are not created here: open the budget
of a project and choose Save as template in the menu of the budget
table. This requires the permission Edit budget templates. The template
then appears on this tab. It also takes over the values in the cells; empty
the table of the sample project beforehand if new projects should start
without amounts.
Important limits apply when creating and using templates:
The Sage column and its bookings are not copied, neither when saving as a
template nor when importing a template or another project. In the target
project the Sage column is created again as soon as the first booking is
assigned to a row there. Sum or difference columns that include the Sage
column are kept and calculate without the Sage share in the copy, as do
columns that build on such a sum Coming with the next update. Saving and
importing also work when such a column comes before its source columns.
Links to specific funding sources are not retained.
Verifications are not taken over: positions of a template and of a budget
created from it start unverified.
Applying a template to a project replaces its existing budget structure.
In the project, Import template is therefore only offered while the
table still has the empty base structure; see
Budget templates.
A template replaces the project budget
Before applying one, check whether the project already contains required
positions, comments, calculations, assignments or imported data. This is not
merely an addition of a few rows.
Agree organisation-wide names for the budget columns.
Decide whether accounts and cost units are used globally.
Maintain complete, duplicate-free account and cost-unit lists.
Build and review a realistic budget structure in a sample project.
Save it as a clearly named budget template.
Apply the template to a test project and verify totals, calculations and columns.
Only then use it as a standard for further projects.
Daily work with positions, calculations, comments, approvals, funding sources
and exports is covered under Project budget.
Projects
Business intelligence in a project
Record attendance, tickets, revenue, occupancy, production data, and reporting snapshots
The Business Intelligence project component collects data for analysis
and reporting. It combines manual entries with the project's events, rooms,
and properties. Visibility and editing depend on the project settings and
the component permission. If you may only read, you see the notice
Read-only view; Data quality with the missing items is only shown
to people who may edit the component. The Export button only appears
if you may edit the component and additionally have the permission Export
BI data (module Business Intelligence).
The key figure tiles summarise values such as attendance, sold tickets,
revenue, and occupancy. Values that have not been recorded are shown as
— rather than 0, so "not entered yet" and "actually zero" remain
distinguishable. At the very top, Data quality shows how much of the
information required for a reliable report is present. Under Still
missing, each missing item is a button; a click jumps to the matching
section.
A missing value is not automatically zero. If a figure genuinely does not
apply, mark it Not relevant for this project so reports can distinguish a
deliberate exclusion from an overlooked entry.
The component follows the principle "record first, then evaluate": you
enter figures at the top, and key figures, comparisons and snapshots below
evaluate them. The save feedback names the reason if a value was not
accepted and highlights the field concerned.
The section Audience & revenue records four figures: Visitors,
Sold tickets, Revenue and Costs. Costs are always entered as one
total for the project. The other three can be entered in one of two input
modes:
Input mode
Use
Total
One figure for the whole production.
Per event
Relevant project events receive individual values and Artwork calculates totals. Required for period comparisons and the monthly trend in the BI dashboard.
In per event mode a table of the project's events appears. By default
it shows Audience events only — events whose event type carries the BI
tag for performances; Show all events adds the rest. The table can be
searched and sorted by room and event. Several selected rows can be filled
with a common value; events in the future are marked as such. The total row
shows the current state; occupancy is calculated from sold tickets and the
effective room capacity.
Do not switch the input mode casually
Switching between total and per-event recording discards the figures of
the other mode. Artwork asks for confirmation; export or note any values
you still need first.
If attendance is missing, Artwork may provisionally estimate it from sold
tickets and labels the figure as an estimate. With Break down by
category you record the tickets per audience category (full, reduced,
free); from these Artwork derives rates such as the paying rate. Adopt
sum enters the sum of the paying categories as sold tickets.
For Revenue (input mode Total) and Costs, Artwork suggests a value
from the budget where available: in the actual view the Revenue from Sage
bookings or Costs from Sage bookings, in the plan view the Income
side or Expense side of the project budget. Adopt value enters the
suggestion; you can overwrite it at any time.
Next to the title of the component you switch between Actual and
Plan. In the plan view you record the expected visitors, tickets,
revenue and costs; the actual figures stay untouched. When you open it for
the first time, you choose the starting point:
Choice
Effect
Start empty
Creates empty plan values
Copy structure from actuals
Takes over the input modes of the actual view, but no figures
Copy values from another project
Searches for a project and takes over its actual figures for visitors, sold tickets and revenue as plan totals, for example the predecessor production of a revival
As soon as plan values and actual figures exist, the actual view shows the
Plan vs. actual comparison with difference and Attainment.
Production data, capacities, time efforts and custom fields are maintained
only in the actual view; they apply to both.
Artwork initially uses the room's Default capacity. Enter a
Project-specific capacity if this production uses a different seating
layout. The Effective capacity column shows which value is used. The
table only lists rooms in which the project has events. Maintain capacity
before judging occupancy; no reliable percentage can be calculated without
it.
The standard production information records whether the project is a new,
co-, or in-house production, whether it is a German premiere, and the
premiere date. These fields can be exported across projects for statistics
and funding reports.
Artwork calculates further values from the project, events, and BI entries.
Configured BI tags can group event types for reporting without changing the
event types shown in the calendar.
The key figures performances, event days and occupancy are only
calculated if the respective BI tag is assigned to at least one event type.
Which tag controls which key figure is set in the tag dialog under
System → Events → BI tags with Controls key figure — exactly one
tag controls "Performances" (also the capacity basis of the occupancy
rate), one controls "Event days". Without the assignment, — is shown
with a hint; there is no fallback to all events.
Correct the source event, capacity, or entry rather than trying to
overwrite a derived value.
Record a named effort in one of the ranges 0–10, 10–25, 25–50,
50–100, or 100+. The name should identify the area being assessed, such
as “production management” or “technical preparation”. The creator remains
visible on the entry.
The ranges are estimates in hours. They enter the
effort score
of the BI dashboard with fixed hour values: 5, 17.5, 37.5, 75 and 125 hours.
A snapshot (German label: Stichtag) preserves the project's current
BI values under a name and date. Use it for planned, interim, and final
reporting states.
Enter a name and date.
Under Data set, choose whether the actual figures or the plan values are preserved.
Create the snapshot to preserve the current values.
Select a snapshot via Compare snapshot with current values.
Review differences and trends.
Snapshots do not change with live project data. Deletion is permanent.
The Period comparison and the Attainment shown in the component
refer to the live values instead. The period comparison contrasts two
periods, optionally with Previous year or Previous period as the
comparison; it only shows figures recorded per event, because totals cannot
be assigned to a period. Attainment relates the actual figures to the
plan values.
Administrators can add organisation-specific text, number, selection, and
other fields; in the component the section is called Custom fields.
They can also contribute to the data-quality indicator.
You open the BI export in the project's BI component or in the
BI dashboard; it is the same dialog. It requires
the permission Export BI data and covers all productions of the house,
regardless of your project access. It can cover multiple projects and a
date range; opened from the project, the range is prefilled with the
project period.
Under Export structure you decide what the file contains: Project
rows only, Event rows only or Projects and events (2 sheets). The
events sheet always has the same columns; the column selection applies to
the productions sheet. In addition, productions can be filtered by cost
bearer and events by BI tags.
The column selection is grouped and
searchable: select columns for master data, project period, capacity,
attendance, tickets, revenue, occupancy, production details, BI tags, and
custom fields. Save common column combinations as presets with unique
names. While the Excel file is being created you see a waiting state with
Cancel export. The data sheets are called Productions and
Events; they have a frozen header row, autofilter and real date,
currency and percentage values. The Info sheet is always included, even
with only one data sheet, and states creation time, creator, period and its
source, export structure, BI tag filter and the productions included.
Export files stay available for 24 hours — only to the person who started
the export; after that you have to create the export again. Before downloading, verify the date range, projects, and
selected columns against the reporting state you intend to deliver.
The project settings live under System → Projects (permission Project
settings) and are organized into tabs: Project Settings (master data
& creation toggles), Artist residencies, Project Role Settings,
Tab Settings, Component Settings, Print Layout Settings,
Project overview builder and BI Field Settings. The biggest lever,
the tabs & components of the
project view, has its own page; this one covers master data and toggles.
Each entry consists of a name and a color. New entries, renames and
deletions are saved immediately; deleted entries are in the
recycle bin.
Projects can carry several values per list; one of each can be marked as
the main category/genre/sector. The display option Event color by main
category uses this in the calendar.
Freely definable statuses with a color (e.g. idea, in planning,
confirmed, cancelled). Add Status creates a status; clicking an
existing status opens it for editing.
In the status window you can tick Project counts as "in planning".
Such statuses carry a calendar icon in the list. The marker is more than a
visual label:
In the project's event entry (the
project schedule and Set up
events when creating a project) the switch for planned events is
preset for a project in this status. New rows are then created as
planned events instead of fixed
events, as long as you do not change the switch. The browser remembers
your choice per project. Events you create in the calendar do not follow
the project status.
Existing events do not change by themselves. When a project moves into
or out of such a status via Edit basic data, a dialog offers to
convert the events or to request their verification (see
Header).
Choose the colors so that the status is quickly understood in the project
overview and the calendar.
These toggles determine which fields the
creation window
offers — keeping it as lean as your process allows:
Toggle
Field in the creation window
Project Attributes
Category / genre / sector
Project status
Status selection
Project management
Project management selection
Cost bearer
Name of the cost unit
Budget deadline
Deadline date field. The toggle also shows the tab Budget export by deadline in the export of the project overview.
Artists
Artists field
The toggles also apply to the Edit basic data window: a field that is
switched off is missing there too. Changes are saved immediately.
Two further toggles on the same page take effect beyond the creation
window:
Project status as a required field (in the Project Status
section): a project status must be selected when creating a project; an
assigned status remains changeable when editing the base data but can no
longer be removed.
CRM contacts in project team — CRM contacts can additionally be
linked in the project team as
external team members
and given project roles.
Project roles (e.g. direction, dramaturgy, production
management) are defined in the Project Role Settings tab and assigned
in the project team. Each user can
have default project roles in their profile, which are preselected when
they are added to a team. Project roles are plain labels and grant no
rights. They appear in the project team, in the person's profile and in
the export
Excel Project Role Overview.
If CRM contacts in project team is enabled, they can also be assigned
to CRM contacts in the team.
The same page also maintains Contract Types, Company Types and
Currencies (for the contract module); there are additionally separate
settings pages for artist residencies and the
budget settings.
The project overview builder determines which columns and contents the
project list
displays, so the overview, too, can be adapted to your venue. The
selection only contains components that work as a column (no separators
or titles, no large tools such as calendar, shifts or budget), and each
component only once. Remove a column via its three-dot menu with
Delete; the component and its project values are kept. The columns for
the project title and the actions are fixed and can only be moved. Every
change is saved immediately.
The overview builder is arranged by drag and drop. Typical contents include
period, status, artists, properties, project team, group, and BI figures. The
layout is central, while each user's filters and sorting remain personal.
Print layout settings define what the project PDF looks like: you assemble a
layout from the printable components of the project view (title, base data,
texts, properties …); when printing from the project header, users then
pick one of the layouts. This way there can be, for example, an internal
info sheet and a rental exposé from the same project data.
Print layouts can include headings, custom text, base data, period, status,
team, properties, shift and budget information, document lists, and other
printable components. The PDF always uses current project data.
Placed components are rearranged via drag & drop: you can move them or
swap their places, also across the areas of the layout. The component
search also finds special components by their German name.
A layout consists of a Header (1–5 columns), a Body (1–3 columns)
and a Footer (1–5 columns); the column counts are fixed after
creation. With a one-column body all special components can be used.
Each header and footer column can carry a free note. Only layouts with
Should this print layout be available? switched on can be chosen in
the project. Printing runs via the printer icon in the project header and
the browser's print dialog (Save as PDF).
Print layouts respect visibility
A layout only outputs what the printing person may also see in the
project view: components with restricted visibility or from tabs
invisible to them stay empty, and document, comment and checklist lists
only contain content from visible tabs. Deactivated layouts can only be
opened with the project settings permission.
The Artist residencies tab contains default values. They are
pre-filled when someone creates a new residency in a project and can be
overwritten there. Existing residencies are not changed by a new default.
Setting
Effect
Deduction per breakfast
Amount deducted per breakfast
Default daily allowance
Pre-fills the daily allowance field of a new residency
“Do not save artist in database” checked by default
Ticks this checkbox in advance for new residencies
Name columns in the artist residency table
Which name columns the table shows and in which order
The BI Field Settings tab (permission Tool settings) bundles the setup of
the BI module:
The setup checklist at the top of the page shows in seven steps what
the module still needs — enable the BI module, assign the key-figure
tags to event types, place the BI component in a project tab, enter seat
capacities for rooms, check audience categories, set the season window,
grant BI permissions. The status is read live and every step links
directly to the relevant page.
Audience categories structure how ticket numbers are recorded (full,
reduced, free).
BI fields are free additional fields for venue-specific figures.
Which event types count as performances or event days is defined in the BI
tags under System → Events → BI tags: in the tag dialog, Controls key
figure decides whether the tag controls "Performances" or "Event days".
There is no separate menu item for the BI export any more; the export sits
in the BI dashboard and in the project's BI
component. Their day-to-day use is covered in
Business intelligence in a project.
Central settings may still be referenced by existing projects. Deleted
genres, categories, sectors, project statuses, contract types, company
types and currencies therefore end up in the
recycle bin in the
sidebar, tab Project Settings (permission Open trash). From there
they can be restored or removed permanently; both additionally require the
permission Project settings. Check current use before permanent deletion.
Projects
Tabs & Components
Assemble the project view from components — the construction kit behind the tabs
The project view is a construction kit: which tabs exist, what is on
them and who may see what is configured by administrators under
System → Projects in the Tab Settings and Component Settings
tabs (permission Project settings). Changes affect all projects.
Create tab adds a new tab; name and order are up to you — the order
is sorted via drag & drop.
A tab can be marked as the default tab via Set as default tab: it
opens when someone opens a project. In addition, every tab shows its
visibility ("Visible for all" or restricted, see
Restricting and deleting tabs).
Every tab contains an ordered list of components; it can additionally
have sidebar tabs — narrow sub-sections on the right (in the default
setup e.g. project information, shift information, budget
information).
Folder components (collapsible containers) group components into
expandable/collapsible sections. Folders cannot be nested, and the large
tools do not fit into them: Calendar, Shifts, Budget, Bulk Event Create
Component, Artwork-Tickets as well as All Checklists, All Comments
and All Documents.
Create tab from template next to Create tab adds a fully
equipped tab. Every template has a description; templates with a sidebar
show Including sidebar with the names of the sidebar tabs, and Show
components lists all components of the template in advance. You can
choose from:
the default tabsProject Information (with the orange sections
Descriptions for the text areas Short description, Website text
and Press & public relations, and Documents with the file upload),
Schedule, Checklists, Shifts, Budget and Comments. Each comes
with a sidebar: Shifts with Shift information, Budget with
Budget information, all others with Project Information. This is
handy if a default tab was deleted by mistake or a new venue wants to
start with the proven layout;
the Production inquiry template: an inquiry form with coloured
sections for contact & company, artists (with the CRM contact list
Names of everyone arriving), general information, documents (file
upload), music & rights, anything else, texts & description, marketing
material: images & video, and sponsors & partners. It has no sidebar
and is meant for collecting data from guest performances, also in
combination with external access.
The result is always a normal tab: the template only saves you the manual
setup, and you can rename, rearrange, extend or delete the components like
any other. The new tab is placed at the end of the tab bar and is visible
to everyone. Its texts and field names are created in the language of the
person who creates it. Text fields, section titles and the CRM contact
list are created as new custom components each time: if you apply the
same template twice, these fields exist twice, with separate contents.
Standard components such as the file upload or the budget are reused
instead.
All project tabs follow a uniform, left-anchored layout: tools such as
calendar, shifts, budget and schedule always run across the full width,
tables and lists in a uniform column, text and form components in reading
width.
To the right of the tabs is the palette with all components, grouped by
type and with a search field. You drag a component to the desired place
via drag & drop or use the plus button on the component: the Add
component window offers Add to this tab, Add to folder and Add
to sidebar and appends the component to the end of the selected area.
Used: N on a component means it is placed in N tabs. In every one of
them it shows the same data record per project.
Requires configuration is shown on File upload, Comments and
Checklist. When you drop the component you choose which tabs it
collects its content from: Only include current tab or a selection
of several tabs. For the file upload you change the selection later on
the placement (see File upload and upload areas).
To change it for Comments and Checklist, remove them from the tab
and place them again.
You fill the sidebar of a tab via Add sidebar tab. Folders and some
components cannot be placed there.
In the Create tab or Edit tab window you define the visibility in
addition to the name. With Visible for all, everyone who may open the
project sees the tab. If you switch the option off, you select users and
teams; only they and admins then still see the tab. A restricted tab
cannot be opened via its direct address either. If you select nobody,
nobody except admins sees it.
Delete tab asks for confirmation first. The following applies:
The last tab cannot be deleted; at least one project tab must be
available.
The components themselves and their values in the projects are kept.
Only their placement in this tab is removed.
Comments, checklists and documents of a tab that is visible for all stay
visible for all. For a restricted tab, only admins see them afterwards.
A tab should represent one clear work context, such as communications,
technical planning, or finance. Details needed almost everywhere are often
better placed in the sidebar. The default tab should contain what most users
need first when opening a project.
Freely creatable contents that are filled in per project. You create them
under Component settings with Create a new component and then drag
them into a tab. You can create as many of the same type as you like, for
example one CRM contact list “Arriving people” and a second one “Artists”.
The type cannot be changed after creation. An update does not create
custom components: new types only become available for selection. A
component marked 0× exists but is not placed in any tab yet and is
therefore not visible anywhere.
Component
Contents
Title
Heading with selectable font size, an optional Text below the heading and an optional Section bar in a color of your choice
Text Field / Text Area
Single- or multi-line text
Checkbox
Yes/no marker, activated by default if desired
Drop Down
Predefined options, optionally with a default. Allow multiple selection permits several values per project.
Multiple choice (checkboxes)
Predefined options as checkboxes, several values per project, optionally with Default options
Link / Link List
A single link or a collection; the link list has an upper limit (Max links)
Separator
Spacing with adjustable height, with Show a separator line if desired
Folder component
Collapsible container for other components
CRM contact list
CRM contacts in the project, such as arriving people, see CRM contact list
For text field, text area and link components, the configured
placeholder is a real placeholder: it appears in the empty field and
disappears as soon as something is entered. A component therefore needs its
own label in the component settings if it should be named permanently.
You reorder the options of drop-downs and multiple-choice components in
the component settings by dragging, without deleting them. Allow
multiple selection can only be switched off again as long as no project
has selected several values.
Deleting removes the project values
If you delete a custom component in the component settings, all values
already entered in projects are removed as well. If a component should
only disappear from one tab, remove it there in the tab settings.
Special components cannot be deleted.
A CRM contact list collects CRM contacts in the project, for example the
people arriving for a guest performance. In the component settings you
define, besides Title and Hint text:
Allowed contact types: Only contacts of these types can be created
or linked in the list. Each type gets its own button in the project with
the form based on its CRM properties. Without a selection, all contact
types are allowed. Freelancers and service providers are maintained in
their own profile; they can only be linked, and only if you select them
explicitly.
Maximum number of contacts (optional): Empty means no limit.
Use rolesNew in 1.9.0: Contacts are grouped in the
project by roles you name freely. The special role Artist shows a
person as an artist of the project everywhere, for example in the
calendar, the duty roster and exports.
In the project you add contacts with Add ‹contact type› or with
Link existing CRM contact. Removing a contact from the list does not
delete it from the CRM.
External people
can also fill the list.
Ready-made function blocks, called Special components in the
interface. Each exists exactly once and can be placed in one or more
tabs. The name in the palette is given in brackets where it differs. The
most important ones:
Component
Function
Project title / base data (Project basic data) / project status
The project's header data
Project properties (Project Attributes)
Category, genre, sector
Project team
Team list with rights and roles
Project group display (Project Group, Project group display component, Component Subprojects)
Group ↔ member projects
Calendar tab (Calendar)
The project calendar
Schedule (Bulk Event Create Component)
Tabular bulk event creation
Project period
Automatically calculated time range
Checklist / All checklists
One specific or all checklists
Shift tab (Shifts), Shift Contact Persons, General Shift Information, Relevant Dates For Shift Planning
Special component: all Sage bookings of the project, only with an active Sage integration. It is created during the update and must be dragged into a tab once.
Ticket sales for the events of the project. The component is only offered if your instance is connected to Artwork-Tickets.
Many standard components expose connected data in a project context. The
period is calculated from calendar events, the shift tab opens the global
duty-roster logic for this project, and material issue links to inventory.
Consider the workflow a component starts as well as its appearance.
Every placement of the File upload component in a tab or folder is its
own upload area. It shows the files of the tabs you select when
placing it.
Default visibility: A new file appears in all upload areas whose tab
selection contains the tab in which it was uploaded.
Changing the tab selection: In the tab settings the placement has
the line Shows documents from tabs with Edit (window Edit tab
selection). If the file upload sits in a folder, remove it and place
it again instead.
Upload settings: Per area, Edit in the line Upload settings
limits the allowed file types (Only allow certain file types), the
Maximum file size (MB) and the Maximum number of files per
project. Empty fields mean no additional limit. Only file types and
sizes within the
file settings can be
chosen. The number counts the files uploaded via this area. The limits
are shown in the project below the upload field.
Redistributing in the project: If there are several upload areas,
New files visible in lets you decide before uploading where new
files appear. On every file a badge shows Only here or Also in n
other area(s). Clicking it opens Visible in, where you choose the
areas for this file or reset it to the standard. At least one area must
stay selected. This requires write permission in the project.
Independently of this, All Documents shows all files of the project
from the tabs the respective person may see. Examples for dividing things
up and protecting confidential files are under
Distributing documents deliberately.
Every component – your own as well as the standard ones – may sit in
several tabs and shows the same record of the project there. A field
placed in the Technology and Production tabs is therefore maintained
only once. Permissions apply to the component and thus in all tabs; for
different rights you need a separate component. Examples and how to handle
documents in restricted tabs are described in
Setting up the project view.
One component, one place
The "all …" variants (all checklists, all comments, all documents) show
the project's entire contents. The single variants only show the
contents of the tabs you select when placing them, in the simplest case
only those of their own tab. So, for example, every craft can have its
own tab with its own checklist and its own comments.
Basic rule: seeing a component always requires access to the project,
editing always requires write permission in the project (the Write
permission or Project management checkbox in the
project team or the global
permission Write all projects). The settings in the
component settings can narrow this circle further, but never extend it.
Per component you choose:
Setting
Meaning
No further restriction
Visible to everyone with project access, editable by everyone with write permission in the project
Visible to everyone with project access, but editing is additionally limited to …
Readable by everyone in the project; editable only by the named users or departments — and only if they also have write permission in the project
Only visible to the following …
Visible only to the named ones; editing additionally requires write permission in the project
This way the budget information, for example, stays reserved for the
administration while everyone sees the short description. For Title,
Separator, Shifts, Budget and Calendar this setting does not
exist: titles and separators carry no content, and access to shifts,
budget and calendar follows the user permissions and the project (for
example the Budget access checkbox in the project team). Admins always
see every component. The permission Write all projects only
lifts the editing restriction of components a person can see – “Only visible
to the following” also applies to these users. The rules are also checked on the server — they match exactly
what the interface offers. The content of a component a person may not see
is never sent to their browser and does not appear in
print layouts either.
In the component dialog an info icon on every field explains what it does;
the texts depend on the component type.
External accesses see the whole tab
If a tab is shared via an external access,
the internal visibility settings of the components do not apply to the
invited person. They see all custom components of the tab (title, text
field, text area, checkbox, dropdown, multiple choice, link, link list,
separator, folder, CRM contact list) plus the standard components
Project title, Project basic data, Artists and File upload. They
do not get to see any other standard component, such as project team,
comments, checklists, calendar, shifts or budget. With write access they
can fill in the custom input components, the CRM contact list and, if
Allow file upload for external accesses is enabled, the file upload; project title, basic data and artists stay read-only for
them. Create a dedicated tab for exchanging data with externals, for
example from the Production inquiry template.
Tab visibility, the project permission and the permission of the individual
component work together: a person needs access to the project, to the tab
and to the component within it; editing additionally requires write
permission in the project. Specialist permissions can additionally apply to
budgets, contracts, or material issues. After larger changes, check the
result with a typical project-team role (with and without write
permission), an administration role and an external-access role.
The shipped setup (project information, schedule, checklists, shifts,
budget, comments) covers most venues. It has proven best to create new tabs
only once a department repeatedly needs contents of its own: every
additional tab is one more click for everyone.
BI Dashboard
Overview
Understand organisation-wide figures, trends and production comparisons
The BI Dashboard consolidates the business-intelligence data recorded in
projects into an organisation-wide steering view. While the regular
Dashboard shows today's personal work, the BI Dashboard
answers questions such as:
How many visitors, how much revenue and how many performances were recorded?
How are visitor numbers and revenue developing compared with the previous year?
Which sectors or production categories contribute to the results?
Which productions show a notable relationship between effort and output?
Where are BI figures still missing?
The menu item is only visible when the BI module is enabled and your account
has the permission View BI dashboard. The buttons Excel-Export,
Budget export and Export table only appear with the permission
Export BI data, which includes viewing the dashboard.
The dashboard has two views that you switch at the top:
View
Content
Overview
KPI tiles, data-gap notices, monthly trend, revenue and visitors by category
Steering
Effort vs. output and the production table
Below the header, one sentence states which evaluation period currently
applies — it affects all tiles, charts and the table. The category
filter is a real page filter: clicking a category filters the whole
dashboard, not just the table. Excel-Export opens the shared
BI export dialog,
prefilled with the dashboard period. Next to it is the
budget export.
By default, Artwork uses the season window defined in the tool settings
under Communication & Legal.
If no season or an invalid one is configured, the dashboard uses the current
calendar year and shows a notice with the link Set season window.
Alternatively, you can use these presets:
Selection
Effect
Season (default)
Uses the centrally configured season start and end
Calendar year
1 January through 31 December of the current year
Last 12 months
Rolling period ending today
Free choice
A freely selected date range via the fields From and To, both days included
For Season and Calendar year you step with the arrows next to the
selection to the previous or next season or year without typing dates;
preset and offset are part of the URL, so the view can be shared as a link.
From and To fields only appear for Free choice. After entering dates
manually, select Apply. The To date cannot precede the From date.
Below the period selection, Comparison defines what the tiles and the
monthly trend are compared with:
Selection
Effect
Previous year
Default: the equivalent period shifted back by one year
Previous period
The period of the same length directly before the evaluation period
Free choice
Your own comparison period via From and To, confirmed with Apply
No comparison
Hides the change values
Projects whose figures are only recorded as totals cannot be assigned to a
period and are therefore not part of the period comparison. The dashboard
states their number below the tiles.
Budget export in the header creates an Excel file with all budget rows
of the projects that have events in the selected period; with an active
Sage interface including the Sage actuals. The dialog is prefilled with the
dashboard period. You can narrow down the rows:
by Account number: type the beginning of the number into the field
below Filter by account number (prefix match). Two buttons then show
the number of matching rows in the first two budget columns (by default
account and cost center). Only a click on one of them adds the input as a
filter; it then appears as a chip “… starts with …” below the field. An
input that is only typed does not filter,
by Cost bearer: the selection limits the export to projects with
these cost bearers. Without a selection all of them apply.
You can change the period in the dialog; without From and To,
Export stays disabled.
Several filter values of the same column are combined with OR, filters of
different columns with AND. With an active Sage interface, an additional
option restricts the Sage bookings to the document date within the period.
The export is house-wide and independent of your project access.
Missing figures are not automatically extrapolated in totals. Values that
have not been recorded are shown as — so they are not confused with a
real zero; productions without figures still pull totals towards zero. Use
the data-gap notices and mark figures Not relevant in the project when
they deliberately do not apply.
Interpret KPI tiles, estimates, warnings and quick entry correctly
The KPI tiles summarise the selected period across all productions. Where
appropriate, a green or red percentage shows the change from the selected
comparison period, by default
the previous year. If no comparison is shown, the comparison value may be
zero or unavailable. Values that have not been recorded are shown as —,
not 0. An info tooltip on every tile explains how the figure is calculated;
a legend below the production table describes the colour logic: occupancy green from 90 %, blue from
50 %, yellow below; attainment green from 100 %, yellow from 80 %, red
below; costs green up to plan, yellow up to 120 % of plan, red above. If
plan values
are recorded in the projects, the tiles additionally state the plan value
and the attainment.
Total recorded attendance; missing values may be estimated from sold tickets
Revenue
Total revenue recorded in BI data
Costs
Sum of the recorded total costs. The tile only appears if at least one production has recorded costs, and only counts these productions
Occupancy rate
Sold tickets in relation to the seat capacity of the rooms played in the period
Event days
Number of days with events whose event type carries the BI tag "Event day"
Performances
Number of events whose event type carries the BI tag "Performance"
Productions
Number of regular projects with at least one event in the period, whether or not all BI figures are complete
Recorded
Productions in the period that have at least one BI figure (or are marked as not relevant); the others pull every total towards zero
An ≈ before the visitor total means that at least one value was estimated
from sold tickets. The estimate is useful for orientation but is not a
substitute for confirmed attendance.
For visitors and revenue, figures recorded per event only count with the
events in the period; figures recorded as a total count in full as soon as
the production has an event in the period.
If productions in the period have broken down their tickets by audience
category, a second row appears below the tiles: Tickets issued, Free
tickets with Free ticket rate, Reduced tickets with Reduced
ticket rate and Paying rate.
For occupancy, Artwork adds sold tickets and effective capacities across
productions and calculates an overall ratio. It is not a simple average of
the displayed project percentages.
BI tags classify event types as performances or event days for reporting.
Which tag controls which key figure is set in the tag dialog under
System → Events → BI tags with Controls key figure: exactly one tag
controls "Performances" (and thus the capacity basis of the occupancy
rate), one controls "Event days". Renaming a tag does not change this.
If the controlling tag is not assigned to any event type, the dashboard
displays a warning and shows Performances, Event days or the
occupancy rate as — with a hint — even when calendar events exist. There
is no fallback to all events.
Configure BI tags takes authorised users to the BI tags. Assign the
appropriate event types there. This does not change the events themselves;
it defines how they contribute to reporting.
Artwork flags productions that have events in the selected period but no
overall or per-event visitor, ticket or revenue figures. These gaps pull the
overall evaluation towards zero and should be reviewed before reporting; the
Recorded tile shows how many productions already have figures.
A production is not considered a gap if all three figures have deliberately
been marked Not relevant. This distinction identifies whether information
is missing or genuinely does not apply.
Click a project name in the data-gap warning. A click on a production in
the production table, by contrast, opens the project's BI tab directly.
Quick entry lets you record project totals for:
visitors,
sold tickets, and
revenue,
or mark a figure Not relevant. Existing values are prefilled — you only
change what is new. Artwork refreshes the dashboard after saving. Open
project takes you to the project's complete BI view.
In quick entry you can only save for projects in which you have write
access: with the global write permission for projects, as a team member
with write access, as project management, as the creator, or through a
department assigned to the project. The permission to view the BI dashboard
is not enough; without write access the dialog reports an error when you
save.
If the BI component is not included in any project tab, the dashboard shows
a warning at the top with the link Open tab settings. As long as it is
missing, BI figures cannot be maintained in the projects.
Quick entry stores project totals
It does not distribute figures among individual events. If a figure is
already recorded per event in the project, totals do not apply here; quick
entry points this out. Maintain event-specific visitor, ticket or revenue
data in the project's BI tab in the Per event input mode.
Does the selected range match the reporting period?
Are the controlling BI tags assigned to the relevant event types?
Have all reported data gaps been resolved?
Are estimated visitor figures sufficient for the intended purpose?
Are room and project capacities current?
Have non-applicable figures been explicitly marked?
You can also create a project
snapshot to preserve a
reporting state. The BI Dashboard itself shows the currently available source
data for the selected period.
BI Dashboard
Charts & steering
Explore trends, categories and effort/output comparisons down to each production
The BI Dashboard moves from trends over time and categories to individual
productions. The Overview view contains the monthly trend and the
category charts, the Steering view the effort-vs.-output chart and the
production table. Charts provide orientation and reveal notable patterns;
any business interpretation should also consider the period, data quality
and project context.
The Monthly trend chart uses only per-event BI entries because these have a
specific date. It shows:
visitors per month as bars,
visitors in the corresponding month of the comparison period (by default
the previous year) as a dashed line,
revenue per month on a second scale.
Figures entered only as project totals do not appear in the monthly chart, but
can still be included in the KPI totals. The sum of the monthly bars may
therefore differ from the visitor or revenue tile.
For very long ranges, Artwork limits the chart to a maximum of 36 months to
keep it readable.
Revenue by category and Visitors by category group productions by their
main category or sector. If no main category has been set, Artwork uses the
first assigned category; productions without a category appear under a neutral
entry.
Click a segment or bar to filter the whole dashboard — tiles, charts and the
production table — to that category. The active category is displayed and
can be removed there. This filter is temporary and does not modify any
project.
The scatter chart in the Steering view compares each eligible production
using:
horizontal axis: Effort score,
vertical axis: revenue when revenue data is available, otherwise visitors.
The coloured quadrants compare each production with the median across all
productions in the current period:
Colour
Classification
Red
high effort, low output
Green
low effort, high output
Indigo
high effort, high output
Grey
low effort, low output
Click a point to open its project. The chart appears once at least three
productions in the period have figures.
A comparison, not an automatic judgement
“High” and “low” refer only to the median among the productions currently
being compared. Artistic quality, strategic importance, public remit and
special production circumstances are not assessed automatically.
Effort ranges recorded in a project are converted to representative hour
values for this calculation: 0–10 counts as 5, 10–25 as 17.5, 25–50
as 37.5, 50–100 as 75 and 100+ as 125 hours. The info tooltip on the
column heading Effort score states the formula. The score is not a time
account or cost calculation. It provides a consistent comparison for
internal steering.
bookings per performance (only with an active Sage interface),
tasks plus documents per production,
effort score,
once plan values exist: plan visitors, plan revenue, plan costs, costs
attainment and attainment.
The table is initially sorted by effort score in descending order. Click a
column heading to sort ascending or descending. Metrics per
performance show a dash if no performance is available as a denominator;
values that have not been recorded are also shown as —. Clicking the
name of a production or the pencil icon Maintain figures in the project
opens the project's BI tab.
Export table hands the table over to the
BI export.
The occupancy bar offers quick visual guidance, colouring low, medium and high
values differently. The displayed percentage and the quality of its ticket
and capacity data remain decisive.
In Steering, sort the table by revenue, occupancy or effort.
Open affected projects and review source data and circumstances.
Only then draw conclusions or prepare reports.
Calendar
Overview
What the calendar is and how events, rooms and approvals fit together
The calendar is Artwork's room occupancy and event planning module:
performances, rehearsals, setups and teardowns, blockers — everything is
planned as an event into a room. The grid shows days as rows and
rooms as columns, so you see occupancy and free slots at a glance.
The calendar is also the starting point for project and staff planning: an
event can be assigned to a project, determine its period, contain sub-events
and a production timeline, and provide the context for shifts. Changes to an
event are therefore immediately visible in the project and the duty roster.
A calendar entry with an event type, a time range (or all-day), a room and an optional project.
Event type
The category of an event (e.g. performance, rehearsal, setup, blocker) with a color and abbreviation — configurable, including mandatory fields and a verification mode.
Event status
An optional add-on module: freely definable statuses (e.g. requested, confirmed) with a color — the calendar can color events by status or spell the status out on the tile.
Event properties
Configurable attributes such as Publikum (audience) or Laut (loud), shown as icons on the event and available as filters.
Series
A repeating event with frequency, weekdays and end — changes apply to one event, to this and following events or to the whole series, see Editing series.
Room booking request
Anyone who may not book a room directly submits a request — room admins accept or decline. Not used when "Events always bookable directly" is active.
Planned event
An event in the planning calendar: provisional and invisible to regular users until it is adopted.
The separate space for provisional planning. Only visible with the permission View planning calendar or Edit planned events, and as long as the "Planning calendar" module is enabled.
Event Verifications
Incoming room booking and verification requests, plus your own sent requests. The entry disappears when the setting Events always bookable directly is active.
Narrow down period and rooms. Choose the period you need and use
filters for areas, rooms, properties, event types and project status.
Create the event. Event type, time, room, project, description and
properties provide its working context. Repetitions and sub-events cover
series and detailed day schedules.
Coordinate room and content. Artwork shows potential occupancy
conflicts. Depending on room rights, the event is booked directly or
requested from the room admins — unless your organisation has switched on
direct booking for all events.
Have provisional plans verified. Provisional season planning is created
in the planning calendar. A planned event becomes a fixed event through
verification; the verification mode of the event type defines who has to
verify.
Continue and publish. Maintain further events in the project table,
create shifts in the duty roster, and pass approved information on through
exports or calendar subscriptions.
Three different approvals
A room booking request asks in the regular calendar whether a room
may be used. A planned event is a provisional planning-calendar
entry. Event verification turns a planned event into a fixed one: it
only exists for planned events, and an event confirmed this way is firmly
booked without an additional room booking request. With the setting
Events always bookable directly,
room booking requests and event verification are dropped entirely; only
the planning calendar remains as a provisional stage.
Submit booking requests in all rooms, also as a series or for several cells via the calendar's multi-edit, and edit your own events
Plan events directly (Termine fest planen)
Book events directly in all rooms; answer room requests; edit, decline and delete other people's events; create several events at once in the project's event list; save timeline presets
Open the planning calendar and see planned events, also in the regular calendar via Show planned events. Read only.
Edit planned events (Geplante Termine bearbeiten)
Edit, move, duplicate and delete planned events, convert fixed events to planned events, request and withdraw the verification of all planned events
Plan directly in the planning calendar (Im Planungskalender fest planen)
Create planned events in all rooms and request verification for your own. Independent of Plan events directly; room admins create planned events in their own rooms without this permission.
View day remarks (Tagesbemerkungen sehen)
See the day remarks column in the calendar, planning calendar and duty roster
Edit day remarks (Tagesbemerkungen bearbeiten)
Create, change and delete day remarks
View duty rosters (Dienstpläne einsehen) or Plan shifts (Schichten planen)
Use the display setting Show shifts in the calendar
In addition, every room grants its own rights: room admins (edit the
room and approve occupancies) and users authorized to request — see
Event Verifications.
Series are not tied to a permission of their own: whoever may create an
event can also repeat it. If you may only request the room, all events of
the series are created as room requests.
When ‘Events always bookable directly’ is active
Everyone who may create events then books directly in the calendar.
Request room occupancy acts like "create events", and Plan events
directly only still covers editing, declining and deleting other
people's events, events without a room and timeline presets. The
permissions page marks affected rights as "Without effect" or "Partly
without effect". Creating planned events still requires Plan directly in the
planning calendar; they are then confirmed as fixed events without a
verification step.
Calendar
The Calendar View
Working with the event calendar — navigation, filters, display settings, daily view and multi-edit
Open the event calendar via Calendar → Calendar in the sidebar. The grid
shows days as rows (grouped by calendar week) and rooms as columns;
each cell contains that room's events on that day as colored cards with the
type abbreviation and time.
Click a room heading to open its room view. Long room names wrap onto up to
two lines in the header; if a name is still truncated, hover to see it in
full. Clicking an event card opens the event — read-only if you have no
edit rights, otherwise as an editable form. The project symbol on a card
links directly to the associated project.
The time range and the view switches sit on the left, the tools on the right:
Element
Function
Time range
Two directly editable date fields with the weekday, followed by the calendar weeks and number of days (e.g. "CW 12–14 · 21 days"). The arrows Time range back / forward shift the range by its own length, or by one month for a whole month. The calendar icon opens Select period with the mode chips Day, Week, Month and Free selection, the quick selection (Today, Current week, Current month, Current year, Next 7/14/30/90 days, Next 12 months) and two month calendars; clicking a calendar week number selects the whole week. Keyboard: when the time range bar has focus (not inside a date field), ←/→ page and T jumps to today. In the open window, Enter applies the selection and Esc closes it. The calendar shows at most 2 years; longer ranges are cut to 2 years from the start date.
Current week / Current month
Jumps to the common time ranges; Current month also takes you from the daily view back to the grid.
Jump to month
Appears as soon as the range spans several months: a click scrolls to the first day of the selected month without changing the range. Not in "At a glance" and not in the project period.
Daily view
Hour-based detail view — limited to a maximum of 31 days.
At a glance
Compact list display of the events.
Project period
Couples the calendar to a project: search for a project or artist, and exactly its period is shown.
Zoom
Dropdown with the levels 40–140 % and the entry Month view (40%); alternatively Ctrl/Cmd + mouse wheel over the calendar. Below 80 %, compact mode applies — see Views & Display Settings.
Multi-edit
Select several events and edit them in bulk — see below.
If the browser window is narrower than 1536 pixels, only the filter, the
display settings and Add Event stay directly visible. Zoom, fullscreen, Subscribe to calendar and
Export calendar then sit in the More options menu.
If events in the selected period lack a room, a yellow button with a
warning triangle and the number of these events appears in the function
bar. Clicking it opens the list Events without room, from which the
events can be scheduled after the fact. In the calendar tab of a project, a
red notice above the calendar appears instead ("n event(s) without
room!").
Grid, month view (zoom 40 %), daily view, "At a glance" and project period
show the same calendar with a different focus. A comparison of the views,
the effect of each zoom level and recommended settings for typical tasks
are described under
Views & Display Settings.
In short: zoom, expanded days and fullscreen affect presentation only;
filters and project mode determine which data is included — which matters
especially before an export.
The month view is the smallest zoom level (Month view (40%) in the
zoom dropdown). With Expand days switched off, a whole month fits on the
screen; the tiles appear in compact mode. Details under
Zoom, compact mode and room column width.
Narrow room columns (for instance with a small room column width) still
show the full tile content and the three-dot menu in the grid at 80 % zoom
and above; the text simply wraps more. Only in the
daily view do narrow tiles shrink to name, time and an info
icon with a tooltip. Truncated descriptions show the full text on hover.
The filter panel (the Calendar Filter window) narrows the grid down to
what you are working on right now. At the top, the Active filters
appear as removable tags; below are the collapsible categories with the
number of selected entries. Apply takes over the selection, Reset
clears all check marks. A dot on the funnel shows that a filter is active.
The calendar offers four groups:
Group
Categories
Room Filters
Room Categories, Room Attributes, Rooms
Area Filters
Areas
Event Filters
Event Types, Event Properties
Project Status Filters
Project Status
The room list only contains rooms marked as Relevant for disposition;
other rooms do not appear in the calendar anyway. To avoid placing a quiet
rehearsal next to a loud event, for example, filter by the matching event
property (e.g. Laut, the property for loud events) and see where such events are.
Project status shows only events of projects with one of the selected
statuses; events without a project are hidden. The filter applies to the
calendar, the planning calendar, the daily views and the project's event
list, and can be stored in saved filters.
A filter by crafts and the Shift filters section (Only show shifts
that are not fully staffed) only exist in the
duty roster, not in the calendar.
Shifts shown in the calendar (Show shifts) can therefore not be
filtered by staffing here.
To find free rooms, use the display setting: switch Hide unoccupied
rooms off, and unoccupied rooms stay visible in the grid. If a filter or
Hide unoccupied rooms hides all rooms, the calendar shows a notice
with the cause instead of an empty area.
Save filter stores the current combination as a saved filter that
you can apply later with one click. The currently active saved filter is
highlighted in green with a check mark; the Deselect filter icon
switches it off without deleting it, while the X deletes the saved
filter. A saved filter remembers the combination for your personal
workflow; it never changes events. The same behaviour applies in the duty
roster (week, day, list) and in the project's event list.
The gear opens your personal display options; they persist across
sessions and show only settings that take effect in the current view. The
options are sorted into four groups:
Navigation — Share time period across views
Appearance & Accessibility — contrast, expand days, colour source of
the tiles (event type, status or main category), room column width, day
remarks
Every option with its effect, the views it applies in and a usage
recommendation is described in
Views & Display Settings.
The calendar and the planning calendar each have their own display
settings, and so do the daily views; details under
What is saved where?.
Show shifts requires duty roster access
Show shifts (calendar and daily view) is only available to people with
the permission View duty rosters or Plan shifts. Without one of them
the option is missing and shifts do not appear in the calendar.
Day rows additionally show public and school holidays (managed in the
event settings).
Weekends inside a holiday period are recognisable by a darker shade of the
holiday colour. If several entries fall on one day, an entry you created
yourself defines the day colour before an imported one, and a single-day
entry before a multi-day one (vacations). If another entry of that day has
a different colour, it is laid on top as hatching.
If the day remarks column is activated in the
calendar settings, the calendar (and likewise
the planning calendar) shows a dedicated column next to the date column for
notes covering the whole day, for instance hints for all crafts or
organisational specifics. There is one shared remark per day: it
applies to all rooms and appears with the same content in the calendar,
the planning calendar and the
duty roster. Whether you can hide the
column via the display setting Day remarks depends on whether your
administration has set it as mandatory. If a remark does not fit
into its cell, a tooltip shows the full text on hover — in the calendar,
the daily view and the duty roster. The permissions View day remarks and
Edit day remarks control who may see and who may edit the column.
With Edit day remarks you click into the cell of the day, write up to
500 characters and save. An empty text deletes the remark. The change
appears for everyone else immediately.
The daily view shows up to 31 days as an hourly grid per room — ideal
for show days. Which hours it hides on quiet days (e.g. 00:00–08:00) is
defined by the
calendar settings system
setting.
On days without a timed event in this range the hours are missing, and a
note appears above the day. As soon as an event falls into the range on a
day, that day shows all 24 hours. Multi-day and all-day events remain
visible. The tiles show
their full content at every zoom level; if parallel events make them
narrow, name, time and an info icon with a tooltip remain. On very short
tiles, the status (Planned Event, Verification requested) appears only
as a colour stripe at the edge, with the text in the tooltip. For long
periods, switch back to the grid, as the daily view is limited to 31 days.
The multi-edit switch lets you select several events and cells and handle
them in bulk:
Duplicate or delete events (to the trash; sub-events are deleted
along with them)
Duplicate one event into selected cells — select the event, then
click the day/room cells it should be copied into
Create events in several cells at once — first select several
day/room cells, then create an event; this creates independent
individual events, not one collective event. If you may only request the
selected rooms, the button reads Request event in n cells: the
events are created as room requests and the room administration is
notified. The same applies to copies into rooms you may only request;
the request then runs under your name. If you may neither create nor
request events in one of the selected rooms, a notice appears instead of
the button. In rooms with Can be booked by anyone you book directly,
provided you may create events; the switch alone is not enough
Coming with the next update
Move selected events into one cell — when exactly one cell and at
least one event are selected, the events move together into that day
and room cell. Times and duration are kept; multi-day events and their
shifts move along accordingly
Accept / decline requests (for room admins, as long as room booking
requests are in use)
Convert to planned events: turns the selected fixed events into
planned events in the
planning calendar; open room
requests are withdrawn in the process. Only with the permission Edit
planned events
Only in the planning calendar: Request verification, Approve and
Reject (in the
verification workflow).
Moving, duplicating and deleting require Edit planned events there
If you are not allowed to edit one of the selected events, the bulk action
changes, deletes or copies nothing at all instead of stopping halfway.
Activate multi-edit mode first, then select the events or cells. The
available bulk actions depend on the status and permissions of the
selection. Before confirming, check in particular whether series, room
requests or planned events are included — their follow-up actions can
differ from those of regular individual events.
Deleted events move to the trash for 30 days and
can be restored from there.
When deleting a series event, Artwork asks whether only this event,
this and following or the whole series should go to the trash — see
Editing series. Series
events always go to the trash first; there, Restore series brings back
all events of a series at once. After the 30 days they are removed
permanently like other events. The trash protects against accidental
deletion but is not a long-term archive.
Calendar
Views & Display Settings
Which calendar view suits which task, what each display option does and in which view it applies, plus recommended settings for typical tasks
You can adapt the calendar to your way of working in many respects. Almost
all of it sits in two places of the function bar: the zoom and the
gear (display settings). This page explains every option, says in
which view it applies and suggests settings for typical tasks. How to use
the calendar in general is described in
The Calendar View.
Display settings are personal
Everything on this page applies only to you and stays saved across
sessions. Other users see the calendar with their own settings. What
display settings do not do: they change no events and do not
restrict what others see.
Comparing several days and rooms, spotting free space, moving events by drag & drop.
Month view
Zoom dropdown → Month view (40%)
Reviewing a whole month at a glance; tiles appear in compact mode.
Daily view
Switch Switch between weekly and daily view
Time overlaps within a day, the schedule on a show day; a maximum of 31 days.
At a glance
Switch At a glance
Comparing room utilisation over the period: one column per room, all events listed below each other, without day rows.
Project period
Switch Project search, then choose a project or artist
Working only on the events of one production in its automatically calculated period; other events stay visible for orientation.
Planning calendar
Menu Calendar → Planning calendar
Planning provisionally without colleagues seeing the drafts in the calendar — see Planning Calendar.
Zoom, fullscreen, daily view and "At a glance" only change the
presentation. Filters and project period, on the other hand, change
which content is shown — this matters before an export, because
exports adopt the active filters.
The percentage dropdown in the function bar offers the levels 40 %,
60 %, 80 %, 100 % (default), 120 % and 140 %. The first entry, Month
view (40%), also jumps to the start of the month of the currently visible
range. Alternatively, zoom with Ctrl (Windows) or Cmd (Mac) +
mouse wheel over the calendar.
Important to understand: the zoom only controls the row height, i.e.
how many days fit on the screen. The width of the room columns stays the
same at every level; you set it separately via Room column width in the
display settings (Narrow 160 px, Standard 212 px, Wide 280 px, Very
wide 320 px).
Below 80 %, the calendar switches to compact mode, recognisable by
the Compact chip in the function bar:
Every tile becomes one line with time and title. The title names the
event name and the project name, separated by "·", preceded by the event
type abbreviation (for example SET: Stage setup · Summer festival). If
the event has neither a name nor a project, the event type is written
out. An event name that merely repeats the event type is dropped.
A click on the tile opens the event directly; the three-dot menu is not
available in compact mode.
Hovering shows a tooltip with all details.
The options under Event Content (see below) only affect the large
tiles from 80 % upwards.
In the daily view, the zoom instead determines the height of the hours and
the width of the room columns; "Room column width" does not exist there.
The gear opens the Calendar Settings window. It shows only options that
actually take effect in the view that is currently open; that is why the
daily view has fewer checkboxes than the grid, and the planning calendar an
additional section. Changes apply after Save. A dot on the gear
indicates that at least one option is switched on (options that are on by
default and "Share time period across views" do not count).
Calendar, planning calendar, duty roster, duty roster list view and article planning always show the same period. When you switch it on, all views adopt the period of the view you are currently in. When it is off, each view remembers its own period.
all
When you switch back and forth between calendar and duty roster and do not want to navigate anew every time. Switch it off if, for example, you look at next week in the duty roster and at the season in the calendar.
Stronger colours for grid lines, weekends, holidays and tiles. Text on coloured areas switches to white only on really dark shades.
C, CD, P, PD
With light event colours, on a projector or for visual impairments.
Expand days
Day rows grow until all events are visible. Off: fixed row height, each cell scrolls on its own. In the daily views the hour height stays fixed; long texts on the tile wrap there instead of being cut off.
C, CD, P, PD
For rooms with many events per day. Switch it off for the month view, otherwise the month does not fit on the screen.
Artist names instead of event title
In compact mode (below 80 %), the tile shows the project's artists instead of the event title. If the project has no artists, the event title stays.
C, P
For guest-performance venues and festivals where the artists say more than the event title.
Day remarks
Shows the day remarks column next to the date column. Only appears if the column is enabled in the calendar settings and you have View day remarks. If your administration has made the column mandatory, the checkbox is locked and always on. Default: on.
C, P
Switch it off if you need space and the notes play no role in your work.
Use event status colour
Colours tiles by event status instead of event type; events without a status keep the colour of the event type. Only with the event status module active. Excludes "by main category".
C, CD, P, PD
When the confirmation state (requested, confirmed, cancelled) matters more than the kind of event.
Event colour by main category
Colours tiles by the project's main category. Events without a main category appear anthracite, events without a project grey. Excludes "by status".
C, CD, P, PD
For venues that work in divisions (drama, music, rentals) and want to read the calendar that way.
Room column width
Width of each room column, independent of the zoom (see above). Default: 212 px.
C, P
Narrow for many rooms side by side; Wide or Very wide when tiles carry a lot of content (description, artists).
Where does a tile's colour come from?
If neither colour option is active, every tile carries the colour of its
event type. The two colour options cannot be active at the same
time: switching one on switches the other off. The same logic controls
the colours in the exports.
Rooms without events in the visible period disappear from the grid. What counts is what the room actually shows with your filters and display settings: with Show shifts on, shift cards keep a room visible as well. In the planning calendar planned events count, fixed ones only with Show fixed events. If no room is left, a notice names the cause.
C, CD, P, PD
With many rooms of which only a few are in use; for printouts and presentations. Switch it off when you are looking for free rooms.
Show planned events
Shows provisional entries from the planning calendar in the normal calendar. Only with View planning calendar or Edit planned events.
C, CD
For schedulers who want to check fixed and planned occupancy together without opening the planning calendar.
Repeat event
Marks events that belong to a series with a repeat icon.
C, CD, P, PD
Whenever you want to know while editing whether a change affects a series.
Show project group
Shows the project group (e.g. the festival) on the tile.
C, CD, P, PD
For project groups with many individual projects.
Show shifts
Stand-alone shifts appear as separate cards in the room/day cell, mixed with the events and sorted by start time. Only with the permission View duty rosters or Plan shifts.
C, CD, P, PD
For technical and craft managers who want to see in the calendar where staff are scheduled. Filtering by staffing is only possible in the duty roster.
Timeline
Shows an icon on tiles through which you open and extend the event's timeline.
C, CD, P, PD
For venues that maintain daily schedules (admission, start, interval, end) in artwork.
These options determine what appears on the large tiles (from 80 %
zoom). The more you switch on, the taller the tiles become; with Expand
days everything still stays readable.
Option
Effect
Applies in
When useful
Event name
The name of the event. Default: on. If there is no name, the tile shows the project or event type.
C, CD, P, PD
Switch it off only if your events have no names of their own and project name plus event type are enough.
Description
The description text of the event. Truncated texts show the full wording on hover.
C, CD, P, PD
For show days and for venues that keep notes directly on the event.
Project Status
The status of the associated project (for instance in planning, confirmed).
C, CD, P, PD
When the calendar also shows projects that are not yet certain to take place.
Project managers
The project managers of the project.
C, CD, P, PD
For queries from technical and administrative staff.
Event creator
The profile picture of the person who created the event.
C, CD, P, PD
In venues where many people create events.
Admission
The admission time on the tile. Only if the admission field is enabled. Default: on.
C, CD, P, PD
For admission, box office and evening duty.
Event status spelled out
The event status as its own row with a colour dot below the name. Only with the event status module active.
C, CD, P, PD
When you want to read the status without switching the tile colour to it.
The settings are saved per user. Some apply per view, others to several
views together:
Setting
Shared by
All checkboxes of the gear and the room column width
Each of the four views on its own: calendar, calendar daily view, planning calendar, planning calendar daily view. Only Share time period across views applies everywhere.
Zoom, "At a glance", weekly/daily view switch
Calendar and planning calendar together; independent of the duty roster.
Period and filters (including saved filters)
Each of the four views on its own: calendar, calendar daily view, planning calendar, planning calendar daily view. With Share time period across views, one shared period applies.
Project period (project search)
Grid views together, daily views together.
So if you set Hide unoccupied rooms in the planning calendar, this
does not change the normal calendar. Since version 1.9.0 the calendar and
the planning calendar have separate display settings; on the update, the
planning calendar started with a copy of the previous calendar settings.
Both sit next to each other in the function bar, but they do different
things:
A filter decides which rooms and events are loaded. It also
affects exports and can be stored as a saved filter.
A display setting decides how the loaded content looks. It does
not affect other people and is adopted in exports only as a preset that
you can change there.
If you cannot find an event, first check the active filters (tags in the
filter panel, dot on the funnel), then Hide unoccupied rooms and the
period.
Calendar
Creating Events
The event form — type, times, repetition, room, project, sub-events and editing series
Hover over a room/day cell and a plus icon ("Add event") appears — it
opens the event form with the day and room prefilled. The plus button
Add Event on the right of the function bar opens the same form without
a preselected room. Clicking an existing event opens it for editing.
Which fields and actions you see depends on the event type, room rights and
your permissions. Without edit rights, a clear read-only view opens with
type, status, time, room, project, description and properties. This lets
many people look up events reliably without changing them by accident.
Event type — the category of the event; determines its color and
abbreviation in the calendar. Depending on the
type configuration, a project
assignment and an individual event name may be mandatory.
Event status — only visible when the status module is active; the
default status is preselected.
Event name — optional (or mandatory if the event type requires it).
All-day or with a start/end time; the event duration shortcuts
(30/60/90 min) set the end to a standard duration after the start. If your
default event duration differs from these, it appears as a fourth button
(Default: n min). The shortcuts only work once date and start time
are set, and not for all-day events. The switch to the right of the section
heading is called Move the end date along when the start date is
changed: when it is active, the event keeps its length if you change the start day. The
presets (default event duration, default start time, "full day as default")
come from the standard values.
If the Admission field is enabled in the standard values, an optional
admission time can be entered as well — a calendar display option shows it
in the event cards above the time. The admission time always refers to the
start day.
Start and end may be on different days. This also covers multi-day guest
performances, overnight setups or long blocking periods correctly. If start
and end time are identical or the end is arithmetically before the start,
check the end date in particular — in the project's event list, Artwork may
turn this into an event lasting until the following day.
In the Repeat section, the Repeat event toggle turns the event into
a series:
Frequency — Daily, Weekly, Every 2 weeks or Monthly.
On these weekdays — with Weekly and Every 2 weeks you can pick
several weekdays (for example Mon and Wed). The weekday of the first
event is always included.
Series ends — either Ends on date with an end date or Ends
after with a Number of events. A series is limited to 500 events.
Below the form, the Preview of the series shows live which events will
be created — with date, time and room. Room conflicts are counted ("n
potential conflicts detected"), so you can adjust frequency or room before
saving. How to change an existing series is described under
Editing series.
Room — the room search shows potential conflicts with existing
occupancies live. Whether you can book directly or submit a
booking request depends on your
rights for the room — unless your organisation has enabled
Events always bookable directly,
in which case everyone books directly.
Project: The checkbox Enable project assignment shows the
project selection. Under Existing project you search for a project
or pick one of the recently opened ones; under New project you create
one on the spot. Events whose type is relevant for the project period
contribute to the project's automatically calculated period. If the
project belongs to a project group, the group is shown next to the
project name.
With an existing project you can switch straight to the project view from
the form, provided you have access. If you choose New project, it is
saved together with the event. For detailed master data, team rights and
further project content, open the new project afterwards in the project
overview.
If the New project choice is missing, your administration has switched
off project creation from events in the
calendar settings.
Events can then only be linked to existing projects.
A free-text description ("What do I need to bear in mind for the event?") is
visible in the calendar and in the project's event list. Below it, tick the
applicable event properties (e.g. Publikum for events with an audience, Laut for loud events). They
appear as icons on the event and can be filtered.
Save creates the event — or Request occupancy ("Belegung
anfragen") if you may only request the room. After a request, the notice
Room request submitted confirms that the event is not firmly booked
yet. If you have neither a calendar permission nor a role in the selected
room, a notice appears instead of the button Coming with the next update; see
Understanding booking access.
Afterwards you can
plan shifts on the event or create a
timeline.
Room admins can treat a requested occupancy as a firm acceptance or as an
optional acceptance (Commitments or Optional commitment) and
add an option (Option 1 to Option 4) and a comment. The requesting
person is informed about the decision. What the optional commitment does
and where the note is visible is described under
Handling room booking requests. If Events always bookable
directly is active, there is no request mode; the button is always
Save.
An event can contain sub-events — e.g. the soundcheck from 16:00–17:00
inside an all-day blocker. Sub-events have their own type, their own times
(at least 30 minutes), their own properties and description. They appear
in the event card below the main event. The times are pre-filled with
those of the main event. Artwork does not check whether a sub-event lies
within the main event; make sure of that yourself. A deleted sub-event is
removed permanently right away and does not go to the trash.
You create a sub-event via the three-dot menu of the event tile with Add
Sub-Event. The entry only appears on events of the standard event type
(the first event type in the list, which cannot be deleted) and only for
room admins, the person who created the event, and admins. In compact mode
(zoom below 80 %) the menu is not available.
Sub-events suit clearly delimited sections that should be visible and
filterable within the main event. They do not replace a separate main event
when another room, a separate project or an approval process of its own is
needed.
For show days you can maintain a timeline on the event — the production
schedule (get-in, soundcheck, doors, show …) with times. Timeline
presets from the event settings can be imported; the Timeline display
option shows timelines in the calendar. The timeline may be created and
edited by anyone who may edit the event (write access to the project,
Plan events directly, room admin or the person who created the event) or
who has the permission Plan shifts. If the permission is missing, the
dialog tells you when saving.
In the three-dot menu of the event tile, Import timeline preset brings
a preset into the event. Save timeline as preset appears as soon as
the event has a timeline and requires Plan events directly.
A timeline is a scheduling aid within the event and does not need to consist
of independent calendar bookings. It is therefore ideal for internal
production steps. Recurring sequences can be saved as a preset and imported
into other events.
The description of a timeline entry appears next to the time in the
event's schedule (shifts tab of the project) and in the daily view of the
duty roster — visible to everyone who can see the schedule. A hint in the
edit modal and in the inline card of the shifts tab reminds you of this.
Events can be dragged into other cells in the grid via drag & drop.
Multi-edit duplicates, moves
or deletes many events at once. For projects there is additionally the
tabular bulk event creation in the
project's event list.
If people are assigned to the project for specific days and those days fall
outside the project period because of the move, the dialog Dissolve
project assignments? asks on saving. It only appears when the event's
period actually changes.
When you open an event that belongs to a series, frequency, weekdays and end
of the series are prefilled in the Repeat section. At the top of the
event dialog you choose what your change applies to:
Choice
Effect
Only this event
Changes apply only to this event. Changing date, time or room makes it a deviating event of the series. Frequency and end of the series cannot be changed with this choice.
This and following
Changes apply to this and all following events of the series.
Whole series
Changes apply to all events of the series, including past ones.
With This and following and Whole series, fields such as name,
description, event type, status, room, project and properties are applied
one to one. Changed times are applied as a shift: if you move the event one
hour later, all affected events move by one hour. Deviating events receive
the field changes too, but keep their individually set time.
Next to the choice, the event dialog has the Series tab with the list
Events of this series: date, time and room per event, plus the markers
Deviating, In the trash and Shifts (count) as well as a note
on room conflicts. Past events are greyed out. The open event is
highlighted as This event; Show in calendar jumps to the week of
the respective event and resets your calendar filters in the process. When
creating a new series, the same tab shows the preview.
Extending the end date appends events at the end of the series;
shortening removes only the events after the new end (to the trash).
Changing the frequency or weekdays re-creates the future events from
the edited event on. The dialog Change series? tells you beforehand
how many events and shifts are affected.
Individually moved (deviating) events are kept when the series changes;
events in the trash count as occupied. No date is created twice.
Delete offers the same three-way choice ("This event is part of a
series. Which events should be put in the trash?"): Only this event,
This and following or Whole series — with the number of affected
events. Nothing is deleted permanently: all events go to the
trash, where Restore series brings back all
events of a series together. From the tile or from multi-edit, Delete all
series events is also available.
If you switch off the Repeat event toggle on a series event, Remove
from series? asks:
Detach only this event — the event becomes a single event; the other
events of the series stay as they are.
End the series — all other events of the series are put in the trash;
this event becomes a single event.
Exception or series?
Change only one event when it is a genuine exception. For a new standard
time, a different room or a changed description of the whole run, use
This and following or Whole series so that you do not end up with
many deviating individual states.
The project's event list is faster
than the single form for productions with many events. There you can add
rows, adjust column widths, show or hide descriptions and change several
events together. The regular calendar remains the better view when you
need to assess room conflicts in the context of other projects.
Calendar
Rooms, areas & booking access
Organise rooms, model availability, and control booking requests
Rooms are more than names in a selector. Their properties, capacities,
validity periods, and access rules determine where events can be planned and
whether a booking is immediately confirmed or requires approval. Manage them
under System → Rooms. The page is titled Rooms & areas; the calendar
filter and the calendar subscription list the same entries under Areas.
Areas organise rooms by building, location, or operational unit. Every
room belongs to exactly one area, which places it in the corresponding room
and calendar views. Use short, unambiguous names; make the location visible
where similar names exist.
In the Areas section, click Add area, enter the Name of the
area in the New area window and confirm with Create. You choose
the colour of the area afterwards via its three-dot menu under Edit.
Expand the area and click Add room. The room is created in this
area; the New room window has no separate field for it, and neither
has the Edit room dialog.
The Room name is mandatory, for a temporary room also the end
date. The other fields are described in
the table under Room information. Create adds
the room.
You set the colour of a room only after creating it, under Edit room.
Room admins and people authorised to request are entered on the room detail
page, see Understanding booking access.
Categories answer “what kind of room is this?”, while properties answer “what
does this room offer or permit?”. A room can carry several categories and
several properties; both can be filtered in the calendar (Room
Categories, Room Attributes). Consistent labels make filters useful.
Adjacent-room links (labelled Adjoining rooms in the interface) record
which rooms can affect each other, for example through noise, audiences,
setup, or shared access. The assignment is shown on the room detail page
and in the room's history.
For the calendar it is information only: an event in an adjoining room
does not block a room, does not appear as a conflict in the event form and
cannot be filtered separately. The help text in the room dialog says the
same Coming with the next update: Adjoining rooms record which rooms are next
to each other. There is no notification about loud events in an
adjoining room; the notification type Side events no longer appears in
the notification settingsComing with the next update. So check parallel occupancies yourself in the grid, for example with the filter for the event
property Laut (loud).
The room capacity is its standard value and supports project occupancy
reporting. If one production uses a different seating plan, enter a
project-specific capacity in
Business intelligence
without changing the room for other projects.
Can edit the room and approve or reject booking requests
Authorized to request
Can request a booking for this room
Can be booked by anyone
Whoever may create events (calendar permission or role in the room) books directly instead of requesting
The help text at the switch says Coming with the next update: Decides whether
everyone who may create events books this room directly or only the room
admins. If it is off, the others can only request the room.
Under Access to room, whole teams can be entered as room admins or as
authorized to request in addition to individual people; all members then
receive the rights and the notifications. If a room has no room admins, the
person who created the room decides on requests.
A person can be a room administrator, requester, or both. If the room is not
generally bookable, the event remains a request until a room administrator
decides it.
No effect with ‘Events always bookable directly’
If the switch Events always bookable directly is active in the
event settings,
everyone who may create events books every room directly in the normal
calendar. Can be booked by anyone and Authorized to request have
no effect there. The room page shows a notice; the fields stay editable
and apply again as soon as the switch is off. Room admins may still
edit and delete other people's events in their room; only answering
requests is dropped.
In the planning calendar,
Can be booked by anyone keeps its effect: in such rooms everyone who
may create events creates planned events. In all other rooms this needs
Plan directly in the planning calendar or the room admin role.
Calendar and room permissions work together
Room admins and users authorized to request create events in their room
even without the calendar permission Request room occupancy: via the
plus in the room cell. Can be booked by anyone alone is not enough,
however. Someone with neither a calendar permission nor a right on the
room sees a notice instead of Save in the form Coming with the next update:
To create events you need a calendar permission or a role as room admin
or requester in this room. The bulk actions in the calendar then create
nothing either, neither directly nor as a request.
Likewise, calendar access does not automatically permit confirmed
booking of every protected room.
Temporary rooms suit guest venues, outdoor areas, and rented locations. Set
the first and last available date. Artwork checks that an event—including an
overnight or multi-day event—fits fully within this period.
The room detail combines description, area, categories, properties, adjacent
rooms, validity, and access. View history lists who changed the name,
description, categories, properties, adjoining rooms, room admins or the
validity period, and when.
Description, Access to room, Room properties and Documents
sit directly on the page and are edited via the pencil icon. The pencils
are only visible to people with Room administration, admins and the room
admins of the room.
Duplicate (copy icon on the room card, three-dot menu, or room detail
page) creates "(Copy) room name" in the same area and takes over the master
data: colour, description, validity period, capacity, and the switches for
direct booking and scheduling relevance. Categories, properties, adjacent
rooms, room administrators, files, and events are not copied – you maintain
them anew on the copy. An area can also be duplicated via its menu, then
including all its rooms.
Deleted rooms first move to the trash and can be restored. If you delete
an area, all its rooms move to the trash with it. Only delete
permanently after checking how existing events and reports refer to the
room.
The Sort rooms tab under System → Rooms lists all rooms regardless
of their area. Drag them into the desired order; every change is saved
immediately. This order applies to all users and determines the room
columns or rows in the calendar, planning calendar and duty roster as well
as in the exports.
Is Relevant for disposition switched on for the room, and does no filter hide it?
For a temporary room, does the complete event fit its validity period?
Does the user have a calendar permission (Request room occupancy or
Plan events directly), or are they entered on the room as room admin
or authorized to request?
Is Events always bookable directly active? Then the room's request
settings do not apply, and everyone with a create permission books
directly.
May they request this room, or is it directly bookable?
Is room-administrator approval still pending?
Does the event overlap an existing booking?
Is something scheduled in parallel in an adjoining room? Artwork does not check this automatically.
Assign room administrators before opening a protected room for requests.
Update capacities and properties after alterations.
Review validity periods for temporary rooms.
Move unused rooms to the trash before permanent deletion.
After changing access, test the intended direct-booking or request workflow
with a requester account.
Calendar
Event Verifications
Room booking requests and the verification workflow for events
Not everyone may simply occupy every room, and planned events should,
depending on their event type, be reviewed before they become fixed. Both
cases come together under
Calendar → Event verifications: the inbox for incoming requests and
the overview Requests sent by me.
Not used with ‘Events always bookable directly’
If the switch Events always bookable directly is active in the
standard values, there
are neither room booking requests nor event verification: everyone who may
create events books directly, the menu entry Event Verifications
disappears, and open requests are accepted when the switch is turned on.
Everything else on this page applies only while the switch is off.
Both kinds of request look similar but answer different questions: for a
room booking, the person responsible for the room decides. For an event
verification, the reviewers assigned to the event type decide about its
content. Room booking requests only exist for fixed events in the regular
calendar, verification only for planned events from the
planning calendar. An event
therefore never goes through both: a verified planned event is firmly
booked right away.
Whether an event takes effect immediately or has to be requested is decided
per room:
Rooms with "Can be booked by anyone" are open to everyone who may
create events (calendar permission or a right on the room).
Otherwise, only the room's room admins book directly — as well as
users with the global permission Plan events directly (Termine fest
planen) and admins.
Everyone else with Request room occupancy (or the per-room setting
Authorized to request) submits a room booking request: the save
button of the event form becomes "Request occupancy" ("Belegung
anfragen"), and the event appears hatched as requested in the calendar.
Room admins and users authorized to request are maintained per room under
Access to room (room management); whole teams can be entered there as
well, and all their members then receive the rights and notifications. If
a room has no room admins, the person who created the room decides on
requests. They receive the request as a notification and answer it there;
the Event Verifications page does not list these requests for them.
Plan events directly applies to the calendar only; in the
planning calendar there
are no room requests, and creating events there needs the separate
permission Plan directly in the planning calendar.
Under Event Verifications, room admins see the open requests for their
rooms (admins and users with Plan events directly see all), grouped by
room. For each request:
Accept: after a confirmation prompt the occupancy becomes firm.
Decline: the event loses its room but continues to exist. It
remembers the declined room and is then listed in the calendar under
Events without room.
Show in calendar jumps to the week of the event and resets your
calendar filters in the process.
The notification about the request offers the same actions. In the
calendar, room admins and admins find Accept room request in the
three-dot menu of the tile; Decline event declines and asks for a
reason, which is sent to the requesting person as a notification.
The event dialog offers more. Open the request in the calendar or choose
Edit and accept (pencil icon) in the notification. The dialog is then
titled Change & confirm occupancy:
Commitments books the occupancy firmly.
Optional commitment also books it firmly and adds a note Option 1
to Option 4 to the event.
Accepting in a different room: choose another room in the dialog and
tick Commitments. The event does not remember the originally
requested room in this case; that only happens when declining.
A comment on the booking is sent to the requesting person as a
notification. Without an acceptance the button reads Send message,
and the request stays open. The requesting person can write back via
Answers in the notification.
An optional commitment suits cases where the room is reserved but the
event itself is not yet final. For the room occupancy it makes no
difference to a regular acceptance. The note is stored on the event; in
this version, however, the display settings have no switch that shows it
on the tile. Therefore also record an option via the
event status or the
description. Comments are not shown on the event, only in the
notifications.
Several requests can be accepted or declined at once via
multi-edit.
Independently of rooms, every event type
can have a verification mode. It applies to planned events of that
type and controls who has to confirm them before they become fixed events.
Events created directly in the regular calendar do not go through
verification.
Mode
Meaning
No verification needed
Planned events are confirmed without a review (default)
All assigned users must verify
Every named reviewer must approve
At least one assigned user must verify
One approval is enough
A specific user must verify
Exactly the named person decides
Planned events are submitted for verification: individually via the
three-dot menu of the tile in the planning calendar, in bulk via
multi-edit, or via Requests sent by me. Whoever created the event or
has Edit planned events may request. The reviewers are notified and find
the requests under Event Verifications → Incoming requests in the
section Verification requests for planned events, grouped by event
type. There they approve or reject; Open in Calendar leads to
the week of the event in the planning calendar. When rejecting, a
Rejection Reason can be entered, which goes back to the requesting
person. Until the decision, the tile carries the note Verification
requested; a still-open request can be withdrawn.
What happens after the decision:
Approved and rule fulfilled: the planned event becomes a fixed,
firmly booked event. In the mode at least one, the remaining open
requests are thereby settled.
Rejected: the event stays planned and can be sent for verification
again after a correction. In the mode all, one rejection ends the
round; the remaining reviewers no longer have to answer.
If you are a reviewer yourself in the mode all, your approval counts
as given when you submit. If you are the only reviewer assigned, the
event is confirmed immediately Coming with the next update. If you are the specific person or one of the
reviewers in the mode at least one, the event is confirmed immediately
on submitting; the action is then called Approve.
Admins can approve any planned event directly, even without a
request and even if other reviewers have not yet approved.
If no reviewers are assigned to the event type, nothing is sent and a
message says so.
For the modes all must confirm and at least one person must
confirm, the status under Requests sent by me shows which responses
are still missing.
The second section shows what is still awaiting a decision:
My room booking requests lists your open room requests with the
status Pending. An accepted or declined request disappears from the
list; you learn the outcome from the notification. After a decline,
Change request there takes you to the event so you can move it to
another room, and Delete event removes it. The event is also listed
in the calendar under "Events without room"; the event dialog notes the
declined room.
My Verification Requests shows the reviewers for each planned event,
sorted into Approved, Rejected and Pending. You read the rejection
reason by hovering over the person who rejected.
The Planned Events card lists your planned events without an open
request; Request Verification submits them from here.
When you select a room in the event form, Artwork shows potential
conflicts with existing events live. Accepting despite a conflict is
possible; the responsibility lies with the room admins. You find
alternative rooms in the grid when the display setting Hide unoccupied
rooms is off and you narrow the filter down to matching room categories
or room attributes.
A conflict warning is not an automatic rejection. It draws attention to
overlapping occupancies so that room admin and requesting person can decide
deliberately. Only the selected room is checked: events in
adjoining rooms do
not count as a conflict. Before accepting, you should therefore look at
sub-events, multi-day occupancies and adjoining rooms in the grid
yourself.
New requests and decisions appear in your personal notifications. Comments
and rejection reasons help you make the next change right away. Under
Requests sent by me, the state of your verification requests remains
available even after the notification has been read. Answered room
requests are no longer listed there; you find read notifications in the
notification archive.
Calendar
Planning Calendar
Plan provisionally without occupying the real calendar
The planning calendar (Calendar → Planning calendar) is a separate
space for provisional planning — for instance the season planning for next
year. It looks like the normal calendar, but:
Events here are planned events: they do not occupy rooms bindingly
and are invisible to regular users until they are adopted as fixed
events.
A red warning "Attention! You are in the planning calendar" in the
function bar prevents mix-ups.
The planning calendar has its own filters and display options —
saved filters and display settings of the normal calendar remain
untouched. The Project
status filter applies here as well. The option Show fixed events
shows the real occupancies for orientation.
Multi-edit can do the same as in the normal calendar: duplicate
events into selected cells, create (individual) events in several cells
at once, and move selected events into one cell — see
Multi-edit. Moving,
duplicating and deleting require Edit planned events here.
Planned events are never room requests: they are always created as
firmly planned and appear neither in the
calendar subscription
nor for people without a planning calendar permission, not even in the
duty roster.
Typical uses include season drafts, unconfirmed guest performances and
alternative room plans. Entries can already contain project, properties,
description and times without filling the binding calendar for all users.
Plan. Anyone with Plan directly in the planning calendar creates
planned events here, with the same handling as in the
event form. Room admins can do so in
their own rooms without this permission, and in rooms with Can be booked
by anyone so can everyone who may create events. View planning
calendar alone only allows viewing, and the calendar permission Plan
events directly is not sufficient: the form then shows the notice "You
lack the permission 'Plan directly in the planning calendar' to create
planned events in this room."
Request verification. Whoever created the planned event or has Edit
planned events sends it for verification with Request verification:
individually in the three-dot menu of the tile, in bulk via multi-edit, or
under Event Verifications → Requests sent by me. Who has to verify is
defined by the
verification mode of the event type.
If the event type needs no verification or your own approval would be
enough (you are the designated verifier or one of the verifiers in the
mode at least one), the action is called Approve and confirms the
event immediately.
Become visible. As soon as the verifiers have approved, the event
becomes a normal, firmly booked calendar entry; no additional room booking
request is created. After a rejection it stays planned and can be sent
for verification again. You take back an open request with Withdraw
verification request. Conversely, Convert to planned event (three-dot
menu, with Edit planned events) turns a fixed event back into a planned
one; an open room request is withdrawn in the process.
Before adopting, check whether room, event type, project and times still
match the current planning state, because the confirmed event occupies the
room bindingly right away. Admins can approve planned events directly at
any time, even without a requested verification. If no verifiers are
assigned to the event type, the request is not sent and a message says so.
No review step with ‘Events always bookable directly’
If Events always bookable directly is active in the
standard values,
there is no verification: instead, Confirm as fixed event (tile) or
Confirm as fixed events (multi-edit) turns planned events into fixed
events immediately. "Approve" and "Reject" no longer appear. Creating
planned events still requires Plan directly in the planning calendar.
A project status can be marked centrally as a planning status (the
switch Project counts as "in planning" on the project status). The
mark does not turn the events of a project into planned events by itself.
It only presets the switch for planned events in the event entry of the
project (schedule and Set up
events during creation): new rows are created there as planned events as
long as you do not change the switch. Events you create in the calendar do
not follow the project status, and existing events stay as they are.
If a project changes to such a status, the dialog Project status change
asks whether all events of the project should become planned events
(Convert to planning events). If the project changes to a status
without this mark, the dialog Project
status change asks whether verification should be requested for all
planned events of the project (Request event verification; with
"Events always bookable directly" Confirm as fixed events). Both
require Edit planned events.
Seeing planned events in the normal calendar
Planners can show planned events in the normal calendar too, via the
display option Show planned events — as dashed cards, clearly
distinguished from fixed events.
The display option Show fixed events overlays the real bookings in the
planning calendar as a reference. They are not converted into planned
events and cannot be adopted here by accident. Use the overlay to develop
alternatives without overlooking existing occupancies.
Open the planning calendar and see planned events (read only); also unlocks the display option Show planned events
Edit planned events (Geplante Termine bearbeiten)
Edit, move, duplicate and delete planned events, convert fixed events to planned events (also all events of a project), and request and withdraw the verification of all planned events. Only applies to planned events, not to fixed ones.
Plan directly in the planning calendar (Im Planungskalender fest planen)
Create planned events in all rooms and request and withdraw verification for your own. This permission alone does not allow editing planned events of others.
Approving and rejecting does not depend on any of these permissions but on
who is assigned as verifier on the event type. Opening the planning
calendar requires View planning calendar or Edit planned events;
Plan directly in the planning calendar alone does not open it.
The "Planning calendar" module is switched on and off in the tool settings
on the tab Module visibility.
When it is off, the menu item is missing and the page is closed for admins
as well. Planned events that already exist are kept and can still be shown
in the normal calendar via Show planned events by anyone with a
planning calendar permission.
Since version 1.7.7, Plan directly in the planning calendar is independent
of Plan events directly: calendar and planning calendar are permitted
separately. Anyone who only has Plan events directly cannot create
planned events in the planning calendar. Since version 1.9.0 this also
applies when the switch Events always bookable directly is active, and
View planning calendar only allows viewing.
Calendar
Exports & Calendar Subscription
Take the calendar outside — as PDF (calendar, monthly overview, season schedule), Excel or an ICS subscription
The Export calendar button in the function bar opens the export dialog
with five tabs. The visible calendar range and the active filters are preselected in
every tab and can be adjusted there independently; the dialog closes after
the export. The two Excel tabs open in the mode Export by project; you
only see the preset time range there after switching to Export by
period:
Export
Contents
PDF Monthly Overview Calendar Export
A compact month display; the first tab.
Season schedule projects (PDF)
Year or season overview in wall-calendar style with project names per day — see below.
PDF Calendar Export
The grid as a PDF: the classic occupancy plan for posting up.
Excel Event List Export
The events of a time range or of selected projects as a table with selectable columns, ideal for further processing.
Excel Calendar Export
The calendar grid as a table.
Check period, project mode and active filters before exporting because they
define the content. Depending on the PDF variant, you can choose heading,
paper size, orientation and resolution (DPI), among other things. The event
list is better for sorting and further processing; the calendar grid keeps
the relationship between days and rooms. The PDF is downloaded right
after it has been created; Artwork keeps no copy for later retrieval. For
a new state, export again.
PDF Calendar Export and PDF Monthly Overview Calendar Export share
these fields:
Option
Effect
Heading
Title above the plan.
Project (optional)
With a project, the PDF Calendar Export uses the project period; the monthly overview determines the months of the project and creates one page per month.
Period
Without a project: Start date and End date in the PDF Calendar Export. In the monthly overview Day of start month and Day of end month; the whole month of the selected day is always exported.
Paper size
A4, A3, A5 or A6. Preselected: A4 in the PDF Calendar Export, A3 in the monthly overview. A6 is only possible in landscape format.
Paper orientation
Landscape format or portrait format. Preselected: portrait format in the PDF Calendar Export, landscape format in the monthly overview.
Resolution (DPI)
Standard 72, maximum 300.
Only the PDF Calendar Export additionally offers Days per page (default
7) and the Export mode: Events relative to each other shows
concurrent events side by side and makes overlaps visible, Events in time
blocks lists them one after another per time block and is easier to read.
Both Excel tabs have the toggle Export by project / Export by
period at the top:
Export by project: search for one or more projects or pick them from
the recently opened ones. All events of these projects are exported; the
calendar export spans from the earliest to the latest of these events.
Without a project the Export button stays disabled.
Export by period: Start date and End date. All events that
touch the period are included, also those that start before the period
and only end after it Coming with the next update. Events without an end
time are included if they start within the period.
Under Filter you narrow down by rooms, areas, room categories, room
attributes, event types, event properties and project status in both
modes.
Only the event list has the Columns section. All columns are
preselected and can be deselected individually: Event ID, Project name,
Start date, End date, Start time, End time, Event type, Event name, Event
description, Event Status, Room, Project team and Project properties
(categories, genres and sectors of the project). Admission is only
offered when the admission field is activated, Artists only when the
artists field for projects is switched on. Without the event status module
the Event Status column stays empty.
Planned events in the event list
The event list has no display settings. Anyone who may see the planning
calendar also gets planned events exported there. In the event status
column they carry the addition plannedComing with the next update, for
example "Option (planned)", or just "planned" without an event status. If
you only need fixed events, filter by this column or use the Excel
Calendar Export with Show planned events switched off.
In the three PDF tabs you can save the selected room, area and event
filters as a personal preset: above Active filters there is Save
current filters as preset (only when at least one filter is active); in
the Save filter preset dialog you enter a name. Saved presets appear as
chips under Saved filter presets and apply in all three PDF tabs. A
click resets the filters and activates the preset; the X deletes it after
confirmation. Period, project mode and display settings are not part of
the preset. The Excel tabs have no presets; for the calendar view itself
there are the saved filters.
Every tab except Excel Event List Export contains a Display
settings panel, preset from your current
calendar display settings.
Changes only apply to this export; your calendar view stays unchanged:
Event color — Color by event type, by event status or by main
category of project
Event content — Event name, Description, Project Status,
Project managers, Artists, Event creator, Admission, Event
status spelled out
Artist names instead of event title — artist names replace the event
name; events without artists still show the event name
Visibility — Hide unoccupied rooms, Show planned events, and for
the PDF calendar additionally Day remarks
The season schedule uses only the color source and the artist names from
this panel, because it contains no event tiles.
The Season schedule projects export is a year or season overview in the
style of a wall calendar: months as columns, days 1–31 as rows, and per day
the names of the projects that have events there. Times and event details
are deliberately left out; if a project has several matching events on one
day, the count follows the name ("Project name (3)"). Multi-day events count
on every day of their duration; events from the planning calendar are not
included.
Period — start and end date; up to 6 months are displayed per page,
longer periods run over several pages. The export is always in landscape
format.
Only show days with event type — if the event type filter is set, a
project only appears on days on which it has at least one event of the
selected event types. Without a selection, all events count.
Active filters — rooms, areas, room categories and attributes and
event properties as in the calendar; saved filter presets can be applied
here and new ones created via Save current filters as preset.
Display options — Show holidays (name and marker from the
holidays),
Show calendar weeks, Highlight weekends, Highlight project names in
color (color according to the selected color source), Show events
without project (then the event name is shown), Show room
abbreviations (after the project name), Half months per page (double
row height)
Characters always shown in full (default 16) — the font size in a
cell grows as far as row height and column width allow, but at most
until this many characters of a name fit without truncation. A smaller
value gives larger text and more truncated names, a larger value smaller
text and longer readable names.
Heading, Paper size (A3 as the default, or A4) and Resolution (DPI).
If Show calendar weeks is unticked, the calendar week column is dropped;
weekday and day number then share one column ("Mo 1") and the content
column per month becomes correspondingly wider. With High contrast active
in the display settings, text on color-highlighted project names switches
to white only on dark colors.
The Subscribe to calendar button sets up a personal ICS feed that
phone and desktop calendars can subscribe to — so the schedule lands in
your private calendar automatically:
Can be restricted to a time range, event types, areas and
rooms.
Activate calendar notificationsComing with the next update with a lead
time (minutes, hours or days) adds a reminder to every event in the feed,
just like the
roster subscription.
The reminder text is in your language, for example "Rehearsal starts in
one hour."
Alternatively, an ICS file can be downloaded (a one-off snapshot
instead of a subscription).
Planned events from the
planning calendar are never part
of the feed because they are not confirmed yet.
The feed contains all fixed events of the house that match your selection,
not only your own. This includes events whose room request is still open.
Events without a room appear as cancelled. Without a defined time range
the feed reaches indefinitely into the past and the future. Each entry
carries the event name (or else the project name), room and project as the
location, the description with the name of the person who created the
event, and a link to the project.
A subscription refreshes regularly in the calendar application, while a
downloaded file does not. If an event changes in Artwork, the change
therefore appears automatically only in the subscribed feed. You adjust
period and filters of the feed later via the same Subscribe to
calendar button; the subscription link stays the same.
Keep your subscription URL private
The feed address is meant for the signed-in person. Treat it like a
personal access key, as calendar applications retrieve the feed via this
link. If the link has been shared unintentionally, Renew link in the
subscription instructions creates a new address. The old link becomes
invalid immediately; afterwards, subscribe to the calendar in your
calendar application with the new link. For deactivated accounts the
feed no longer delivers data.
Define the organisation-wide hidden hours of the daily view and the day remarks column
Under System → Calendar (permission Calendar settings), you define
which hours the
daily view hides on quiet
days. This
organisation-wide setting also applies to the daily view of the duty roster
and consists of the fields Hidden from and Hidden untilComing with the next update. The
day remarks column is also activated here, and
project creation from events is controlled
here.
The range from Hidden from to Hidden until is the part of the day
the daily view hides. So do not enter your operating hours, but the
hours in which usually nothing takes place at your house. Hidden from
is the end of your operating hours, Hidden until is their beginning: to
keep 08:00 to 23:00 visible, enter 23:00 under Hidden from and 08:00
under Hidden until.
The range may therefore span midnight. Only full hours count, minutes are
ignored. The values are saved as soon as you leave the field.
Calendar daily view: on days without a timed event in this range the
hours are missing, and a note above the day says "Hours between … are
hidden". If an event in any room falls into this range on a day, that
day shows all 24 hours. All-day events do not trigger this.
Duty roster daily view: the range is only collapsed for rooms that
have an all-day event on that day and neither a timed event nor a shift
in this range.
If both values are identical, nothing is hidden.
Display, not a booking rule
The range limits neither permitted event times nor room availability. It
only changes the presentation of daily view.
Per Artwork instance, Activate day remarks column switches the column
on for all users. When active, the calendar, the planning calendar and the
duty roster show a dedicated column with
one shared remark per day; it applies to all rooms. The permissions
View day remarks and Edit day remarks control who may see and who
may edit the column.
Under Visibility of the column you define whether it can be hidden:
Choice
Effect
Users decide themselves
Everyone shows or hides the column via their display settings. It is shown by default.
Column is mandatory for all users
The column is always visible; the checkbox in the display settings is locked.
The section Project link of events contains the switch Project
creation possible when creating events (on by default). When it is on, a
new project can be created directly in the
event form when linking a
project. When it is off, the New project choice is missing there and
events can only be linked to existing projects, so that no projects are
created by accident.
After a change, review both a typical working day and an evening event. This
quickly shows whether the selected window is practical for most users.
Calendar
Event settings
Configure event types, statuses, properties, holidays, standard values (including "Events always bookable directly") and timeline presets
The functional event configuration lives under System → Events
(permission Event settings). The page is organized into tabs: Event
Types, BI Tags, Standard values, Public holidays & school
holidays, Event Status, Event properties and Timeline
Presets:
Event types categorize every event. Configurable per type:
Name, color and abbreviation (max. 4 characters) — this is how the
type appears on every event card,
Project assignment mandatory — events of this type need a project,
Individual event name mandatory — enforces a distinct name per event,
Relevant for project period — events of this type count towards the
automatically calculated project period,
Can sell tickets (only visible when Artwork-Tickets is active):
only events of such types appear in the ticketing component of a
project,
Verification mode: whether and by whom planned events of this
type in the planning calendar
must be confirmed
before they become fixed events: no confirmation, all named reviewers,
at least one, or a specific person. The mode has no effect on events
created directly in the regular calendar.
If Events always bookable directly is active, the
dialog hides this section; the stored configuration is kept and applies
again as soon as the switch is off.
The first event type in the list is the standard event type: it can
be edited but not deleted, and only events of this type can get
sub-events.
The shift settings no longer offer a venue-wide setting for shift-relevant
event types. Within a project the selection can still be maintained as a
hint for planning, see
Shift information in the project.
Event types affect more than colour. Before creating a new one, decide
whether it extends the project period, requires a project, needs separate
verification and should appear in shift planning. Clear names and short,
distinct abbreviations make dense calendar views easier to read.
The optional event status module adds freely definable statuses to
events (e.g. requested, confirmed, cancelled): each with a color,
a sortable order and a default status for new events. The module is
activated at the top of the status page; the display option Use event
status colour then colors the calendar by status instead of by event type,
and Event status spelled out shows the status as its own row with a
colour dot on the event tile.
Event properties are configurable attributes with an icon and a name
(Publikum for audience and Laut for loud are supplied; you add others
such as Catering needed yourself). They appear as
checkboxes in the event form, as icons on event cards and as filters in the
calendar.
Properties describe practical effects of an event and are therefore a good
complement to event types. Rehearsal would be a type, for example, while
loud, with audience or catering needed are properties that can occur
with different types. This keeps the number of event types manageable and
enables targeted room filters.
Under Public holidays & school holidays you maintain the public holidays and
school vacations that the calendar, planning calendar and duty roster show
in colour on the day rows. There are two ways:
Public holidays & school vacations via interface: first the country
(Germany or Switzerland), then under Select states & color any
number of federal states or cantons as chips and a colour, and finally the
checkboxes Holidays and School vacations. Save & Import loads
the entries from the current year until the end of the year after next;
identical holidays of several states are merged into one entry, and
statutory public holidays are automatically marked as special days. Every
new run replaces the previously imported entries with the current data;
entries you created yourself are kept. On 1 January, Artwork repeats the
import automatically with the saved selection so that the new following
year is available (this run sets the colour to dark grey).
Create holidays & school vacations yourself: own entries with name,
start and end time, federal states (without a selection, the entry
applies nationwide), colour and the switch Repeat the holiday
annually / One-off public holiday.
In the table, the column Via interface shows where an entry comes
from (imported via the interface or created manually); imported entries
cannot be edited or deleted individually, manual ones can. Check the
Special Day column after every import. If several entries fall on the
same day, an entry you created yourself defines the day colour before an
imported one; a differing second colour appears as hatching in the
calendar.
Every entry has a Holiday type: Statutory public holiday, School
vacations or Custom entry. Filter by type narrows the list down to
one type.
The checkbox Treat as special day decides whether an entry counts as a
special day in the duty roster's working-time calculation: on a special day
without work, a person's daily target drops to 0 (or by the weekday average
in three-month mode), provided their contract has the special day rule
active; hours worked count normally. Statutory public holidays are special
days by default, school vacations are not.
Access for shift planners
People with the permission Plan shifts open the holidays page as a
read-only view and can only set the special day checkboxes there.
Creating, editing, deleting and importing require the permission Event
settings.
The standard values speed up creating events: Default event duration
(minutes), Default start time and Full day as default.
The optional Admission field is also activated here: when the toggle is
on, an admission time can additionally be entered on events. Via a display
option in the calendar, the admission then appears in the event cards above
the existing time information.
The values are starting points for new events and can be overridden in the
form at any time. Choose them so that the most common case needs as little
input as possible without forcing special cases.
The switch Events always bookable directly turns off room booking
requests and event verification for the whole installation. When it is
active, everyone who may create events books directly in the calendar, and
planned events are confirmed without a review step:
The event form no longer offers Request occupancy, the menu entry
Event verifications disappears, and room admins receive no requests.
Planned events are adopted with Confirm as fixed events without a
review step; "Request verification", "Approve" and "Reject" are gone from
the planning calendar. Since version 1.9.0, creating planned events
still requires the permission Plan directly in the planning calendar
(room admins in their own rooms do not need it).
The room settings Can be booked by anyone and Authorized to
request have no effect in the regular calendar. Request room
occupancy counts like "create
events" (including bulk creation and series); Plan events directly only
still covers editing, declining and deleting other people's events,
events without a room and timeline presets. Room admins keep editing in
their rooms.
Room page, event type dialog and notification settings hide the request
and verification parts; the permissions page marks affected rights as
"Without effect" or "Partly without effect".
When switching on, a dialog shows how many open room requests become
firmly booked events and how many planned events with an open
verification request become fixed events. Switch on and accept
requests records this in the event history but sends no notifications.
Cannot be undone
The requests accepted when switching on remain fixed events even if you
switch the setting off again later. The room and event type configuration,
however, stays stored and applies again immediately after switching off.
Central event settings apply to all users and often to existing events as
well. Personal display options and saved filters remain individual. Before
deleting a used event type, status or property, check which existing events
reference it. When you delete an event type, all its events switch to the
standard event type, including those in the trash.
What the duty roster is and how its pieces fit together
The duty roster (German UI: Dienstplan) is Artwork's staff scheduling
module. Planners define shifts — time blocks that need a certain number
of people in certain functions — and fill them by drag & drop. Once a week
is fully planned, the plan is committed: shifts become binding and the
assigned staff are notified.
The roster combines three perspectives: in the upper grid, planners work by
event, room and craft; the workforce panel shows each person's workload; and
in My operational plan workers see only their own duties. Changes,
conflicts, working-time rules and approvals all use the same shift data, so
no separate plan has to be reconciled.
A time block on a specific day with start/end time, a break, a craft and a required headcount. Shifts can stand alone (tied to a room, optionally linked to a project) or belong to an event.
Craft
Gewerk
A trade or department (e.g. Ton, Licht, Bühne, Kostüm). Every shift belongs to exactly one craft, and workers can only be scheduled into crafts they are assigned to.
Function
Funktion
The role within a shift (e.g. Meister, Mitarbeiter). The craft defines which functions exist. A person's capabilities in their work profile are still called qualifications.
Slot
Platz
A fillable position of a shift. A shift defines how many slots it has per function; the occupancy display (1/3) counts filled against required slots.
Worker
Mitarbeiter*in
Anyone who can take shifts: internal employees, freelancers and external service providers.
Commit
Festschreiben
Locking a planned period per calendar week and craft. Committed shifts show a lock icon, changes are tracked, and workers are notified of their final roster.
Approval
Freigabe
The second instance when the approval workflow is active: planners submit a calendar week, approvers release or reject it (status Pending / Approved / Rejected).
Accept / decline
Zusage / Absage
A scheduled person's reply to their shift, provided shift confirmation is active and the person has the permission.
Standalone shifts are created directly in the duty roster for a room
and can additionally be linked to a project. This is typical for services
that don't hang on a single event.
Event shifts are attached to a calendar event (a performance, rehearsal
or setup) and appear inside that event's card. They can also be planned from
the project's shifts tab.
So a standalone shift needs no calendar event, but always a room; the
project is optional. This suits office hours, standby duties, maintenance
or cross-project work. The link decides in which filtered and
project-related views the shift appears (see
Shifts without a room or event).
Choose a period and context. Work venue-wide or restrict the plan to a
project, rooms, event types and crafts. The view switch Week | Day |
List toggles between grid, daily view and list.
Create demand. Add shifts manually or use time presets, shift templates
and template groups for recurring sequences. Required functions and slot
counts reveal open slots.
Assign staff. Drag available people onto shifts. Before the assignment,
Artwork checks time overlaps, vacation and unavailability; it continuously
checks functions, contracted hours and working-time rules.
Review the plan. Filter for understaffed shifts, check staffing per
craft, weekly hours and rule violations, and use the Week status page
for an overview of all crafts and calendar weeks.
Commit or submit for approval. A finished period becomes binding per
calendar week and craft. Workers are informed; later changes remain
traceable.
What you can do in the duty roster depends on your permissions (names as
shown in user rights, module Duty roster). The three levels build on
each other — a higher level includes the lower ones:
Permission
Allows
View duty rosters
Open duty rosters, list view, week status, other people's rosters and the PDF and Excel exports of the duty roster
Plan shifts
Create, edit and delete shifts; assign and remove people; apply templates; manage substitute days off; decide work time change requests of the own crafts; set availability status; accept or decline shifts on behalf of others
Commit duty rosters
Commit and reopen calendar weeks per craft, or submit an approval request when the workflow is active
View own roster
Open the personal roster and export it as PDF
View own uncommitted shifts
Exception for individual people: see own shifts in the personal roster before they are committed, although the shift setting Hide uncommitted shifts from own roster is active
Accept or decline shifts
Accept or decline own shifts (requires the shift setting Shift confirmation by employees)
Enter own individual times
Create, edit and delete individual times for yourself in the personal roster, from today on and also as a series. Past days stay reserved for people with Manage availability of others or Plan shifts
Subscribe to roster calendar
Subscribe to the personal roster as an ICS feed
Shift settings
Manage the shift settings. If granular mode is active there under Permission model, the Fine-grained shift settings permissions decide per tab (view or edit)
Manage availability of others
Create and edit vacation, availability and individual times of other people
View staff info data
The info icon on person tiles: season figures, substitute days off and vacation per person
View hour accounts
Read working-time accounts and weekly hours of all people — also required for working times and overtime in the info window
Pay out overtime
Manually pay out overtime
“View own roster” also protects access
Without the permission View own roster the personal roster cannot be
opened — the permission controls access, not just the menu entry. Other
people's rosters are reachable for people with planning or management
rights; with those they can open their own as well.
Approvers are not a permission
Who may approve requests is not controlled by a permission but by the
user list of the
approval workflow
in the shift settings.
Additionally, each craft defines who may schedule which type of worker into
its shifts — see Shift Settings.
Shift Plan
The Duty Roster
Use the week, day and list views, display settings, the workforce panel and the shift history
Open the duty roster via Shift plan → Duty rosters in the sidebar. The
week view has two halves:
Top — the planning grid: rooms as rows, days as columns (grouped into
calendar weeks, "KW"). Each cell shows the events taking place in that room
on that day, with their shifts, plus standalone shifts. Only rooms with
the room property Relevant for disposition appear as rows (see
Rooms, areas & booking access).
Bottom — the workforce panel: all workers who can take shifts, grouped
by craft, with their weekly hour balance. This is where you drag people from
when assigning staff.
The divider between the two halves can be dragged to resize, and the panel can
be collapsed entirely.
Two directly editable date fields showing weekday, calendar week and number of days. At most 6 months are loaded: a longer period (also from the quick selection, such as Next 12 months) is cut to six months from the start date, and Artwork briefly shows the notice Maximum 6 months possible in the display. The calendar icon opens Select period with the mode chips Day, Week, Month, Free selection, the quick selection (Today, Current week, Current month, Next 7/14/30/90 days …) and two month calendars; clicking a calendar week number selects that week. With Free selection you click the start day first and then the end day. The selection in the window only takes effect after Apply. Keyboard with the bar focused: ←/→ page, T jumps to today.
Current week / Current month
Two buttons next to the date range jump to the running week or month with one click. Today is reachable via the quick selection in Select period or the T key.
Arrow navigation
The arrows Time range back / forward next to the date fields shift the loaded period by its own length. If exactly one whole calendar month is selected, they jump to the previous or next whole month.
Scroll mode
A second group of arrows with a mode icon between them (tooltip Change scroll mode): Jump by day, Jump by calendar week or Jump by month. These arrows scroll within the loaded period to the next day column, calendar week or first day of the next month, without reloading. The mode is stored per person and also applies in the list view and in article planning.
Project search (compass toggle)
Locks the visible period to a project: search for a project or artist and the roster shows exactly its time span, with a link to the project's shifts tab.
View
The switch Week | Day | List.
Zoom
Levels 55 %, 75 % and 100 % (also Ctrl/Cmd + mouse wheel): narrows the day columns so more days fit at a glance. Below 100 % shifts appear as a compact pill with time, craft abbreviation and staffing; a click opens the shift. You can also drag people onto the compact pill Coming with the next update; to assign someone to a specific function slot, zoom back to 100 %. See Views & Display Settings.
Edit (pencil switch)
Multi-edit mode: select several room/day cells and create or delete shifts in bulk. The tooltip explains what the mode does. Only visible with the permission Plan shifts.
Calendar subscription (calendar star, tooltip Subscribe to shift calendar)
Personal roster as ICS feed, see Exports. Only visible with the permission Subscribe to roster calendar.
On narrow screens the function bar collapses: below 1536 px width, zoom,
Help & legend, commit, history, export, fullscreen and the calendar
subscription move into the More options menu; display settings and
filter stay visible as buttons.
The project search does more than enable a filter. It adopts the calculated
project period, shows the related events and shifts and provides a direct way
back into the project. A production can be planned completely without
parallel projects overloading the grid. The period can be adjusted manually
afterwards if needed.
The filter panel narrows the grid down to what you're working on. Filters can
be saved ("Saved filters") and re-applied with one click; active filters
appear as removable tags.
Event types — e.g. only performances, only setup times
Crafts — only show shifts of selected crafts
In the week and the daily view, the filter window also offers the toggle
Only show shifts that are not fully staffed under Shift Filters. It
is the same one as in the display settings.
The gear icon opens the display settings. They are personal to you and
persist between sessions. The window only shows settings that take effect in
the view currently open — so the week view has different options than the
daily and list views, and the daily view and the project shifts tab share
one set.
The most important options of the week view: Show events (off = shifts
only), Hide unoccupied rooms, Only show shifts that are not fully
staffed, Show staffing per craft, Show qualifications, Show
description and Expand days. Every option with its effect, the views
it applies in and when to use it — including those of the daily and list
views — is described under
Views & Display Settings.
If the day remarks column is
activated for your instance, the day notes from the calendar are also shown
in the duty roster. Room names and the date row move along while scrolling,
so they stay visible even with tall, filled cells.
Each craft expands into its workers; within the craft, people are grouped by
function. Expanding and collapsing reacts immediately and remembers which
crafts are open even with an active craft filter. Per worker row you see:
Avatar and name — with an info button for the
info window and a link to their individual roster
Hour balance — the chip shows the week's planned time against the
contracted hours (e.g. -22:30 h means 22.5 hours still unplanned); green
and red indicate over- and under-planning
Day cells — each assignment appears as a chip (e.g. 10:00 – 18:00 Raum B), so you always see who is already booked and when. With shift
confirmation active, the reply status sits next to it as a coloured pill:
blue requested, green accepted, red declined (details and comment in
the hover text).
Day service balls — day services are filled completely in their
colour; the icon is automatically white or black depending on the
brightness of the colour.
When someone enters, changes or deletes an availability or absence, the
person row updates in all open duty roster windows without reloading — also
for the day status from the day modal and for changes made via multi-edit.
After reloading, navigating dates or changing filters, the workforce panel
returns to the position you last scrolled to.
The panel has its own controls: an edit switch (multi-edit on worker
cells with the actions Edit Entries and Delete Entries), the button
Create individual time series for
recurring individual times,
day services (these three only with the permission Plan shifts), the
highlight switch (click a shift to
highlight its assigned workers), the compact view, a sun/moon switch
that renders the workforce panel light or dark (the choice is stored per
person; plus/minus hours, availability, absence, substitute days off and the
staffing traffic light are readable in both modes), the people filter
(funnel) and the sort menu (default order by function, grouping by
function with or without duplicate entries, alphabetical, alphabetical
internal/external — see
Sort menu).
Show freelancer — show or hide freelancers in the workforce panel;
the choice survives reloading.
Only show people with open rule violations — a toggle with a counter
of open violations. While it is active, a notice bar above the workforce
panel offers Remove filter; an empty result is explained ("No people
with open rule violations in this period."). In the daily view this filter
sits in the filter window.
Crafts and functions — narrow the workforce panel to certain
crafts or functions.
In the craft row of the workforce panel, each day shows a pill
staffed/demand with a traffic-light colour (red: less than half of the
slots staffed, orange: at least half, green: fully staffed); the KW column
shows the weekly total, the tooltip names demand, staffed and open. Clicking the pill filters
the grid to the open shifts of that craft, a second click resets the filter.
If you don't need the pills, hide them via the display setting Show
staffing per craft.
Clicking a day cell opens the day modal with all information about this
person for the chosen day, in two columns. You can open other people's rows
only with the permission Plan shifts; without it only your own row opens,
and the availability status is read-only there.
Left: the assigned shifts, the
project assignments and the
individual times. Below each shift — with shift confirmation active — the
reply status is shown as a pill (Requested, Accepted on …,
Declined on …, with comment); planners can record the reply on the
person's behalf right there. The trash button removes the person from
the shift.
Right: the availability status for the day, day comment, rule
violations, substitute day off and the availabilities the person has
registered.
Under Availability status for this day you choose one of four statuses;
their labels follow the language of the interface Coming with the next update,
also in the duty roster cell and in multi-edit. For internal users with a work time pattern the status also affects
the hour account:
Status
Meaning
Effect on the hour account
Available
No entry; the person can be assigned.
None. The work done counts.
Work-free day
Absence like vacation.
Counts like vacation: the day is target-neutral (actual = target). Work done anyway is added on top.
Not available
Absence like sickness.
Counts like sickness: actual = target. Shifts the person is still assigned to do not count in addition on that day.
Free
Free day, either full or half (morning or afternoon).
None. The day counts as a free day in the key figures.
If you set Free or Not available, Artwork first checks the
consequences: shifts and individual times on that day are offered for
removal (Yes, remove or No, only change status). For all three
statuses other than Available, the
project assignments and wishes
that the new status would dissolve are also listed with project, type
(binding/wish) and days. Free dissolves binding assignments and wishes,
Work-free day and Not available only wishes. If only assignments
are affected, you confirm with Change status anyway. Multi-edit in the
workforce panel only asks about the project assignments when it changes the
status; it does not remove shifts or individual times.
From here you can also open the shift history for this
person and day. Request work time change is only available on your own
shift — requests are always bound to the signed-in person and their
assignment to the shift (see Requesting a working-time
correction).
Individual times add working time not attached to a shift, such as
office work, home office or training. They can be created individually or as
a recurring series for several people, so these times are included in the
daily and weekly view as well.
The info icon on the person tile opens the info window (permission View
staff info data). The icon exists only for internal users, not for
freelancers and service providers. The window has the tabs Season-related
data, Substitute days off and Vacation; each tab loads its data
only when opened. If work time accounting is switched on in the
shift settings, the
tabs Actual hours (month by month) and Overtime are added. For other
people, these two tabs only show data if you also hold the permission View
hour accounts or HR administration. With the permission Pay out
overtime you book out payable overtime in a documented way in the
Overtime tab; previous payouts remain in the history. What the figures
mean is explained under
Understanding a person's key figures
and Paying out overtime.
People can be assigned to a project directly in the duty roster — for
individual days or the entire project period — before any concrete shifts
exist. Personnel planning can start earlier, and everyone sees who is
earmarked for which production. The feature can be switched off in the
shift settings under
Project assignments; all sections, stripes and buttons described here
are then missing.
Binding assignment (for planners): In a person's day modal you'll find
the Projects section. Via Assign project you bindingly assign the
person to a project, either for Single day(s) or for the Entire
project period; several days are picked in an inline calendar. You need
the permission Plan shifts for this. Projects whose period includes the
selected days are suggested first; the search finds all others. The project
period runs from the earliest to the latest event of the project. If the
project has events with an event type marked as Relevant for project
period, only those count. A project without events has no period and can
only be assigned day by day, and the same applies to a project whose period
is longer than two years.
An assignment for the entire project period "moves along": if the project
shifts in time, it adapts automatically. Assignments for single days do not
move along. If such a day lies outside the project period after an event
was changed, the assignment is dissolved. In the event dialog, Artwork asks
before saving and lists the affected people and days. For binding
assignments, planners and the affected person are notified.
When assigning on days off or absence days, Artwork warns and only saves
once you confirm with Assign anyway. Days on which the person is already
in a shift of the same project or is already assigned are skipped. Internal
users are added to the project team with the assignment and are notified
about new, accepted and removed assignments. The assignment appears as a
coloured stripe in the day cell. Via multi-edit in the workforce panel you
assign all selected people on the selected days in one step; only projects
whose period covers all selected days can be chosen there. You remove an
assignment in the day modal with Remove for this day only or Remove
entire assignment.
If an assigned person is placed into a shift of the same project, the shift
replaces the assignment on the days of the shift. If the person is removed
from the shift again or the shift is deleted, the assignment comes back. It
does not come back if the person is still in another shift of the project
on that day or has meanwhile been given the status Free. In the daily
view, in the project's shifts tab and in the list view with Detailed
function overview per shift, assigned people are listed first in the
selection list of an open slot, bindingly assigned people before people
with a wish (see staffing shifts). Assignments
also appear in My operational plan, in the project's shifts tab
(display setting Show project assignments) and, binding ones only, in the
PDF export of the personal operational plan. In the shifts tab, the
Assigned persons overview has three columns: Entire project period,
Single days and Wishes. Single days are bundled per person into
ranges; planners expand them into day chips and remove individual days. Via
Assign person you assign people directly to the project there. People
who may not see the duty roster also see their own assignments and wishes
in the overview, but only their own.
Project wishes (for employees): In My operational plan a person
enters themselves, non-bindingly, as a wish for a project via the heart icon
in the day header (Enter project wish), likewise for individual days or
the whole period. The same works in the project's shifts tab via Enter
wish and in the day modal of your own row. Everyone can enter a wish only
for themselves. Planners see wishes as a striped stripe in the day cell and
when staffing shifts of the project. In the day modal, Accept turns the
wish into a binding assignment for all days of that wish. No wish is
possible on days with a registered absence; if the person enters an absence
later, the wish is dropped on those days.
The Day view turns the grid into a day-by-day list — each day becomes a
section with one row per room: events on the left, shifts on the right. It
shows at most 8 days and is ideal for the detailed planning of a single day
or for use on the event day. Artwork cuts a longer period from the start
date and points this out with Maximum of 8 days possible in the daily view
of the shift planComing with the next update. There is no
drag & drop here: you staff a slot by clicking Unoccupied and picking the
person from the list. You also look for a
replacement after a
decline and record replies on a person's behalf via the assignment menu.
The List view (also reachable via Shift plan → Shift plan list
view) shows all shifts of a period as a list, grouped by day and below
that by room. It is the fastest way to review staffing status:
Each row shows the craft abbreviation, the time, the occupancy (2/3 = two of
three slots filled) with a status dot (green fully staffed, orange partial,
red empty) and the per-function breakdown. Instead of the dot, a warning
triangle is shown when an assigned person is not available on that day. If
the shift belongs to a project, the project name at the end of the row leads
to the project's shifts tab. The three-dot menu of the row contains Edit
shift and Show in shift plan. With the permission Plan shifts you
create new shifts right in the list via Add Shift.
The pencil switch in the function bar turns on multi-select: every shift row
gets a checkbox, and above the list the number of selected shifts appears
together with Duplicate and Delete. Both actions require the
permission Plan shifts; without it the switch can still be turned on, but
the action is rejected with an error message. The same applies to the whole
selection as soon as it contains a shift of a craft you may not plan.
Duplicate creates each selected shift once more on the same day in the
same room, with the same times and the same demand per function, but
without assigned people. The copy is not committed and not requested, even
if the original is, and does not belong to the series of the original.
Delete moves the selected shifts to the
recycle bin after a
confirmation prompt, including committed and staffed ones. For committed
shifts, the assigned users and the planners of the craft are notified.
If Hide shift row is active in the display settings, there are no
checkboxes; switch the option off for multi-select.
With Detailed function overview per shift, each shift additionally
shows its slots. There you staff a slot via Unoccupied, as in the daily
view.
The list has its own display settings — Show fully staffed shifts,
Show appointments, Sort by shift groups, Detailed function
overview per shift with Hide shift row, Show description, Show
Shift group tag — described under
List view only.
The function bar also contains the Today button, the scroll mode (here
the arrows shift the period by 1, 7 or 30 days) and the history. A lock
marks committed shifts, a request icon requested ones. Show in shift
plan opens the week view with the calendar week of the shift and
highlights the shift there; the period of the week view is set to that week
in the process.
The info icon in the function bar opens the help panel with three areas:
Legend — what the markers in the cells mean: staffing traffic light,
lock for committed shifts, Approval requested, Changed after
commitment, warning triangle for open and check chip for processed rule
violations, Assigned but not available, overbooking, day service,
special day, substitute day off and the reply pills.
Operation — the most important actions of the current view.
Workflow — the path from the shift via the assignment to commitment
and approval.
The explanatory box on how a shift is built, which used to sit in the shift
dialog, lives here.
If the week or day grid shows nothing, a notice names the reason and the
next sensible step:
Notice
Cause and next step
No rooms released for the duty roster
No room is visible. Only rooms with the room property Relevant for disposition appear in the duty roster; a link leads to the room management. If a filter or the display setting Hide unoccupied rooms is active, the notice says so.
Master data missing
There are no crafts or no functions yet. The notice shows what is missing and links to the shift settings.
No shifts in this period
Nothing is planned in the period. Planners start right away via Add Shift or Add Shift based on templates.
All shifts are hidden
The period contains shifts, but a filter, Only show shifts that are not fully staffed or Hide unoccupied days hides all of them. The notice lists the causes that apply.
The notice can be closed. People without planning rights get a pointer to
the responsible people instead of the buttons.
The History button opens the shift history: a log of every change made
to shifts — who created, edited, staffed, committed or deleted what, and
when. Especially useful after a plan was committed, since late changes must
be accounted for. Besides shifts, the history also logs day entries of
people: availability and absence, notes, individual times, day services,
substitute days off and project assignments. Anyone who may view the duty
roster can open the history.
The left column separates two blocks:
Data selection: loads the entries from the server, filtered by period
(refers to the shift start, not to the change date), craft and
person. If you open the history from the function bar, nothing is
loaded at first; Load history fetches the entries. After that, every
change to period, craft or person reloads automatically. Choosing a person
loads immediately.
Narrow down — takes effect immediately on the loaded entries without
reloading: Search in results (with highlighting), Kind of change,
Shift (searchable dropdown; deleted shifts are marked) and Only
subsequent changes (after commitment). To search server-wide, press
Enter or use Search in all entries.
50 entries are loaded at a time; the summary above the list shows how many
of how many are loaded, and Load more at the end of the list fetches the
next ones. Narrow down only affects the entries already loaded. Under
Kind of change you choose between Staffing, Shift details, Shift
created/deleted and Commitment & request; further kinds such as
Confirmations, Availability & absence, Notes and Other day entries
appear as soon as such entries are loaded.
The Person field accepts users, freelancers and service providers and
has three scopes: Only actions on the person, Person + their shifts
(default — shows, for example, when the shift the person is in was
committed) and Also carried out by the person. Each entry then says why it
is listed: Concerns Max, Max is scheduled in this shift or Carried out
by Max.
Above the list a summary shows the active filters as removable chips and
Reset all. There you also choose the grouping: by change date
(newest first) or by shift day; the day headings say what the date
means.
Each entry shows its shift in a header line ("#12249 · Tue 18.08.2026 ·
14:00–22:00 · CS · Hauptraum · project"); the before/after table can be
expanded. Creation entries are labelled Shift created, edits Shift
data changed; staffing entries show person and function as a chip. When
grouped by shift day, all actions of one shift form a timeline under one
header; clicking the header shows only this shift, and a fixed header
line with Show all shifts appears at the top. An empty result explains
what is empty and offers the next step — such as Expand period to whole
months or Include their shifts.
The history opens in several places with a matching preset: from the
function bar (empty, current period), from the day modal (person and day
preset), from My operational plan (person preset), via the clock icon
Show history of this day, which appears in the week view when hovering
over a day header (all people on that day), and from the dialog of an
existing shift via the Shift history button (only this shift; the
history opens on top of the dialog). Except when opened from the function
bar, the entries are loaded right away. Export as Excel in the left
column adopts period, craft and person filter; with a person filter the file
contains the column Relation, see
Exports.
The page Shift plan → Week status shows all crafts across several
calendar weeks with commitment state, open requests, unacknowledged
changes, open rule violations, open slots and request deadline — the
overview before you commit. It is described under
Committing & Approval.
Every worker has a personal counterpart to the duty roster: Shift plan →
My operational plan lists only your own shifts (permission View own
roster; it controls access, not just the menu entry). Workers who cannot
see the full duty roster still see their own assignments here.
Committed and provisional assignments are distinguishable. Your house can
decide in the shift settings that people only see their shifts in their own
roster once they are committed
(Uncommitted shifts in own roster);
the permission View own uncommitted shifts exempts individual people.
Whether draft shifts already appear in the calendar subscription is also
set centrally in the shift settings. In case of deviations, the person can request a work time
change without editing the roster.
From their own operational plan, workers can also
enter project wishes and — when
Shift confirmation by employees is active and they hold the permission
Accept or decline shifts — accept or decline shifts (see
Committing & Approval).
Everything else about the personal roster is covered under
Personal Roster & Working Time.
Shift Plan
Views & Display Settings
Week, day and list view compared, every display option with its effect and scope, the options of the workforce panel and recommended settings for typical tasks
The duty roster has three views, each with its own set of display settings.
On top of that come the zoom of the week view and the tools of the
workforce panel. This page explains every option, says where it takes
effect and suggests settings for typical tasks. How to operate the roster
itself is described under
The Duty Roster.
Display settings are personal
Everything on this page applies only to you and is kept across sessions.
It does not change any shifts and does not restrict what others see. Who
may see and plan which shifts is controlled by the
permissions.
Rooms as rows, days as columns; assign people by drag & drop. The main view for planning.
Day
Switch, position Day
One section per day, one row per room, events on the left, shifts on the right; up to 8 days. For detailed planning and the event day.
List
Switch, position List, or menu Shift plan → Shift plan list view
All shifts of the period as a list by day, with the staffing status per row. The fastest way to find open slots and to duplicate or delete several shifts.
Project shifts tab
In the project, the tab with the shift component
The daily view, narrowed to one project, with the project assignments. Shares its settings with the daily view (see below).
The views show the same data. Period and filters, however, are stored per
view: if you switch from the week to the list and back, your narrowing is
still there.
The percentage dropdown of the week view offers the levels 55 %, 75 % and
100 % (default); Ctrl or Cmd + mouse wheel works here too. Unlike
in the calendar, the zoom controls the width of the day columns, i.e.
how many days fit side by side; the room rows keep their height.
Below 100 % shift cards show only the craft abbreviation, start time and
staffing (2/3) with a traffic-light colour; the full time span is in the
tooltip. On wide screens the chip Compact in the function bar points
this out. A click opens the shift. You can drag people onto the compact
card in compact mode as well; the chip's tooltip says so too
Coming with the next update. The individual function slots are not visible there,
though; to assign someone to a specific slot, zoom back to 100 %. With
Show description the description appears shortened below the compact
card, the full text in the tooltip.
The gear in the function bar opens the display settings window. It only
shows options that take effect in the view currently open. A dot on the
gear means that at least one option is switched on (options that are on by
default and "Share time period across views" do not count). Changes apply
after Save.
Calendar, planning calendar, duty roster, list view and article planning always show the same period. When you switch it on, all views adopt the period of the current view.
W, D, P, L
When you switch between calendar and duty roster for the same week. Switch it off if, for example, you permanently work two weeks ahead in the duty roster.
Shows the event tiles (and project group bars) in the room grid. Switched off, the grid contains only shifts; artwork then loads no events, which speeds up rendering, and Hide unoccupied rooms counts shifts only. Default: on.
W
Switch it off for pure staff planning when you know the events from the calendar anyway.
Hide unoccupied rooms
Rooms without events and shifts in the period disappear from the grid.
W, D, P
For venues with many rooms; almost always useful in the project shifts tab.
Hide unoccupied days
Days without visible events or shifts are skipped in the daily view.
D, P
When a project has only a few performance days over several weeks.
Only show shifts that are not fully staffed
Only shifts with at least one open slot stay visible. You can reach the same setting in the filter window under Shift Filters.
W, D, P
At the end of planning, to work through the remaining demand; switch it off again afterwards.
Show staffing per craft
Shows the pill staffed/demand with a traffic light per day and calendar week in the craft row of the workforce panel. Clicking the pill filters the grid to the open shifts of that craft. Default: on.
W
Switch it off if you want a calmer row; the click filter stays reachable via the people filter.
Show project assignments
Shows the Assigned persons overview and the avatars in the day bars. Only appears if project assignments are enabled in the shift settings. Default: on.
D, P
For productions that assign people bindingly or as a wish.
Show events from other projects
Also shows events of other projects and without a project in the project shifts tab.
P
When you want to see what else is happening in the venue while planning a production.
Show shifts from other projects
Also shows shifts of other projects and without a project in the project shifts tab.
P
To spot people double-booked across productions.
Show project group
Shows the project group on the event tiles.
W
For festivals and series with many individual projects.
Timeline
Shows an icon on event tiles for opening and adding to the timeline.
W
When shifts are based on schedule points (admission, start, end).
The list has its own window with two sections. Show appointments is
the list's counterpart to Show events in the week view, but it is a
separate setting with a different effect.
Section
Option
Effect
When useful
Visibility & Filters
Show fully staffed shifts
Shifts that are already fully staffed also stay in the list.
Switch it off to see only the remaining demand.
Visibility & Filters
Show appointments
Events appear in a separate column next to the shifts.
When you want to read shifts in the context of their event.
Visibility & Filters
Sort by shift groups
Groups the shifts within a room by shift group.
For venues that plan in shift groups.
List layout
Detailed function overview per shift
Shows the assigned people and the open slots below each shift.
To check staffing without clicking into the shift.
List layout
Hide shift row (sub-option, only with the detailed overview)
Hides the header row of the shift; the craft abbreviation then precedes each person row.
For a pure list of people, for example for printing.
The lower area with the assignable people has its own controls, which are
not in the gear window. They too are stored personally unless stated
otherwise.
Element
Effect
Show user overview / Hide user overview (arrow in the floating bar at the bottom)
Collapses or expands the workforce panel.
Dragging the divider
Changes the height of the workforce panel; a double-click on the handle shows or hides it.
Compact view
Smaller person rows so more people are visible without scrolling.
Sun/moon
Renders the workforce panel light or dark. Plus/minus hours, availability, absence, substitute days off and the staffing traffic light remain readable in both modes.
Highlight (light bulb)
Click a shift or a person: everything else is dimmed. Only for the current session.
Multi-edit (pencil)
Multi-edit on person cells: assign one person to several shifts. Only for the current session and only with the permission Plan shifts.
The sort menu of the workforce panel defines the order in which people
appear within a craft:
Reset: removes the alphabetical sorting. The default order applies
again: craft managers first, then following the order of the craft
functions from the shift settings.
Group by function (default: on) — people appear under the heading of
their function. The sub-option Show duplicate entries (default: on)
shows a person with several functions under each of these functions;
switched off, they appear only once.
Alphabetically Intern/Extern ascending or descending — sorts
alphabetically and inserts a separator row External before
freelancers and service providers.
Alphabetically ascending or descending by first name / last name:
pure name sorting. Whether first or last name is used, also within
internal and external, is decided by the
organisation-wide Sort settings
in the shift settings. It cannot be changed in the sort menu itself; the
menu entry only names what is currently sorted by.
A filter (funnel) decides which rooms, events and crafts are loaded.
It also affects the workforce panel (craft filter) and exports, and it can
be stored as a saved filter.
A display setting (gear) decides how the loaded content looks. It does
not affect other people.
The filter Only show shifts that are not fully staffed is
deliberately reachable in both places; it is the same setting.
If a shift is missing, first check the active filters (tags in the filter
window, dot on the funnel), then Only show shifts that are not fully
staffed and the period.
If filters or display settings hide all shifts of the period, the week and
daily views show a notice with the causes instead of an empty area: an
active filter, Only show shifts that are not fully staffed or Hide
unoccupied days.
Shift Plan
Creating Shifts
The shift dialog, function slots, breaks according to the Working Hours Act and templates
Shifts are created directly in the duty roster (requires the Plan shifts
permission). Hover over a room/day cell and two icons appear at the bottom
right: Add Shift based on templates (creates shifts from
templates or template groups in this
cell) and Add Shift (plus). The plus opens the shift dialog.
The same dialog is used for editing — clicking any shift card opens it as
Edit shift.
Before creating new shifts, decide whether they belong to an existing event
or should stand alone. Event shifts inherit the date and context of the
event; standalone shifts are more flexible for duties without a calendar
entry.
At the very top is the collapsed row shift templates: a
template fills the whole dialog with saved values
(times, break, craft, functions). The list is searchable. The Time
presets sit further down, next to the time fields.
The craft determines who can be assigned and which function slots
the shift offers — which is why it comes before all other fields. Changing
the craft of an existing shift removes all people already assigned; the
dialog points this out.
Start time / End time with date: the working time. A shift longer
than 10 hours triggers a warning. For shifts attached to an event, the
dialog also warns if the shift starts before the event or only after it
has ended. Both are hints; you can still save.
Prefilled from the cell you clicked; standalone shifts keep the room so they
appear in the grid. The room is required: a standalone shift cannot be saved
without one.
After choosing the craft, the functions of the craft appear first, each
with a counter (e.g. Mitarbeiter: 2, Meister: 1), followed by the
global qualifications — cross-craft attributes such as first aider or
forklift licence that are requested in addition to the functions. These
numbers are the shift's demand: they define the slots, drive the occupancy
display (1/3) and later the reminders about shifts that are not fully
staffed.
Project: link the shift to a project so it appears on the project's
shifts tab and in project-based views. Tiles of the recently opened
projects speed up the selection; if the shift lies outside the project
period, the dialog says so. A project change is visible in the duty
roster immediately.
Shift group: optionally group related shifts (groups are managed in
the shift settings and can be shown as tags in the grid).
Note for this shift (optional): a free-text description shown in the grid when
Show description is enabled.
Save creates the shift; it appears immediately as a card in the
corresponding cell. Required fields are craft, room, start and end time and
the break. If something is missing, the save button is disabled and names
the missing fields next to it ("Missing: …"). Server errors are shown in the
dialog. In the edit view, the red button Delete shift deletes the shift.
If the shift is already committed, the bottom of the dialog shows the note
This shift is already committed. with the button Canceling a fixed
term, which lifts the commitment (permission Commit duty rosters).
Later changes to time, craft, demand, description or staffing are recorded
in the shift history. If the shift is already committed, they additionally
appear in the
change list.
The shift history of this shift opens via the Shift history button at
the top right as an embedded window; clicking beside it closes only the history, not the
dialog. The explanatory box on how a shift is built lives in the
help panel of the duty
roster.
In all break fields — shift, individual time, series, shift templates and
time presets — Artwork fills an empty break automatically with the legal
minimum: 30 minutes for more than 6 hours, 45 minutes for more than
9 hours of working time. Below the field you see whether the value is
automatic or manual:
Break automatically filled according to the Working Hours Act (30 min)
— the value follows the entered time.
Manual (20 min, legally 30 min) — you entered a value yourself. Manual
values are never silently overwritten; a reset button restores the legal
minimum. If the value is below the minimum, the hint appears in a warning
colour.
The thresholds are strict: at exactly 6 hours no break is required, at
exactly 9 hours 30 minutes are enough. For shifts across midnight, artwork
calculates up to the end on the following day. As long as you have not
changed the break yourself, it follows the times in both directions: if you
shorten the shift, the automatically set break goes down as well.
The protection of manual values applies to what you type in the open
window. A value below the minimum that does not come from input in this
window is raised to the minimum instead. This affects the break from a
shift template or time preset, and also a saved shift with a shorter break
that you open again for editing. If the shorter break should stay, enter it
once more before saving. A break below the minimum does not prevent saving.
Besides the plus icon on a cell, shifts can be created:
On an event: from the event in the calendar or the project's shifts
tab. Event shifts appear inside the event's card in the duty roster and
inherit its date.
In bulk: with the Edit (pencil) switch in the function bar, select
several room/day cells and add the same shift to all of them at once
(also with a shift template from the template quick select). The same
mode deletes in bulk.
In the daily view: every room section has its own "Add appointment" /
"Add shift" buttons.
On a series event: shifts on a recurring event count as repeat
shifts. When you drag a person onto such a shift, the window Shift
staffing period asks whether the assignment applies For this day
only or On this and other days (with period and weekday). On this
and other days with Every day is preselected. Artwork then assigns
the person to the corresponding shifts of the series in the chosen
period. Shifts in which the function is missing or already fully staffed
are skipped.
You create several shifts at once with the icon Add Shift based on
templates that appears when you hover over a room/day cell. It opens the
window Add Shifts by Presets and Groups for exactly this room and day.
In the tabs Groups and Single presets you select what should be
created. Groups and single templates can be combined; templates selected
twice are created only once. The selection previews times, crafts and
function demand of the templates; optionally a project can be assigned.
This suits recurring weekly plans and standard event days.
Add shifts creates the shifts immediately, without opening the shift
dialog: as standalone, uncommitted shifts in this room, with times, break,
craft, description and function demand of the template. If a template's
end time is not after its start time, the shift ends on the following day.
A template without any functions gets one slot of the function
Mitarbeiter, provided an available function with this name exists.
Templates without valid times or without a craft are skipped. You make
adjustments on the individual shift afterwards.
Only templates of crafts you are allowed to plan are offered. A template
group only appears if this holds for all of its templates; if a group is
missing from the selection, this is usually the reason. You reach the same
window in the daily view via the icon next to Add Shift.
In multi-edit mode (pencil in the function bar), select the room/day cells
first and then click Create. The shift dialog opens; the shift you
enter there is created in every selected cell. Via the template quick
select you can apply a single shift template. Template groups are not
available in multi-edit mode.
Existing shifts are duplicated in the
list view: select several
shifts via multi-select there and click Duplicate. Review rooms and
times after copying.
In the shift settings (tabs Shift templates and Template groups) you
manage reusable shift definitions — each with times, break, craft,
description and function demand. Templates can be bundled into template
groups so a standard day of a certain production type is applied in one
action. Timeline presets, reusable production schedules (get-in,
soundcheck, doors, show …) that can be imported into an event, are not
part of the shift settings. You find them in the
event settings.
Templates, time presets and shift groups are administered in
Shift Settings — the shift dialog only
consumes them.
A standalone shift needs neither an event nor a project, but always a room:
the Room field is required in the shift dialog ("A room is required.").
For duties without an event room, such as office hours or standby, pick a
suitable room of your house. The room must carry the property Relevant for
disposition, otherwise it does not appear in the duty roster (see
Rooms, areas & booking access). The
project stays optional. Filters and project
mode determine the context in which the shift is shown.
Working time without any room is not modelled as a shift but as an
individual time.
A day service only marks a
person's day; it has no times of day and does not count as working time.
Shift Plan
Assigning Staff
Fill shifts by drag & drop, conflict check, find replacement, warnings and overbooking
In the week view, staffing happens by drag & drop: grab a worker from
the workforce panel at the bottom and drop them onto a shift card in the
grid. In the daily view, in a project's shifts tab and in the list view
(with Detailed function overview per shift) you instead click a slot
labelled Unoccupied and pick the person from the list.
A standalone shift card shows the craft abbreviation, the time and the
occupancy — here TO 10:00 – 18:00 (1/3): one of three slots is filled. The
status dot summarizes staffing at a glance:
Dot
Meaning
red
Nobody assigned yet, or overbooked (more people assigned than slots planned)
orange
Partially staffed
green
Fully staffed
If an assigned person is not (or no longer) available that day, a warning
triangle replaces the dot: red for committed shifts, otherwise orange. The
tooltip names the affected people.
With the display setting Show qualifications enabled, the card additionally
lists each function with its own filled/required counter, so you see
exactly which slot is still open. At a reduced zoom the card becomes a
compact pill with time, abbreviation and staffing; the pill is a full drop
target as well.
Three types of workers appear in the workforce panel — internal employees,
freelancers (dashed border) and service providers. To be assignable to
a shift, a worker must:
be marked as "May be assigned to shifts" in their profile,
be assigned to the shift's craft (or the craft must be universally
applicable),
hold a function for which the shift still has an open slot.
And you, the planner, must be allowed to plan the shift's craft: each craft
is either assignable by all planners or restricted to a list of planners.
This applies to employees, freelancers and service providers alike (see
Shift Settings).
People with a
project assignment or project wish
for the shift's project are suggested at the very top with priority and
marked accordingly.
Drag the worker onto the shift card. If exactly one matching slot is open,
the worker is assigned immediately. If several of the worker's functions are
open, Artwork asks which function to fill:
The Select qualification dialog offers a button Use as … for each
matching function. If overbooking is allowed, functions that
are already fully staffed are listed as well, with a dashed border and the
suffix (Overbook). Artwork then always asks, even if only one regular slot
is open.
The Assign function dialog, by contrast, appears in the multi-edit mode
of the workforce panel (pencil switch), when you tick a shift for a person
and several functions are possible. Its subtitle names "Shift 1/1", date,
room and time. Fully staffed functions carry the note Place already fully
staffed there; a tooltip explains that the person counts in addition to
the planned places. Skip assignment closes the dialog without assigning
the person.
After the assignment a success message confirms it, the card updates its
counters, the worker's day cell in the workforce panel shows the new shift,
and their weekly hour balance adjusts. For repeat shifts (shifts on a
series event) the window Shift staffing period additionally asks
whether the assignment applies For this day only or On this and other
days; for the second option you enter the period and weekday.
Assigned people can be removed again via the shift or their day modal
(trash button). For a whole day, planners can review all of a person's
assignments together and remove them if needed. Who made which change stays
traceable in the shift history.
After the drop and, if needed, the function choice, Artwork checks time
overlaps with the person's other assignments and their absences on the
days of the shift. If there are hits, the window Conflicts when
assigning appears with the list of conflicts and the button Assign
anyway; the conflict is then marked on the shift. Cancel discards the
assignment. Without hits, the assignment continues without interruption.
The list names Overlaps with another shift, Vacation (day status
Work-free day), Free day (day status Free) and Not available.
An unavailability with times only counts if it overlaps the shift time.
The window does not check working-time rules; rule violations only arise
after the assignment. For repeat shifts, only the shift you dropped the
person on is checked. The same check runs when assigning via Unoccupied
(daily view, shifts tab, list view), but not in the multi-edit mode of the
workforce panel.
Why some drops are rejected
A drop is refused with a message when the worker cannot be assigned to
this craft, holds no function the shift asks for, no matching slot is
open any more (and overbooking is not allowed), or the worker is already
in this shift. This keeps the plan consistent. Check the worker's day row
or the shift's function counters to see what's blocking. If you are not
allowed to plan the shift's craft, you instead see "Saving failed"
together with "You are not allowed to perform this action." Without the
permission Plan shifts, the shift card does not react to the drop at
all.
If a scheduled person has declined their shift, the assignment in the
shift card shows a red decline icon (tooltip with the person's comment) and
next to it a replacement icon with the tooltip Find replacement for …, in the week view as well as in the daily
view. The window Find replacement for … lists up to 30 suitable free
people of the craft (or of a universally applicable craft) with the
function of the slot, sorted by hour account, with hints such as "Already
has a shift today: …"; a search field narrows the list. Suggested are
internal employees and freelancers who are neither on vacation nor
unavailable that day and have no overlapping shift; service providers do
not appear here. You only see the hour values with the permission View
hour accounts. Assign and the following confirmation swap the
assignment in one step. As with every assignment, both people are notified
only if the shift is committed. If nobody suitable is free, you can still
staff the shift by drag & drop.
Availability — workers maintain availabilities and vacations; assigning
someone who is absent flags a conflict on the shift. For committed
shifts, the scheduled person also receives the notification "Conflict
with your shift".
Overlapping shifts — collisions with the worker's other shifts are
detected across rooms and projects.
Working-time rules — configurable rules (rest periods between shifts,
maximum working hours, minimum breaks, night work …) produce rule
violations that planners review, resolve or deliberately ignore with a
reason. Whoever schedules another person with too short a rest period
gets the notice "Person scheduled with too short a rest period". Rules and
open violations are managed under
Rules & Violations;
substitute days off can be granted from there when extra work is paid
back in time off.
Hard restrictions and warnings are different. A missing function or a slot
that is no longer open blocks the assignment. A working-time rule may
instead — depending on its configuration — create a reviewable violation
that an authorised person ignores with a reason or handles through a
substitute day off. Justified exceptions remain possible and documented.
The day cell shows a person's day status: Available,
Work-free day, Free or Not available, in the language of the
interface Coming with the next update. With the permission Plan shifts you change
the status in the day modal (click the day cell) under Availability
status for this day; without this permission the status is read-only
there. If you set Free or Not available on a day on which the person
has shifts or individual times, the window Change availability status
asks whether the person should be removed from all shifts of that day and
their individual times deleted. It lists the affected entries, including
committed shifts. Yes, remove clears them, No, only change status
keeps them. For Work-free day this question does not appear. Changes
to availabilities are mirrored immediately in the workforce panel of all
open duty roster windows. What the four statuses mean and how they affect
the hour account is explained under
Opening a person and a day in detail.
A status change never removes a shift automatically, not even a
committed one. If a person stays assigned despite a status other than
Available (for example after calling in sick), Artwork points it out:
with a warning triangle on the shift card at the top of the duty roster, an
outlined day cell with a warning triangle in the workforce panel, and an
outline around the person in the project's shifts tab. On the shift card
and in the day cell, red stands for a committed shift; otherwise the mark
is orange. The tooltip reads Assigned but not available, for committed
shifts with the addition (committed shift). This way the shift can be
consciously restaffed.
Individual times have a title, start, end and break or apply all day.
Series can represent regular office hours or training for several people.
Day services are all-day organisational markers such as standby or
office duty. They are set directly on the day cell and have no start and
end time of their own. In the workforce panel they appear as a coloured
ball with icon.
Both give planners a fuller picture before another shift is assigned.
If the toggle Allow overbooking is enabled in the
shift settings, more
people may be assigned than required. The card's status dot then turns red, and the
additional people are marked as Overbooked; they count in addition to the
regular places.
Otherwise, full shifts reject further drops.
The lightbulb switch in the workforce panel activates highlight mode:
click a shift and all workers assigned to it light up in the panel (and vice
versa). In large plans, the fastest way to see who belongs to what.
In the compact view the workforce panel needs less height. Together with
the people filter, sorting and collapsed crafts, even a large workforce can
be reduced to the people currently needed.
Shift Plan
My operational plan & working time
Review your duties, accept or decline shifts, maintain individual working times, and request corrections
My operational plan is each employee's view of planned and recorded
working time. It includes more than shifts: individual working times,
availability, leave, day services, substitute days off, your own key figures,
and working-time change requests all form part of the personal plan.
Open Shift plan → My operational plan to see your own duties for the
selected period (permission View own roster). Committed shifts
are the binding planning state; uncommitted entries may still change.
Your organisation can decide that uncommitted shifts do not appear in your
own operational plan at all (shift setting
Uncommitted shifts in own roster).
You then see a shift only once the week has been committed, unless you hold
the permission View own uncommitted shifts.
Above the week overview you see the totals for the selected period, for
example Work 32:00 h · Break 2:30 h; each calendar week shows its own
totals. Below that is the line Planned … h · Target … h. The target
comes from the work time pattern valid in the selected period; special days
reduce the target, vacation and sick days are target-neutral. If no work time
pattern is stored for you, the target shows "–" together with the badge
Work time pattern missing. Contact HR in that case: without a pattern
neither target nor hours account can be calculated (see
Profiles & work data).
The function bar also offers Subscribe to shift calendar (see
Calendar subscription), My key figures, and
the PDF export Export shift plan as PDF. The shift history is only shown
to people with the permission View duty rosters.
Each shift appears as a card with date, start, end and break, room,
project and related event, craft and your function in the shift, the
planners' description, and the colleagues in the same shift. If your
personal time differs from the shift time, the card shows your time and
below it the note individual user time, original shift time: … - ….
Also check the badges on the card:
Badge
Meaning
Provisional (dashed border)
The shift is not committed yet and may still change
Time changed – please confirm again
The time was changed after you accepted; your acceptance was reset
Time change requested
Your working-time change request for this shift is still open
If you are scheduled on a day that carries an absence entry, the day header
shows a warning triangle: yellow for an absence, red if the day status is
not available or the shift is already committed. The hover text reads
Not available despite shift and names the status. Clarify such days with
the planners. Your own rule violations are also shown as a warning triangle
on the day, in the rule's warning colour; violations already processed
additionally carry a check mark.
Accepting and declining is an opt-in per person. You only see the buttons
Accept shift and Decline shift when two conditions are met:
Shift confirmation by employees is enabled in the
shift settings.
Your account has the permission Accept or decline shifts (Shift plan
module, see
Roles & permissions).
The permission must be granted once
The permission Accept or decline shifts is not part of any role
template. Organisations with shift confirmation enabled must grant it to
each person; until then they see no accept/decline buttons. External
people (freelancers and service providers) do not take part in the
accept/decline flow.
How the flow works:
Unanswered assignments show the status Requested – no reply yet
(blue). After your reply the card shows Accepted on … (green) or
Declined on … (red).
You can accept or decline provisional shifts as well. Optionally add
a comment as Reply to planner.
Declining does not remove you from the shift. After every reply a notice
reminds you: you remain scheduled until the plan is changed. Whoever
assigned you is notified of acceptances and declines.
You can change your reply at any time: after accepting, the card offers
Decline shift, after declining Accept shift.
If the planners change the time of an accepted shift, the acceptance is
reset and the card shows Time changed – please confirm again.
Planners see your status as a coloured pill in the staff panel of the duty
roster and in a person's day dialog, and can record the reply on your
behalf there, for example after a phone call.
My key figures opens the key-figure window for yourself, read-only. The
tabs Season-related data, Substitute days off, Vacation,
Actual hours (with month navigation), Overtime, and Rule
violations show the same values planners see in the key-figure window;
Rule violations lists your own open violations, which planners process
in the duty roster. If no season is configured, the window uses the current
calendar year. What the individual key figures mean is explained under
Profiles & work data.
With Enter project wish (heart icon in the day header) you enter
yourself, non-bindingly, as a wish for a project, for individual days or the
entire project period. The icon only appears if
project assignments
are activated in the shift settings. Planners see
the wish in the duty roster and when staffing shifts and can turn it into a
binding
project assignment
with one click. No wish is possible on days with a registered absence.
You withdraw your own wish on the day via the small cross Remove wish for
this day. If you enter an absence later, it dissolves the wishes in that
period; the dialog names the affected days beforehand.
With the permission Subscribe to roster calendar, Subscribe to shift
calendar sets up a personal calendar feed. It contains your committed
shifts as well as individual times and day services; function and break are
listed in the description of each entry. If your organisation shows all
shifts in the subscription, uncommitted shifts also appear with the prefix
[vorläufig]. They may still change.
If the subscription link was shared unintentionally, Renew link
invalidates the old link immediately; re-subscribe with the new link
afterwards. Period, crafts, and reminders of the feed are explained under
Exports & calendar subscription.
Planners open a person's day directly from the staff panel. The day dialog
combines all information for that day:
planned shifts with accept/decline status,
individual working times and project assignments,
day status (Available, Work-free day, Not available or
Free) and absences,
day services,
detected rule violations,
granted substitute days off,
day comment and change requests.
This shows whether an apparently free time is actually available. A person
may have no shift but already be tied up by leave, an individual working
time, or a substitute day off.
An individual working time records work that is not planned as a shift,
such as office work, preparation, a meeting, or a recurring internal task.
It can be all day or have start, end, and break times.
Artwork applies the configured break rules when saving. Still verify start,
end, and break: individual times count towards the target/actual
calculation, the hours account, and the checks for rest and maximum working
time (see
Rules & violations).
Multi-day individual times are counted once per day.
With the permission Enter own individual times you enter individual times
for yourself:
In My operational plan, click the clock icon Enter individual time in the header of the desired day.
Enter a Title and either tick Full day or enter start, end and break. An empty break is prefilled according to the Working Hours Act.
Save. For regular times choose Enter as recurring series instead.
The entry applies immediately; nobody has to approve it individually. If
your venue uses the approval workflow, the time is still submitted with the
weekly request of the craft, see
The approval workflow.
While the request is open, the time carries the badge In release
request, afterwards Released. You can change it in both cases: during
the request the reviewers see your change, for a released time it has to be
acknowledged afterwards.
You can also edit and
delete your own times in the operational plan. This works only for today and
future days: past days stay reserved for people with Manage availability of
others or Plan shifts. Without one of these permissions the clock icon is
missing; the planners then enter the times.
For recurring tasks you can create a series. Planners open the dialog
Recurring individual times via the button Create individual time
series in the workforce panel of the duty roster. A series contains:
a title (optional),
start and end date of the series period, at most 731 days, roughly two
years,
all day or start and end,
break,
weekly recurrence with Interval (1 = every week, 2 = every 2 weeks)
and Weekdays,
one or more people: users, freelancers or service providers. A series you
create for yourself only applies to you.
Editing a series updates its entries. The change applies to all people in
the series. If you remove a person from the series, they keep the times
already created for them.
Delete series deliberately
Deleting a series also removes its associated individual working times.
Check the period and people involved first.
Availability tells planners when a person can be assigned. Absences such as
leave show periods where no assignment should be made. If availability is
changed after shifts or individual times already exist, Artwork warns about
the conflict and, depending on permission and situation, may offer to
remove the affected entries.
If a person is scheduled despite an absence or the day status not
available, the conflict notice names the person who actually made the
assignment and the time Assignment made on …, both in the notification
and in the absence list in the profile.
Availability does not replace a shift: it only says whether a person can
generally be scheduled. The actual working time is created by a shift or an
individual working time.
People enter wishes and absences for themselves in the operational
plan. The day status is not available there: planners maintain it in the
person's day dialog (permission Plan shifts or Manage availability of
others). The picker shows its four values in the language of the
interface Coming with the next update, and they affect the hours account
differently:
Day status
Effect on the hours account
Available
None. It removes a previously set day status
Work-free day
Like leave: the daily target counts as met. Work done anyway counts on top
Not available
Like sickness: the daily target counts as met. A shift still entered on that day does not count as working time
Free
None. The day counts as a full or half day off (morning or afternoon) in the key figures
You create your own entries in the Availability area below My
operational plan via New entry; no separate permission is needed:
Type Available or Absent. An absence you enter yourself
corresponds to the day status Not available, in the hours account
too; with a time instead of all day it counts as half a day. You do not
choose a leave type here.
From and To: for a period, one entry is created per day.
All day or with a start and end time on the same day.
A single day can be created as a series with Repeat weekly and Ends
on. Period and weekly repetition are mutually exclusive.
Note (optional), at most 100 characters.
You can change and delete your own entries later. Entries of other internal
people can only be maintained with the permission Manage availability of
others; the area and its fields are described under
Operational plan, availability, and absence.
A day service is an all-day marker such as standby, office duty, or an
organisational responsibility. It has no start and end time and is therefore
not the same as a shift. Day services are configured centrally and then
assigned on a person's day.
If the displayed time differs from the work performed, do not correct it
silently via a comment. Use a working-time change request. The request
compares the current state (date, start, end, room, craft, and responsible
people) with the requested new start and end. A comment explains the
reason. You can only submit a request for your own shifts.
Choose Request work time change on the operational plan card.
Enter the new start and end and briefly explain the difference.
Submit the request. The existing duty remains until it is reviewed; the card shows Time change requested.
Track the status under Shift plan → Work time change requests in the tab My work schedule adjustment requests. The list can be filtered by Status and period (From / To). While a request is pending you can withdraw it there with Delete request.
After the decision, verify that working time and hours account were updated correctly.
A request's status is Pending, Approved, or Rejected. Planners
(permission Plan shifts) process incoming requests on the same page in the
tab Work time adjustment requests received. It lists the requests of the
crafts they are registered for as planner and of the crafts that can be
scheduled by all shift planners. Approve applies the new time, Decline
opens a dialog for a Decline Message; it is optional. The Rejection
Reason is shown in your request; without a message it says that no reason
was given. This keeps it traceable what was originally planned, what change
was requested, and how it was decided.
With the permission View staff info data, planners open a person's Key
figures window via the info button in the staff panel. It is the same
window as My key figures, but for other people. Working times and
overtime of others additionally require the permission View hour accounts:
Tab
Contents
Season-related data
Target values from the person's contracts valid in the respective period, pro rata after a contract change Coming with the next update, and the current status, such as free Sundays or full free days per season half
Substitute days off
Open entitlements and granted substitute days off
Vacation
Entitlement, granted days, remaining entitlement, and individual vacation periods
Actual hours
Actual, target and balance per month with month navigation
Overtime
Current overtime balance and processed or paid-out time
The tabs Actual hours and Overtime only exist while
work time accounting
is switched on. If past days differ from the time account, for example after
a later sick note or a changed shift time, the Actual hours tab shows a
notice with the difference. Artwork does not rebook such days
automatically; Rebook in the work times in the person's profile does
that.
The visible values depend on the contract valid on the respective day, the
permissions, and the selected period. If target or remaining figures look
unexpected, first check the timeline under
Contract & working hours.
The counting rules of the individual key figures are described under
Key figures.
If the person's contract has an active overtime rule and you have the
permission Pay out overtime, overtime can be documented as paid out in the
Overtime tab. Record hours, minutes, and a comment. The entry appears in
the overtime history and changes the open balance.
Only overtime whose compensation period from the contract has expired can be
paid out, and at most the positive balance of the time account. The
section Pay out overtime only appears in the tab while something is
currently payable, and it names the maximum. If the overtime rule is
active in the contract but no compensation period is stored, overtime has no
deadline and never becomes payable. The booking only reduces the time
account; the actual payment happens outside Artwork.
A payout is not a change to individual shifts. Correct incorrect working
times first; only the remaining balance should be paid out afterwards.
Check new or changed shifts for date, time, break, and function.
Note the commitment status and, if enabled, accept or decline shifts.
Compare leave, availability, and individual times; clarify warning
triangles on days.
Report discrepancies through a change request.
After correction, recheck the hours account and, where relevant,
overtime under My key figures.
Shift Plan
Rules & violations and substitute days off
Create working-time rules, detect and process violations in the duty roster, and document substitute days off
Artwork checks shifts and individual working times against the
working-time rules defined in your organisation. The markers support
planning but do not replace a professional or legal assessment. Which rule
applies to a person follows from the contract assigned to them on the
respective day.
Rules are maintained under System → Shift settings → Rules & violations
(called "Shift warnings" up to version 1.7.6). Detected violations are
collected in the Open violations tab; the resulting entitlements are
tracked in the Compensation days overview in the Shift plan menu.
Both tabs require the permissions Shift settings and Plan shifts; in
granular mode additionally
View shift rules or Edit shift rules. Editing, ignoring and resolving
violations as well as the compensation days overview require Plan shifts.
Free label as shown in the duty roster and in violations
Description
Explanation of the rule, a required field in the dialog. The text later appears in the Edit rule violation dialog below the rule name
Rule type
What is checked (see Rule types). The type cannot be changed after the rule has been created
Value
Threshold in the unit of the type: hours, days, count, or time of day. The weekly average adds Period (weeks); some types need no value or take it from the contract
Warning colour
Colour of the marker in the duty roster
Default substitute days off and Default compensation deadline (days)
Defaults proposed when processing a violation. The deadline counts in days from the date of the violation. If the rule has no deadline, Artwork proposes the deadline from the person's contract (see Editing a violation)
Notify on rule violation
People notified about new violations. Only people with the permission View duty rosters or Plan shifts and artwork admins can be selected. Anyone who no longer has one of these permissions receives no message and drops off the list the next time the rule is saved
Assign contracts
Searchable multi-select of the contract templates the rule applies to
Without a contract the rule checks nobody
A rule without assigned contracts applies to nobody. Only people who have
one of the assigned contracts in their profile are checked.
Above the rule list, the toggle By rule / By contract switches the view.
By rule shows the rule list. By contract lists the contract
templates with the columns Active for (people with this contract) and
Assigned rules; via Edit rule assignment you tick the rules that
apply to everyone with this contract. Changes to rules or contracts
immediately trigger a re-check of the affected people; nothing needs to be
started manually.
When you delete a rule, Artwork removes its active, automatically detected
violations. Processed, ignored and manually recorded violations are kept as
history.
The button Create legal default rules creates the rule set according to
the German Working Hours Act (ArbZG) in one step and assigns it to the
selected contract templates:
daily maximum 10 h,
weekly maximum 48 h,
rest time 11 h,
at most 6 consecutive working days,
work on Sunday with replacement rest day (default: 1 substitute day off
within 14 days),
work on special days with replacement rest day (default: 1 substitute day
off within 56 days),
15 free Sundays per calendar year,
weekly average 48 h over 24 weeks,
night work maximum 8 h.
In the dialog all rules and all contract templates are preselected. Under
Rules to create you tick or untick the rules, choose the contracts and
confirm with Create selected rules. If a rule with the same type and
the same value already exists (for the weekly average also the same
period), it is only assigned to the contracts still missing and not created
twice; a deactivated rule is reactivated in the process. A rule of the same
type with a different value, for example a daily maximum of 9 h, does not
count as existing: the default rule is then created in addition. The
created rules are ordinary rules afterwards: name, values, colour, and
assignment can be adjusted.
Check the default values
The default rules reflect the Working Hours Act. If a collective agreement
or works agreement with different thresholds applies in your organisation,
adjust the values after creating them.
Total planned working time of a person per day (shifts plus individual times)
Weekly maximum of hours
Total planned working time per week (Monday to Sunday, shifts plus individual times)
Maximum consecutive working days
Number of working days without a day off in between. Every day with a shift or an individual time counts as a working day
Rest time before a working day
Interval between the end of work on the previous day and the first start of work on a working day (neither Sunday nor special day), plus the gap between two assignments on the same day
Rest time before a Sunday or special day
The same check when the day on which work starts is a Sunday or special day
Rest time between shift groups
Minimum interval between consecutive shifts of different shift groups that start on the same day. Shifts without a shift group are left out
Work on Sunday
Creates a violation for every Sunday with a shift, documenting the entitlement to a replacement rest day (no value required)
Work on special day
Like work on Sunday, for public holidays flagged as special day with the contract switch active
Minimum free Sundays per calendar year
Whether the person can still reach the minimum number of free Sundays in the year; empty = legal default of 15
Average weekly hours over a compensation period
Rolling average of planned weekly hours over the last n weeks (Period (weeks))
Daily maximum on days with night work
Maximum working time on days with at least 2 hours within the night window of the shift settings; empty = 8 hours
Minimum whole free days per week
Whole free days per calendar week; empty = "free whole days per week" from the contract
Overtime reduction deadline
Warns before open overtime exceeds its reduction deadline; applies to contracts with the overtime rule active
Minimum free Sundays with Saturday/Monday per season half
Whether the target of free Sundays with a free Saturday or Monday per season half is still reachable; empty = target from the contract
Conflict: half day off / shift
Whether a shift collides with a half day off; the value is the time-of-day threshold
No half day off on special days
Reports a half compensation day that was granted on a special day. Granting it remains possible; the dialog points out the rule beforehand
Minimum days before binding commitment
Reports the person's shifts that start within the configured number of days from today and are not yet committed
The hint below each rule type in the interface explains how to read the
value. Some rules create violations without a shift, for example on the
last Sunday of the year when the free Sundays are no longer reachable, or on
the deadline day of the overtime reduction deadline.
Automatically detected violations have the severity Warning. They only
become an Error for four rule types, once nothing can be changed any
more: free Sundays per calendar year after the end of the year, free days
per week after the week has passed, free Sundays per season half after its
end, and the overtime reduction deadline after the deadline day. The
follow-up violation for an expired compensation-day deadline is an error
as well.
Details people stumble over in daily work:
Work on Sunday counts the day on which the shift starts. A shift from
Saturday evening to Sunday morning therefore creates no violation.
Individual times on a Sunday do not trigger the rule.
Rest time: the comparison only looks at the directly preceding
calendar day; individual times count as work. Two assignments on the same
day with a gap shorter than the rest time also create a violation on the
later shift, for example with split duties. If you plan split duties, a
rest time of 11 hours therefore produces violations regularly.
Weekly maximum: once the limit is exceeded, every further working day
of that week gets a violation, not only the first one.
Maximum consecutive working days: the violation is created on every
day above the limit on which the person has a shift. Days with only an
individual time extend the streak but carry no violation.
Minimum days before binding commitment: once the shift is committed,
the next automatic check removes the violation.
Conflict: half day off / shift: with a morning off the shift must
start at the configured time at the earliest, with an afternoon off it
must end by then at the latest.
Overtime reduction deadline: the value is the number of days before
the deadline from which a warning is created. After the deadline the
warning becomes an error.
Minimum whole free days per week: the week runs from Monday to Sunday.
A day is free if it has neither a shift nor an individual time; shifts
past midnight occupy both days. The violation appears on the Sunday of the
week. If the contract says 0, the rule does not apply to that person.
Average weekly hours: one violation is created per week, on the last
shift of that week. Weeks whose period has less than half of its weeks
planned are not reported.
Minimum free Sundays with Saturday/Monday per season half uses the
season from the tool settings. If none is stored there, Artwork falls
back to the current calendar year; the hint text on the rule type says so
as well Coming with the next update. The violation sits on the last Sunday of the half; a half that
has not started yet is not evaluated.
All checks use the person's individual shift times. If a person has
deviating times in a shift, their own time counts.
Daily and weekly maximum count shifts and individual times; violations
are also reported without a shift when individual times alone exceed the
limit.
The night-work rule evaluates shifts past midnight as a whole.
Breaks are applied according to the break rules, including the 9-hour
threshold.
Special days only count if the public holiday carries the flag Treat as
special day. The rule Work on special day additionally requires
Special day rule active in the person's contract
(see Public holidays and special days).
People without a contract are not checked.
When the check runs: as soon as you assign, remove or replace people,
change shift times, delete shifts or change rules and contracts, Artwork
checks the affected people. In addition, a check over the next 14 days runs
every five minutes. A violation caused by an individual time alone appears
with the next of these checks; if the day lies further in the future, at
the latest when it moves into the 14-day window.
Violations disappear on their own as soon as the conflict is resolved by
changes to shifts or individual times and the next check has run.
Processed, ignored, and manually recorded violations are kept, as are
follow-up violations for an expired deadline (see
Substitute days off).
Rules are assigned to contract templates, and a person's contract has a
validity period. Two people in the same shift may therefore receive
different markers. If an expected marker is missing, check:
Is the rule assigned to the correct contract template?
Was a contract with this template valid on the relevant day (timeline
under
Contract & working hours)?
Coming with the next update Daily rules such as daily maximum, rest times,
weekly maximum, consecutive days, weekly average, night work, and work on
Sundays and special days follow the contract of the day the violation is
booked on. Rules over a period (free days per week, free Sundays per
season half and per calendar year) follow the last day in the counted
period on which a contract applies, even if that contract ends before the
booking day. The overtime reduction deadline follows the contract the
overtime comes from; the warning continues after someone leaves. No rules
apply on days without a contract.
Are all shifts, breaks, and individual working times complete?
For special-day rules: does the holiday carry the special-day flag? For
Work on special day also: is the special day rule active in the
contract?
While assigning staff, Artwork surfaces conflicts as early as possible.
Besides working-time rules this includes overlaps, missing qualifications,
absences, or multiple assignments. Depending on configuration, planners may
still continue. That only means the action is technically possible, not
that the conflict is resolved.
In the duty roster the person cell shows rule violations with two markers:
a warning triangle in the rule's warning colour; from two open
violations on that day the number is shown next to it,
a check chip with the number of violations already processed.
Ignored violations are not shown in the cell. The tooltip names rule,
status, and measured value, for example "17 h of max. 10 h"; a click opens
the person's day. The legend is in the duty roster's help panel. Employees
also see their own open violations in
My operational plan.
The Open violations tab under System → Shift settings lists all
violations with person, date, rule, severity, status, and measured value.
Use the filters to narrow the list:
Period (From / To): at most one year; longer periods are cut with
a notice; without a period all violations of the selected status are
listed,
Crafts, Person, and Rule,
Severity (Warning / Error) and Status (Active / Processed /
Ignored / All statuses). Active is preselected, so the list initially
shows only open violations,
Sort (Newest first / Oldest first).
The chips above the list count the active violations in total and
separately as Errors and Warnings; long lists are paginated.
Export as Excel outputs the filtered list; without a period Artwork
exports the current month. An export covers at most one year.
Each active violation offers three actions:
Action
Effect
Edit
Opens the dialog in which you set substitute days off and the deadline (see Editing a violation). The days are credited to the person's account
Resolve
Marks the violation as done, without further consequences and without substitute days off
Ignore
Discards the violation with a reason (required, at most 500 characters) that remains visible on the violation
Resolve cannot be undone: for a resolved violation the dialog no longer
offers to book substitute days off. Choose Edit if an entitlement is
meant to arise. You can still open an already processed violation via
Edit to see details and history.
Several selected active violations can be ignored together with one
reason, at most 200 at once.
A case Artwork does not detect automatically is recorded in the duty roster:
open the person's day in the workforce panel and choose Add rule
violation. Choose a rule or Other (without rule) with your own title
(at most 120 characters) and enter date, severity, and reason. The manual
violation then appears in the list like any other.
Ignoring remains a documented decision
An ignored violation disappears from open processing but does not make the
plan compliant with the rule. Use a specific reason so the decision remains
understandable later.
The dialog Edit rule violation shows the details of the violation
(measured values such as planned hours, rest hours, or consecutive days)
and the History tab with all previous steps. When editing you define:
the number of substitute days off in half steps (0.5; 1; 1.5 …). The
rule's default is prefilled, otherwise half a day. 1.5 days become one
whole and one half entitlement,
the deadline by which the substitute day off must be granted. It is
required and must lie in the future. The hint Default according to
rule: n days or Default according to contract applies the stored
default. The default from the contract is only offered when you open the
violation from the person's day in the duty roster or from their profile;
in the Open violations tab the field stays empty if the rule has no
deadline,
a reason (optional),
whether it is a Compensation day for public holiday, which reduces
the daily target. For violations of the rule Work on special day the
checkbox is preselected.
Saving books immediately
The substitute days off you enter are credited to the person's account
when you save. This is a booking that affects the account, not just a
display.
After saving, the violation carries the note Processed/approved by … on
…. It can be edited again as long as no substitute day off has been
granted; after that the violation is locked. You can also ignore an active
violation directly from this dialog.
Recording the entitlement and granting the actual free period are two
separate steps. The Compensation days overview in the Shift plan
menu (permission Plan shifts) shows Overdue, Open, and Granted
compensation days with counters and Recent activity. The lists can be
filtered by Person, Craft, Deadline from / until, and Status
and are paginated; Export as Excel outputs the filtered list. The same
entitlements appear in the person's profile under
Substitute days off.
Via Grant compensation day you choose the date. A substitute day off can
be granted as a full day or, morning or afternoon, as a half day. Both
turns a half entitlement into a whole day off; for this Artwork uses a
second open half day of the person. For the chosen date, Artwork checks
whether shifts or special day conditions already exist. If there are shifts
on that day, you choose between Remove shifts and grant and Grant
without removing shifts; alternatively pick another day. You can only
remove the shifts if you may plan their crafts. Granted days appear in the
person cell of the duty roster.
Review shifts that are removed
If a substitute day off is granted despite an existing assignment and the
shifts are removed, new staffing gaps may arise. Check the affected shifts
afterwards and inform everyone involved.
A grant can be taken back with Revoke. The entitlement is then open
again and must be scheduled anew; the history remains traceable. Delete
removes an entitlement entirely and requires a Reason for deletion,
which is shown in the recent activity.
If the deadline passes without the day being granted, the entitlement is
listed under Overdue compensation days. In addition, the automatic rule
check creates a new violation with severity error and the measured value
Compensation deadline expired, which refers to the original violation.
This follow-up violation does not disappear on its own. Grant or delete the
overdue entitlement and resolve, ignore or process the follow-up violation.
For the same deadline the check does not create a new follow-up violation
afterwards Coming with the next update. If you process the original violation
again and the new deadline passes, a follow-up violation is created again.
The rules Work on special day, Rest time before a Sunday or special
day, and No half day off on special days, as well as the target
reduction in the hours account, share one definition: a day is a special
day if the public holiday in the
event settings
carries the flag Treat as special day. School holidays without the flag
are never special days. The contract switch Special day rule active
additionally decides whether the rule Work on special day and the target
reduction apply to the person. The other two rules do not evaluate the
switch: they apply to everyone whose contract has the rule assigned. For
No half day off on special days the hint text on the rule type says so
as well Coming with the next update. Work on special day evaluates every
special day in the period separately within a check run, even if an earlier
special day does not count for the person Coming with the next update. Shift planners can maintain the special-day checkboxes on the
holidays page themselves, even without write access to the other settings.
A violation on a special day can be processed as Compensation day for
public holiday; the granted day then reduces the daily target (see
Special days).
Do manual violations have a meaningful title and reason?
Are entitlements to substitute days off and deadlines complete?
Were granted days off checked against existing shifts?
Have post-commitment changes reached the approval workflow?
Shift Plan
Committing & Approval
Making duty rosters binding, the week status, the approval workflow in detail, changes after commitment and notifications
While a plan is in draft, shifts can be changed freely — staff are not
notified yet. Committing makes a period binding:
committed shifts show a lock icon and record who committed them,
assigned internal employees are notified about their final duty roster
(freelancers and service providers receive no notification from Artwork),
later changes to committed shifts are collected in the change list so
nothing goes unnoticed.
Before committing, a short final check pays off: filter for understaffed
shifts, review open slots, check rule violations and absences, and confirm
the right project period and craft. The Week status page
bundles exactly these points for all crafts. Only the selected combination
of calendar week and craft is committed — not automatically the entire
visible roster.
The calendar-check button in the function bar opens the commit dialog
(permission Commit duty rosters). A commit always targets a combination of
calendar week, year and craft — and several crafts can be
selected at once. Sound can be final while lighting is still in progress.
The dialog shows only the crafts you are allowed to commit and names its
mode in the title:
Commit duty roster (without the approval workflow): all shifts of the
selected crafts in that week are committed immediately, and the assigned
internal employees are notified.
Submit duty roster for approval (with the workflow active) — the
dialog explains that the plan is not committed directly but submitted to
the approvers, lists those people and creates one separate request per
craft (button Submit for approval). If no approvers are set up yet,
the dialog says so.
After saving, Artwork reports the result: when committing, with calendar
week and number of crafts; when submitting, whether a request was created,
an existing one was updated or a rejected week was resubmitted (with the
respective counts for several crafts). Server errors are shown visibly.
Calendar week 53 is rejected in years with 52 calendar weeks.
You lift the commitment of a single shift in the shift dialog: clicking the
shift card opens it, and at the bottom the note This shift is already
committed. appears with the button Canceling a fixed term. The shift
is committed again via the commit dialog of the calendar week. With the
approval workflow active, committing directly is locked; shifts are then
committed only via a request. Lifting a commitment stays possible even
then.
In the workforce panel, the calendar-week cell of each person row is
coloured as a status tile according to the state of their craft in that
week; the cell's tooltip names the status:
Status
Colour
Meaning
Requested
blue
An approval request has been submitted and awaits approval
Committed
green
The week is final for this craft
Changed after commit – confirmation pending
yellow
There were subsequent changes nobody has acknowledged yet
The page Shift plan → Week status (permission View duty rosters)
shows a matrix crafts × calendar weeks. Above the matrix you choose the
number of weeks (4, 8, 13 or 26), page in steps of 4 weeks and filter
to individual crafts; Show all crafts clears the filter. Visible are the
crafts you may plan: crafts that all planners may staff and those where you
are entered as a planner. Admins see all crafts.
Each cell carries a status:
Status
Meaning
No shifts
No shifts of this craft in this week
Open
Shifts exist, nothing is committed and no request has been submitted
Requested
An approval request is pending
Partially committed
Some shifts of this week are committed, others are not
Committed
All shifts of this week are committed
Rejected
The last request was rejected and nothing has been resubmitted
The cell also shows how many shifts are committed (committed/total),
unacknowledged changes, open rule violations and open slots /
demand. If individual times belong to an approval request of the week, a
clock counter Individual times released appears as well. A deadline marker refers to the
request deadline of the craft (days
before the week starts): yellow when the deadline is due soon, red when it
is overdue. The row Total per week sums up how many crafts of the week
are committed.
Clicking a cell opens the details with the matching actions: Go to week in
shift plan, Submit request or Commit shift plan (depending on
whether the workflow is active), Go to request, Open rule violations
and Changes.
Venues with a four-eyes principle enable the Duty roster release
workflow toggle in the
shift settings and name
the approvers there. Approvers are not a separate permission but exactly
this list (admins always may). The workflow can only be enabled with at
least one approver. Only with the workflow active do the three workflow
pages appear in the Shift plan menu.
Planners submit instead of committing. "Submit for approval" creates
one approval request per selected craft for the calendar week. All
still-free shifts of that craft in that week are attached to the request and
are now "in the workflow". If an open request already exists for the same
week, submitting again does not create a second one: shifts added since
then are attached to the existing request. Shifts you create after
submitting therefore only belong to it once you submit again. A pending
request can be withdrawn by the person who submitted it and by any approver.
The shifts then become freely editable again.
The individual times of the week go through approval with the request:
those of the craft's people and of everyone assigned to a shift of the
craft in that week. In the personal roster, in the person's day window in
the duty roster and in the review they carry the badge In release
request and, after approval, Released. Each individual time belongs
to one request only; after a rejection or a withdrawal it is free again for
the next one. An individual time can still be edited in both states. While
the request is open, reviewers see the change; once the time is released,
the change or deletion lands under Shift plan Change list and has to be
acknowledged there. The edit dialog points this out in each case. Without
the approval workflow these badges do not exist: committing a week directly
only covers shifts.
Approvers review. The named users are notified and find all requests
under Shift plan → Shift plan Review requests, grouped by craft, with
pending requests plus those recently approved/rejected (older ones can be
loaded). The review shows exactly which shifts, assignments and changes are
included — including rooms and individual shift notes — and the same
rule violations as the duty roster. The violation markers are clickable
and open the edit dialog if you have Plan shifts and Shift settings
(in the fine-grained permission model also Edit shift rules). On the
overview page, To shift plan (current week) jumps into the current
week. Requests can be browsed back and forth directly. The person rows can
be shown or hidden by type (internal employees, freelancers, service
providers), shortened with Only people with entries and sorted.
Approve or reject.
Approve (button Accept) commits all shifts of the request and
releases its individual times, optionally with a note that goes to the
requesting person. Staff are notified just as with a direct commit.
Reject requires at least one reason: global for the whole request, or
on individual selected days or shifts/people. Without a reason the confirm
button stays locked, and the server also refuses the rejection
Coming with the next update: the request stays open and the dialog shows
Please provide at least one reason for the rejection. Important: on rejection the request's shifts are
reset to the state before the request. Changes made to them since
submitting (times, assignments, craft, room …) are lost. The reasons are
stored for the planners. The requesting person is notified, reworks the
plan and resubmits for approval with one click.
Approve, reject and reset are protected against double clicks.
Planners keep track under Shift plan → Requested duty rosters: a
read-only view of their own requests (and those for their crafts) as a flat
list (newest calendar week first, with pages), filterable by status, craft
and Only my requests, with status (Pending / Approved / Rejected),
the stored reasons and the actions Withdraw request and Resubmit for
approval.
Here too, To shift plan (current week) leads directly into planning; in
a rejected request, Go to week in shift plan opens the affected week.
A pending request marks a clear submitted state and makes parallel changes
traceable. If corrections are needed, it is withdrawn or rejected by the
approvers and then submitted again. Additional shifts for the same week and
craft join an existing pending request as soon as you submit the week
again.
So that no week is left unanswered, each craft can have a deadline for
approval requests in days before the week starts (see
Shift Settings → Crafts). When the
deadline is reached without a request having been submitted for the
calendar week, the craft management is notified automatically: once per
calendar week and only if the craft has shifts in that week. If no craft
management is set, the notification goes to the craft's planners. In the
Week status the deadline is visible as a yellow or red
marker.
Change list — changes to committed shifts (times, assignments,
deletions) are collected under Shift plan → Shift plan Change list.
The page is open to approvers only and appears in the menu only while the
approval workflow is active. The list always shows one craft: on first
opening you pick it via Select craft, later via Change craft.
Each change has its own row per affected person with the working time
before and after, Changed by and Changed at; if a shift with
several people changes, there are correspondingly many rows. Changed or
deleted released individual times appear here as well. Approvers
acknowledge a row via Approve afterwards or everything at once via
Approve all open changes; until then the yellow week status tile marks
the week as "changed after commit". Filters: All changes, Open
changes and Approval granted, plus All / Internal / External and
the search field Search affected entity. The bulk acknowledgement
applies to the selected craft with the search and internal/external
selection and asks for confirmation first. The full trail also lives in the
shift history; the list
can be exported to Excel.
Work time change requests: staff can request a different start and
end time for their own shifts. Planners (permission Plan shifts) decide
under Shift plan → Work time change requests in the tab Work time
adjustment requests received. It lists the requests of the crafts in
which they are entered as planner or which all planners may staff; these
people are also notified about a new request. The status Pending is
preselected. Approve does not change the shift but enters the new
time as the person's individual time in that shift. An accept or decline
already given is reset, and for a committed shift the change appears
under Shift plan Change list. Decline works with or without a
reason. The staff side is described in
Requesting a working-time correction.
A later change may be necessary, for example due to sickness, a time shift
or a staff swap. Artwork does not prevent it outright but marks the affected
state and notifies or records the change. The operational plan stays usable
without losing the binding nature of the original approval.
The commitment of an individual shift can also be revoked deliberately
(button Canceling a fixed term in the shift dialog, permission Commit
duty rosters, and only for crafts you may plan). Use this only when the shift truly needs to return to normal editing; for a
small, traceable correction the change list is often the better path.
When the toggle Shift confirmation by employees is active in the
shift settings,
scheduled people with the permission Accept or decline shifts can
accept or decline their shifts in My operational plan — also for
provisional, not yet committed shifts, optionally with a comment. The help
text of the toggle says so as well Coming with the next update. Unanswered assignments show the status
Requested. If the times of the shift change, a reply already given
expires and the roster shows Time changed – please confirm again.
People without the permission are not asked and show no reply status;
freelancers and service providers do not take part in the flow.
The reply is visible directly in the duty roster: in the workforce panel as
a coloured pill on the shift (blue requested, green accepted, red declined)
and in the day modal below each shift (Requested, Accepted on …,
Declined on …, with comment). Planners with Plan shifts can record the
reply on the person's behalf — in the day modal, via the assignment menu
in the daily view or in the person's roster. After a decline, the shift
card offers Find replacement.
The permission must be granted
The permission Accept or decline shifts is not part of any role preset.
Venues with active shift confirmation must grant it to the people once in
the user rights — until then they see no accept/decline buttons.
Export as Excel in the shift history and as second tab in the export dialog of the Rules & Violations page
Excel: Change list
Export button on the Shift plan Change list page
PDF Daily Plan (Project) and Excel Personnel Plan (Project)
Export button on a project's shifts tab
Permission
The exports of the export dialog, the shift history export and the two
project exports require the permission View duty rosters; the craft
distribution additionally View hour accounts. The rule violations
export requires the same permissions as the Open violations tab:
Plan shifts and Shift settings, in
granular mode
additionally View shift rules or Edit shift rules. Plan shifts alone
is not enough: people who only plan process violations on the person's
day in the duty roster, but reach neither the list nor its export. The
change list can only be exported by approvers.
The tab PDF Shift Plan Export is prefilled with your current view: time
period, active filters and project mode are carried over. You can adjust
everything in the dialog before exporting. You choose Heading, Paper
size (A3, A4, A5; the default of the selected view carries the addition
(Standard)Coming with the next update), Paper orientation (landscape is
recommended so a full week fits one page) and resolution (the field is
prefilled with 96 DPI and names this value as the default, maximum 300). The daily view has its own PDF layout.
The tab offers two layouts as tiles:
Rooms by day: the grid as in the duty roster with rooms as rows and
days as columns, each calendar week on its own page. You choose the
period By date or By calendar week; one PDF holds at most six
months. Under Filter you narrow down to rooms, areas, event types and
crafts. A group without a selection does not filter. The craft selection
affects shifts only, events stay visible. Hide empty rooms omits rooms
without events and shifts in the period.
Personnel overview: people as rows, days as columns, the cells
containing shifts (time, room, craft · function, description,
✓ committed or … requested), individual times and day services. You
choose the period By date (with the quick selection Current view,
This week, This month, Next 4 weeks) or By calendar week, up
to 31 days; the Worker types (internal workers, freelancers,
service providers) and the Contents (shifts, individual times, day
services, people without entries). Here the craft selection only filters
the shifts per person; individual times and day services stay visible.
The PDF defaults to A3; only A3 and A4 are offered
Coming with the next update. Each page holds 18 people (A3) or 12 (A4), further people
follow as "Personnel page x/y". The fitting printout for
the question "Who works when?" rather than "What is happening where?".
Under This is how the PDF is structured the dialog previews rows,
columns and cell content. A clear heading and suitable paper format make
the scope of a printed plan explicit.
The tab Excel Work Time Overview only appears with work time accounting
activated. It exports a monthly matrix of target and actual hours per craft.
In the dialog you choose:
the time period in whole months, with the quick selections Last and
this year, Last year, This year, This and next year. The export
range must not exceed 36 months.
This is how the work time overview file is built: every row is a month,
plus total rows per year. Each selected craft has four columns: target and
actual for internal workers, target and actual for external ones. A final
column block sums all crafts. The values are decimal hours. The overview
aggregates per craft and contains no rows for individual people. It is
intended for controlling working times and broader staffing decisions.
Shows how the shift hours of the people of a universally applicable
craft (e.g. trainees) distribute across other crafts, with hours, shares
and totals. Useful for internal cost allocation. In the dialog you choose
the period (at most 36 months), the Universal craft whose people are
analysed, and the crafts to be listed individually. Hours in crafts that
are not selected are summarized as other crafts. If no craft is marked as
universally applicable, the dialog says so. The tab is only visible with
the permission View hour accounts.
Exports the rule violations of the selected period as a list: date, person,
crafts, rule, measured value, severity, status, substitute days off and
processing. On the
Rules & Violations page,
Export as Excel exports immediately with the filters active there. The
export icon next to it opens the dialog, where period, status, severity and
crafts can still be adjusted; it is prefilled with the active filters as
well.
Exports the shift history
— who changed what and when — for shifts starting in the selected period,
with the same filters as the history window. A set person filter is adopted;
the column Relation says per entry why it is included (concerns the
person, person is scheduled in the shift, performed by the person). The
quickest way is Export as Excel directly in the history window: the
export adopts the current selection. The same export is available as a tab
in the export dialog of the Rules & Violations page; there you choose shift
start from/to, craft, search term and Sort by shift day.
Exports the
changes after commitment
as a list: shift, affected person, kind of change, before/after, changed by
and approval status. You reach the export on the Shift plan Change list
page: Export as Excel takes the current filters, the export button next
to it opens the dialog with craft, status, internal/external, person search
and an optional period. The period refers to the date of the change.
Periods for rule violations, shift history and change list
These three exports are limited to one year — the dialog blocks longer
periods, and a server message is shown. Without a date the current month
applies.
PDF Daily Plan (Project): on a project's shifts tab. One day per
page in a compact timeline layout. Privacy mode shortens names (e.g.
"Max M.") and omits contact details and internal notes, also for
freelancers and service providers; this makes the PDF safe to share
externally.
Excel Personnel Plan (Project): also on a project's shifts tab. One
row per shift, grouped by day. Only functions with Is taken into account
for new shifts set in the shift settings get their own column. You can
choose the Number format:
Readable format ("8 Std. 30 min") or Excel number format (decimal
numbers such as 8.5 including totals, ready for calculations).
Substitute days off: the Compensation days overview page exports
its filtered list as Excel (permission Plan shifts).
My operational plan as PDF: the personal roster can be exported as a
monthly overview, one month per page in landscape format; see
Personal Roster & Working Time.
Workers don't need to open Artwork to know when they work: the
calendar-star button sets up a personal ICS calendar feed that phones
and desktop calendars subscribe to (permission Subscribe to roster
calendar). Only people with this permission can create a new subscription
Coming with the next update. An existing subscription keeps delivering even if
the permission is removed later.
The feed can be limited to a time range and to specific crafts, and
optional calendar notifications add reminders for upcoming shifts; you
set the Lead time in minutes, hours or days. The reminder text is in
your language: the name of the entry is followed by, for example, "starts in
30 minutes."
Coming with the next update After subscribing, the
instructions show the Calendar URL to copy and step-by-step guides for
common calendar programs. Alternatively you can download an ICS file
there; it does not update itself and must be re-imported after changes. Since
it is a subscription, committed changes to the roster show up in the worker's
calendar automatically. Entries contain the project and room name, function
and break as well as individual times, and day services are also shown
in the subscription on the corresponding day. Day services and all-day info
entries do not block the day as "busy" in the subscribing calendar (also in
Outlook).
Your venue decides in the global shift settings whether the calendar feed
contains all shifts or only committed shifts. If the feed contains
all shifts, uncommitted ones appear with the prefix [vorläufig] (the
prefix is German in every interface language). This
setting applies regardless of what planners already see in the full roster.
Keep the subscription address private
The feed URL belongs to the signed-in person and should not be passed on.
Anyone holding it can retrieve the shifts published through that
subscription in their calendar program. Renew link invalidates the old
link.
Shift Plan
Shift Settings
Configure crafts, functions, templates, night work period, working-time rules and the approval workflow
All global configuration of the duty roster lives under System → Shift
settings (permission Shift settings) and is organized in tabs. The tabs
Rules & violations and Open violations additionally require the
permission Plan shifts. Who may see and edit which tabs can be refined
with the permission model.
The general tab: permission model, visibility of uncommitted shifts, shift confirmation, approval workflow, night work period, crafts, global qualifications, craft functions, time presets, sorting, calendar feed, overbooking, project assignments and work time accounting
Day Services
All-day markers assignable to a person's day
Work Time Pattern
Recurring basis for target hours. The tab only appears while work time accounting is switched on
shift groups
Mark related shifts, warning on multiple shift assignments
User Contracts
Contract templates with the contract values that time accounts and rule assignment refer to
shift templates
Templates for single shifts
Shift preset groups
Combine several shift templates into one sequence
Rules & violations
Working-time rules: thresholds, warning colours, assignment to contracts
Open violations
List of detected rule violations to edit, ignore and resolve
Changes to the switches of the general tab are saved immediately; only the
night work period has its own Save button.
The path through the setup in stages is described in
Setting up the duty roster. All master data and templates are covered on this page. The complete
workflow for rule violations and substitute days off is covered in
Rules & Violations.
Only artwork admins see the Permission model card. It defines how finely
access to the shift settings is controlled:
Simple mode active (initial state): the permission Shift settings
grants access to all tabs, reading and writing.
Granular mode active: the permission Shift settings remains the
access to the menu item. Which tabs someone sees and edits is decided by
the Fine-grained shift settings permissions, one permission to view
and one to edit each for: general shift settings, day services, work time
patterns, user contracts, shift groups, shift templates (also covers
shift preset groups) and shift rules (also covers the open violations).
A permission to edit includes viewing.
When granular mode is enabled for the first time, all people and roles that
already hold Shift settings receive all fine-grained permissions.
Afterwards you remove individual ones in the
user permissions. Switching the mode
off and on again later does not distribute the permissions again, so removed
ones stay removed. artwork admins always have full access.
Tabs without read access do not appear. Anyone who may only read the
general tab sees the cards in the upper part, the approval workflow and the
night work period locked, with the hint "You have read access only". The
toggles in the lower part (sorting, subscription, overbooking, project
assignments and working time calculation) are locked as well
Coming with the next update. Some buttons remain operable; Artwork then
rejects the change when saving.
The switch Hide uncommitted shifts from own roster defines whether
people already see their shifts in
My operational plan before the
week has been committed.
Off (initial state): everyone also sees their provisional shifts,
marked with the Provisional badge.
On: the own operational plan only shows committed shifts. As an
exception you can give individual people, for example craft managers, the
permission View own uncommitted shifts.
The switch only affects a person's view of their own operational plan and
its PDF export. Planners still see all shifts in the duty roster. The
calendar subscription does not follow this switch but the setting Shifts
in shift plan subscription under
Miscellaneous toggles.
The Duty roster release workflow toggle enables the two-stage commit
process described in
Committing & Approval.
Below the toggle you select the approvers who review approval requests.
This list, not a permission, determines who may approve.
The workflow can only be enabled with at least one approver ("Add at least
one approver before enabling the workflow."). If it is active and the list
is empty, the page shows a warning because requests would go nowhere;
removing the last approver triggers a confirmation.
When the workflow is disabled, authorized planners commit directly and the
workflow pages disappear from the menu. With the workflow active, each craft
additionally shows the field for the request deadline.
In the general tab you maintain the time window whose hours are booked as
night hours: Night hours from and Night hours until (default
22:00–06:00; for orientation: ArbZG 23–6 h, TVöD 21–6 h). The change
only applies after Save. The window
affects the night booking in the hour account and night work rules such as
Daily maximum on days with night work. Shifts across midnight count their
night minutes completely.
Crafts are the backbone of shift planning. Create the
functions first: the craft dialog only
offers functions that already exist. Each craft has:
a name, abbreviation (at most four characters) and color: the
abbreviation and color identify the craft on every shift card,
under Shift planning permissions the choice between Can be
scheduled by all shift planners and Allocable to a limited extent
with a list of the people who may plan the craft (only people with the
permission Plan shifts are offered),
the craft manager, who is highlighted in the workforce panel and
receives notifications when no planner is listed. You can already enter
them when creating the craft,
the functions available in this craft,
an optional Universally applicable flag: workers of such a craft may be
scheduled into any craft's shifts if they hold a matching function. This
is typical for apprentices or floaters,
Days until notification if shift not fully staffed: how many days
before shift start planners are notified about shifts that are not fully
staffed (0 to 100). With 0 the notification is sent on the day the shift
starts,
Deadline for shift plan request (days before start of week), only
visible with the approval workflow active: if no request has been
submitted for the calendar week by this deadline, the craft management is
notified. New crafts are prefilled with 14 days; leave empty to disable
the reminder. The
Week status shows the
deadline as a yellow or red marker.
You change the order of the crafts by drag & drop in the list.
Which people work in a craft is not set here but in the person's
work profile under
Can be used in the following crafts.
Only people registered as planners of a craft may create, edit or delete
its shifts; otherwise artwork reports "You are currently not registered as
a shift planner for the craft …", and shift templates are only offered for
crafts you can plan. There is one exception for your own shift note: every
scheduled person may edit it, even without planning rights.
Deleting a craft deletes its shifts
When you delete a craft, artwork asks for confirmation and then removes
all shifts of this craft. Scheduled people of committed shifts are
notified. The shifts go to the
recycle bin.
Functions (e.g. Meister, Mitarbeiter, Fachkraft) are the slots a
shift of a craft offers; each has an icon and an availability flag. You
create them in the Craft functions card via New qualification. Which
functions a person can take in a craft is stored per craft in their work
profile. You change the
order of the functions by drag & drop on the handle on the left.
Global qualifications are cross-craft attributes of people (e.g. first
aider, forklift licence). They create no function slot of their own but can
be requested on any shift in addition to the functions.
For reliable suggestions, functions must be maintained on both sides: as a
requirement on the shift and as a capability on the worker.
The option Is taken into account for new shifts is off for a new
function. It has no effect on the shift dialog, which always offers all
functions of the selected craft. It takes effect in two places: the export
Excel Personnel Plan (Project)
only gives functions with this option a column, and in the dialog of a
shift template a function without the option carries the note
“not available” but can still be selected.
A function can be deleted even if shifts already use it: its slots and the
assigned people then move to the default function. The default function
itself cannot be deleted.
You create time presets in the general tab in the Time presets for shifts
card via New time preset. A time preset stores a recurring combination of start, end and break,
for example “Early shift 08:00–16:30”. It speeds up the shift dialog without
setting craft, functions or other shift data. An empty break is prefilled
here too according to the
Working Hours Act.
If more than the time recurs, use a shift template.
Day services are all-day duty markers (with icon and color) that can be pinned
to workers' day cells in the roster, e.g. office duty or on call. They
are not a timed shift. In the workforce panel they appear as a fully coloured
ball; the icon is automatically white or black depending on the brightness
of the colour.
In the Day Services tab you create a service via New Day Service
with name, icon and colour; all three are required.
Day services are assigned in the duty roster: in the
workforce panel,
switch on Day Services, pick the service next to the switch and click a
person's day cell. Another click on the same cell removes the selected
service again. This works for internal people, freelancers and service providers
and requires the permission Plan shifts. The switch only appears once at
least one day service exists. Day services have no effect on time accounts
or the rule check.
Deleting removes all assignments
When you delete a day service, artwork asks for confirmation and then
also removes all of its assignments to people, including past ones.
Work time patterns define recurring weekly working-time schemes. In the
User Contracts tab you create contract templates with their contract
parameters; contract and pattern are assigned to a person in their profile.
They feed the hour balances in the
workforce panel.
You create a work time pattern via Add Work Time Pattern: with a name,
an optional description and one value per weekday. The values are daily
target hours, not times of day: 08:00 means a target of eight hours on that
day, 00:00 a day without a target. The list shows the daily values and the
Total hours of the week for each pattern.
Editing a pattern affects everyone it is assigned to
When you edit a pattern, artwork applies the new daily values to all
people it is assigned to, in all of their periods with this pattern,
including past ones. For a change from a certain date, create a new
pattern instead and assign it in the profile via Plan change. When
you delete a pattern, people keep their previous daily values as
individual weekly hours.
You create a contract template in the User Contracts tab via Add User
Contracts. The name is required. The number fields Free Full Days Per
Week, Free Half Days Per Week and Compensation Period (in days)
are prefilled with 0 and must not be left empty, otherwise the template is
not saved.
Field
Effect
Free Full Days Per Week, Free Half Days Per Week
Key-figure targets: weekly value times the weeks of the season half, 0 means no target. The full-days value also applies to the rule Minimum whole free days per week when no value of its own is set there
Special Day Rule Active
Active (preset): special days reduce the person's daily target. Inactive: special days do not count, every day has the normal daily target
Compensation Period (in days)
Deadline within which a missed free day must be granted as a substitute day off
Use three-month average for target-hour reductions
For weekly holidays and holiday-related compensation days without work, the target is reduced by the average actual daily working time of the three completed calendar months before. If there is no working day in that period, the contractual daily target applies. This switch exists only in the template, not per person
Season-related info data
Six minimum entitlements that you activate individually and give a Minimum value (X): free Sundays per season, days off in the first 26 weeks of the season, free Sundays connected with Saturday/Monday per season half, free Sundays + Saturdays per season, free Sundays per calendar year and 1.5-day combinations. They appear as targets in the person's key figures
Annual vacation days (per calendar year)
Vacation entitlement as a target in the key figures
Non-reduced overtime within the deadline leads to financial compensation
Activates the overtime deadline. The field Period within which overtime must be reduced (days) states after how many days overtime that has not been reduced counts as due for financial compensation
On assignment, artwork copies the template's values into the person's
contract period. If you change the template later, periods that are already
assigned keep their copied values and show them in the profile as
deviations from the template. Only numeric values that are 0 in the
person's period, and the three-month average, still follow the template.
The note in the edit window says the same Coming with the next update: change
all other values and switches in the contract of each person.
Working-time rules are bound to the template, not to the person. On days
on which a person has no contract, or an individual contract without a
template, they are not covered by the rule check Coming with the next update. The same holds when you delete a template:
the people's contract periods remain as individual contracts with their
values, but the rules of the deleted template no longer apply to them.
Contract values are also the basis for working-time rules, vacation and
overtime. If a contract changes, maintain the validity period carefully so
past and future weeks are evaluated with the right target hours. Details are
covered under
Contract & working hours.
Shift groups connect related shifts that already exist. They can appear
as tags on shift cards (display setting Show Shift group tag). They are
also the prerequisite for the rule type
Rest time between shift groups:
without maintained groups this rule cannot take effect.
You create a shift group via New shift group with a name, a colour and
an optional icon. It is assigned per shift in the shift dialog, in the
Shift Group field. When you delete a group, its shifts remain and only
lose the assignment.
The shift groups tab also holds the switch Waring on multiple shift
assignments. When it is on, the duty roster draws a red frame around a
person's day cell as soon as they are assigned to shifts of at least two
different shift groups on the same day. Several shifts of the same group do
not trigger the warning. In granular mode this switch belongs to the
permission Edit general shift settings, not to Edit shift groups.
Tool
Purpose
Shift preset group
Use several shift templates together when creating shifts
Shift group
Mark related concrete shifts and check assignments
Shift templates and shift preset groups each have their own tab. A shift
template copies recurring information into a new shift. In the shift
dialog the inserted values remain editable before saving; templates are
starting points, not locked shift types. Via Add Shift based on
templates in the duty roster, by contrast, the shifts are created
immediately, without an intermediate step. Use recognisable names such as
“Evening admission – Front of house” instead of “Standard”.
You create a shift template via Create Preset. It stores name, start
and end time, break, craft, description and the demand per function; name,
times and craft are required. Room, project, shift group and global
qualifications are not part of the template. The list can be searched by
name or craft, filtered by craft and sorted by start time or name. Later
changes to a template do not affect shifts that were already created from
it.
Shift preset groups combine several templates into one sequence, such as
setup, event and strike. A group consists of a name and the selected shift
templates; a template can be part of several groups. Deleting a group
leaves its individual templates intact. Deleting a shift template also
removes it from its groups. Practical use is explained under
Creating shifts.
The Rules & violations tab defines working-time rules (rest periods
between shifts, maximum working time, night work, days off …) that are bound
to specific contracts. Assignments that break a rule appear in the Open
violations tab. There planners edit them, ignore them with a reason or
resolve them and, if needed, book substitute days off. A separate
dashboard under Shift plan → Compensation days overview tracks granted
and open substitute days off. The person's contract determines which rules
apply.
Rule types, violation handling and substitute days off are described under
Rules & Violations.
Several settings are not global but saved per user: open crafts and
function groups, worker sorting, compact view, light or dark workforce
panel, zoom level, visible period, filters and display settings per view.
Two planners can therefore work with different perspectives without changing
the shared duty roster.
Sort settings: toggle between Sort by first name (left, initial
state) and Sort by last name (right); the side shown in bold applies.
The choice applies to everyone and decides what the alphabetical sort
orders in the workforce panel of the duty roster sort by
Shifts in shift plan subscription: Only committed shifts or All
shifts. With All shifts the ICS feed also contains shifts that are
not yet committed, marked with "[vorläufig]"
Overbooking of shifts: with Allow overbooking, planners may assign
more workers than a shift requires. Overbooked positions are marked
separately and the demand remains unchanged
Shift confirmation by employees: scheduled people can accept or
decline their shifts in My operational plan; planners record replies
on their behalf. Only people with the permission Accept or decline
shifts see the accept/decline buttons, see
Committing & Approval.
While shift confirmation is active, the switch Show confirmations in
shift history appears below it: accepted and declined shifts then show
as their own category in the shift history. Responses are always
recorded; the switch only controls whether the history shows them
Work time accounting: Activated (default) or
Deactivated. When switched off, the duty roster is only used to create
and staff shifts: no target from work time patterns, no time account, no
overtime, no nightly booking; the calendar week column shows only the
planned hours, and the Work Time Pattern tab, the work time
overview export and the tabs Actual hours and Overtime in the key
figures window are removed. Stored data is kept; days while the
calculation was off are not booked afterwards
Project assignments: Activated (default) or Deactivated.
When switched off, all buttons and displays for
project assignments and project wishes
disappear from the duty roster, operational plan, project shifts tab,
availability calendar and multi-edit, as does the display setting Show
project assignments. Existing assignments remain stored and reappear
when the setting is switched back on.
The setup builds up in three stages; each stage can be used on its own.
The detailed guide is
Setting up the duty roster.
Stage 1 – plan and staff shifts: create functions, then crafts with abbreviation, colour, functions and planning rights; in every person's work profile set the switch, the crafts and the functions.
Stage 2 – calculate working time (optional): create work time patterns and user contracts and assign them to people under Contract & working hours; check the night work period. Without this stage, switch off work time accounting.
Stage 3 – rules and violations (optional, needs stage 2): create the legal default rules, add your own rules, assign contracts; maintain shift groups for the rest time between groups.
At any time: time presets and shift templates, shift preset groups, day services, global qualifications, approval workflow, shift confirmation.
Use a test week to check suggestions, warnings and, from stage 2, time accounts.
Inventory System
Overview
How the inventory catalog, article planning, and material issues work together
The inventory system connects article records with time-based planning.
It answers three different questions:
What do we own? Articles, quantities, statuses, properties, and
individually tracked items in the catalog.
When is it available? Internal and external reservations in article
planning.
Who or which project received it? Internal and external material
issues.
A material issue does not reduce the recorded total stock. It reserves the
selected quantity for its period, allowing the same article to be planned
before and after it while overlapping demand becomes visible as overbooking.
Which menu entries you see depends on your permissions:
Inventory requires View inventory, Article Planning and
Material Issues require Inventory disposition.
A type of material with a shared description and total quantity, such as “wireless system model X”.
Single inventory capable
Every physical unit can have its own properties, status, and inventory number. This manual also says “individually tracked”.
Status
Splits stock by condition or usability. The statuses are fixed: Einsatzbereit (ready for use), Defekt, Nicht auffindbar, Ausgesondert and fest verbaut; only Einsatzbereit counts as available.
Property
A configured field such as purchase date, power, serial number, file, room, or manufacturer.
Material issue
A time-limited reservation of catalog articles and custom items.
Internal material issue
Material for a project, room, or internal responsible people.
External material issue
An issue to an external recipient with material value and return information, informally also called a loan slip. It stays reserved until the return is entered.
Material set
Reusable list of articles and standard quantities; not yet a reservation.
Product basket
Personal temporary collection from which a material issue can be created.
The Inventory menu: browse, search and filter articles and open the article details. Includes neither Article Planning nor Material Issues
Create & edit inventory
Maintain articles, their properties and file attachments (Add Article, edit mode in the article dialog)
Delete inventory
Move articles to the trash, restore and permanently delete them; unlocks the Articles tab in the recycle bin
Inventory disposition
The Article Planning and Material Issues menus, create, edit and delete material issues of all projects, confirm returns
Material issue log
Open the cross-project change history (read only)
Create & edit sets
The Material Sets tab under System → Inventory, create and change sets
Delete sets
Remove material sets
Inventory settings
System → Inventory with all tabs; manage categories, properties, statuses, tags, and manufacturers
The inventory overview is visible to anyone who has View inventory or a
permission that includes it: Create & edit inventory, Delete
inventory or Inventory disposition. Delete inventory also includes
creating and editing, and Delete sets includes creating and editing
sets. The overview used to be visible to everyone as soon as the module was
enabled. With the update that introduced the permission, all existing users
and all permission presets therefore received View inventory once;
admins can revoke it selectively since then.
Project team members with write access can create and edit the material
issues of their own project in the project tab without Inventory
disposition; anyone who can read the project sees its material issues. An
external material issue can also be edited by the person entered as
Issued by, who can confirm the return as well. The former permissions
“Manage inventory stock” and “Inventory planner” no longer exist.
Individual tags can additionally be restricted to selected users or
departments. Such a tag protects the whole article: if an article carries a
restricted tag, only people who are released for all restricted tags of that
article can edit it, delete it or restore it from the recycle bin. Admins
are exempt.
Artwork plans availability and documents issues. An issue is not a purchase,
depreciation, or accounting stock movement. Status and return information
must be updated deliberately when the real condition of an article changes.
Inventory System
Inventory catalog & articles
Find, filter, create, and maintain pooled or individually tracked articles
Open Inventory System → Inventory for the complete article catalog. The
menu entry requires the View inventory permission (see
permissions). Use
an image grid or table; categories and subcategories structure articles,
while statuses, properties, and tags support precise searches.
The Search Articles field can cover All properties or one selected
property. This is
useful when a value should be found specifically as a serial number rather
than anywhere in an article name or description.
Additional filters include category and subcategory, quick status counts
(one click applies the filter immediately, a second click removes it),
configured properties with operators appropriate to their data type, tags
grouped into tag groups, and saved filters.
Properties, tags and saved filters live in the Inventory Filter dialog
(filter icon in the toolbar). Changes take effect immediately. Active
filters appear as chips. The filter stays set when you switch categories and
until your next visit. If no result is left, Artwork offers Reset all
filters; reset them before assuming a missing result means the article
does not exist.
Save a frequently used combination of properties and tags in the
Inventory Filter dialog under Saved filters with Save. Give it a
purposeful name such as “mobile audio, ready for use”. Saved filters are
personal; other users do not see them. Click the name to apply the filter,
use the cross to delete it.
With the star (Set as default) a saved filter is applied automatically
when you open the inventory. The default applies to the category or
subcategory in which you saved the filter; a default saved in the overall
overview applies everywhere no specific default is set.
The grid supports visual recognition through images. The table aligns
articles in a category under shared property columns, making technical data
and quantities easier to compare. While a quick status filter is active,
the table shows a separate column with the quantity in that status next to
the total quantity. Via the Display settings cog you can enable Hide
article images in overview for yourself to fit more information on
screen. The chosen view is saved for you as well.
Choose Add Article. It only appears with the Create & edit inventory permission.
Add name, description, and images by click or drag and drop; select a main image.
Select category and, where applicable, subcategory.
Enter total quantity and distribute it across available statuses; for individually tracked articles the total follows from the units.
Assign tags and complete the properties supplied by the category.
Decide whether individual tracking is required and save.
The visible and required fields are controlled by
inventory settings. A
category change can therefore reveal a different set of fields. Fields can
be prefilled with a default value stored in the category. Properties that do
not fit this one article can be removed in the form.
Create stays disabled as long as a category or a required value is
missing or the status quantities do not match the total quantity.
When editing an existing article, Artwork saves name, description, total
quantity, category and subcategory immediately when you leave the field.
The same applies to units that are already saved: name, description,
quantity, status and property values are applied directly. All other details
(status quantities, tags, images, properties of the article and newly added
units) only take effect with Update.
For a pooled article, enter a total quantity and split it across the
predefined statuses. The status quantities must add up to the total: Artwork
tells you whether the sum is above or below the total and only lets you save
once both match. Only stock in the status Einsatzbereit (ready for use)
counts for planning. The status list in the article dialog highlights it,
and the order of statuses everywhere follows the sorting defined in the
settings.
If you change the total quantity of an existing article, Artwork balances
the difference in the status Einsatzbereit: 12 units with 10 ready
become 13 ready automatically when the total is raised to 15. The total
cannot be lowered below the sum of the other statuses. Reduce the quantities
in the other statuses first in that case.
For individually tracked articles the total quantity cannot be edited
manually: it is calculated automatically from the sum of the individual
units.
For example, if ten of twelve cables are ready, one is defective, and one is
retired, only ten are initially available for issues.
Status and issue are different
An issue reserves quantity for a period. A status describes stock
condition. If an item returns damaged, its status may also need updating.
Enable Single inventory capable where every unit needs a separate
identity, such as radios, cameras, or test devices. Each unit can have its
own status, properties, and inventory number. A global setting can force
every detailed unit to quantity 1. Only units in the status
Einsatzbereit are available.
Properties may be shared across all units, or marked as an individual
value that is not copied during duplication or bulk editing, for example a
serial number.
The article dialog then shows two areas: Across-article properties (once
for all units) and Detailed article properties, with the list of units
on the left and the editing area of the selected unit on the right. The
Total quantity is calculated automatically from the units.
Add Detailed Article creates a single unit (“New Article”). When you
hover over a row you can copy it (name, description, status and
properties are taken over, individual values cleared) or delete it.
Bulk create creates up to 100 units in one step: quantity, status and
a default value for each non-shared property (text, number, date,
selection, checkbox, room, manufacturer). The units are named “New Article
1 … n” and have quantity 1.
Edit selection changes marked units together: tick rows or use
Select all (shift-click marks a range; the search field also finds
inventory numbers), then set status, quantity or a property with its value
and confirm with Apply. Delete selection removes the marked units
after confirmation.
All three actions initially only affect the dialog; saving happens with
Create or Update. Only individual fields of units that are already
saved are stored immediately. Units with missing mandatory values are marked red.
Artwork assigns inventory numbers on saving in the format
main number-sequence number (for example 00042-001); sequence numbers are
never reassigned, not even after a unit is deleted. A central prefix and the
option to show the inventory number instead of the name come from the
inventory settings.
Properties can contain text, number, date, year, time, selection, checkbox,
or file values. Special properties connect an article to a room or CRM
manufacturer. File fields suit manuals, certificates, and data sheets.
Descriptions and manufacturer details are plain text: HTML markup is not
interpreted as formatting, and line breaks are preserved.
Upload several images by click or drag and drop and choose a main image.
The maximum size of an image is defined in the
inventory settings (10 MB by
default). Tags add flexible attributes
such as “outdoor”, “trained staff only”, or “inspection due”. A lock marks a
tag with restricted assignment rights. You can only assign tags you are
released for. If an article carries a restricted tag you are not released
for, you can neither edit nor delete the article.
The detail view combines description, inventory number, category, status
quantities, properties, images, and individual units. Unticked checkbox
properties are shown as “No”. Editing and deletion depend on permission
(Create & edit inventory and Delete inventory).
Deleted articles move to the recycle bin under the
Articles tab (permission Delete inventory). If the article is
reserved in upcoming material issues, the delete dialog states how many: the
article stays part of these issues but no longer counts as available. Before
permanent deletion, check whether historical issues and reports still
require it.
Artwork removes the article from all material sets as soon as it is moved to
the recycle bin. If you restore it, images, individual units and status
quantities come back; you have to add it to the sets again. Inventory
numbers of deleted articles are not reassigned.
Add the required articles in the overview: in the grid view with the Add to Basket button that appears when hovering over a tile, in the table view by clicking the row. Repeated additions increase the quantity.
Open the basket, review quantities, and remove unwanted entries. Quantity 0 removes the entry as well.
Choose an internal or external material issue.
Open the form with Create Material Issue and complete its period and assignment.
The basket does not reserve stock. Availability changes only after the
material issue is saved. After the issue is saved, Artwork empties the
basket; if you cancel the form, the basket is kept.
Are serial numbers and other unique values configured individually?
Is there a useful main image?
Are relevant files, room, and manufacturer maintained?
Do tags improve search or access rather than merely duplicate categories?
Inventory System
Article planning
Read daily availability, compare issues, and resolve overbooking
Article planning (menu Inventory System → Article Planning) shows
articles as rows and days as columns. It combines stock with every internal
and external material issue, revealing the quantity still available on each
day. The menu entry requires the Inventory disposition permission.
Choose the required date range in the period bar (with quick selection and
Today); the arrows with the tooltip Jump by … move by day, week
or month. The search field finds articles, categories and subcategories; if
the term matches a category or subcategory, the whole category stays
visible. Categories and subcategories start collapsed. Open them
individually or with Expand all / Collapse all; the number next to
the name is the count of contained articles. The grid shows the calendar
week at the start of each week.
The Display Settings button offers:
Only planned articles: hides rows without an issue in the visible
period,
Share time period across views: links the period to the calendar,
planning calendar, shift plan and list view (see
display settings).
The Legend info icon explains the colours: red dot Overbooked (< 0), blue
Today, grey Weekend, green bar Internal issue, striped bar
External issue.
Your open groups and the “Only planned articles” option are saved for future
work.
Availability equals ready-for-use stock minus all overlapping issues.
Ready-for-use stock is the quantity in the status Einsatzbereit; for
individually tracked articles it is the sum of the units in that status. A
multi-day issue affects every day of its period.
An external material issue keeps its articles reserved beyond the return
date up to today as long as the
return has not
been entered. An unexpectedly low value for past days and today therefore
often comes from an overdue loan slip.
Click an article/day cell to open its usage panel. It shows total and
ready-for-use stock, status breakdown, internal and external use, remaining
or minimum available quantity, and the individual issues behind the result.
The tabs internal and external separate the two kinds of use; the
number next to each is the quantity reserved there. Edit on an issue
opens its form. If stock is exceeded on the selected day, a red notice
appears below.
If no issue exists yet for the demand, New material issue with this
article opens the form for a new internal
material issue directly from the usage
panel. The article is prefilled with quantity 1 and the displayed day as the
period.
Hover for name, period, and project or recipient. Click the bar to edit the
material issue. After the form is closed, article planning recalculates
availability and bars.
Article planning uses the same article permissions as the catalog. Its
filter dialog narrows by categories, subcategories, properties and tags and
is confirmed with Apply. Issues can additionally be highlighted by
project: if you
select one or more projects under Highlight projects in the filter, the
bars of all other issues are dimmed. With no selection, all bars are
highlighted. Internal issues lead to the linked project; external issues
show the recipient instead.
The Material issue book and External Material issue book tabs separate
the workflows. The filters sit in a bar above the list:
Book
Filters
Material issue book
Search by issue name (also searches the notes), period, room, project, Responsible
External Material issue book
Search by issue or external name (also searches the return remarks), period, Issued by, Received by, Only overdue returns
Besides From and To, the period offers the quick ranges Today,
This week (Monday to Sunday) and This month. The period filter shows
every issue whose period touches the selected range, not only those that
start within it. Reset filters clears all fields.
In both books the Status column shows whether custom items are still
open (Status Open or Open) or whether the issue is Completed in
that respect. The external book additionally shows the
return state.
New issue of material opens the form. At the top, the toggle switches
between Internal material issue and External material issue; the
fields adapt accordingly. When editing, the dialog is titled Edit issue of
material for both kinds.
Two prefills help with the project reference:
The Recently opened projects tiles next to the project search apply a
project with one click.
If you change the assigned project, Artwork resets the automatically
adopted values (name, period, and project rooms). Values you changed
manually before are kept.
No silent data loss
If you close a form with unsaved changes, by clicking beside it or pressing
Escape, Artwork asks Should the entered data be discarded? and offers
Save in addition to Discard and No, continue editing.
Unchanged forms close without a prompt.
An internal issue can contain a name, optional project and room, start/end
dates and times, responsible users, notes, catalog articles and quantities,
custom items, and files.
The Material issue name and the start and end dates are required. The
times are prefilled with 00:00 and 23:59 and must not be left empty. The
end must be after the start, taking date and time together. Each article
appears only once per issue and needs a quantity of at least 1.
Open New issue of material and choose Internal material issue.
Assign a project where relevant; name and project period are prefilled.
Optionally assign a room. Clicking a room under Project rooms selects it and sets the period to that room's use in the project.
Verify dates, times, responsible users, and notes.
Search articles or insert a material set, basket, or previous issue.
Check quantities and availability; add custom items and files.
Save and verify the result in planning or the project component.
The same workflow can start inside a project's material-issue component,
where project context is already available. Project team members with write
access can create and edit their project's issues there without the
Inventory disposition permission. Likewise,
New material issue with this article
in article planning opens a prefilled form.
Search available inventory on the left and review selected quantities on the
right. As soon as a period is set, every added article states Available
in period. In the internal form the search results additionally show the
in period badge with the available quantity; the external form has no
such badge. Availability is the lowest level across the
complete period: the basis is the quantity in the Einsatzbereit (ready for use) status
(for individually tracked articles, the sum of ready-for-use units), minus
the highest simultaneous use by other internal and external issues. Issues
that do not overlap therefore do not add up. Details reveals other
issues consuming stock.
If a quantity exceeds availability, Artwork marks the field red, shows the
Overbooking badge and, at the top, the Conflicts regarding
availability banner with Requested and Available per article.
Automatically adjust quantities sets all affected quantities to the
available value. Saving remains possible despite overbooking, so this
remains an operational conflict that must be resolved.
If saving an issue causes an article in a current or upcoming issue to be
overbooked, Artwork notifies the people concerned: the responsible users of
internal issues and the person under Issued by of external issues. The
same people are informed when the total quantity or the ready-for-use stock
of an article in their issue changes. Whoever triggers the change
themselves receives no notification. Therefore enter responsible people on
every issue; without them the notification reaches nobody.
A material set inserts a prepared article list and standard quantities;
the button with the package icon (Select material set) opens the set
selection. If the issue already contains articles of the set, Artwork asks:
Add quantities adds the set quantities to the existing ones, Keep
existing quantities leaves them unchanged. Articles not yet included are
added in both cases.
Copy material from another material issue uses an earlier issue, which
you find by name, as the starting point. You can choose from issues of the
same kind: internal ones in the internal form, external ones in the external
form. Articles that are in the recycle
bin by now are not copied. In both cases check the resulting quantities:
sets and copies save entry work but do not guarantee correctness for the
new period.
Availability, project, and custom items must be checked again.
Custom items record material that is not in the catalog, such as consumables
or one-off purchases. Enter name, quantity, and description. As long as
custom items are open, the issue is listed as Open. The Special items
done checkbox in the form or Special items closed in the row menu
shows that the free list has been processed; the issue then counts as
Completed. Custom items
do not contribute to automatic stock availability. Recurring material should
become a catalog article.
An external issue additionally records name and material value, issue and
return dates, external name, email, phone and address as free text fields
(there is no link to a CRM contact here), issuing person (Issued By), an
optional project assignment, return remarks or damage, and files.
Name, Material Value, Issue Date, Return Date and External
Name are required. Material value documents the loan and does not replace
article valuation. The field is prefilled with 0; you can also save with
0, only negative values disable SaveComing with the next update.
The return date cannot precede the issue date.
Reserved until the return is entered
The articles of an external issue stay reserved until the return is entered,
even beyond the return date. If the return date has passed and no return is
recorded, the issue keeps occupying its quantities up to today and thereby
blocks other planning. Enter returns promptly. Loan slips from the time
before return tracking was introduced count as returned.
Always enter a person under Issued By: they receive the
return reminder and may edit the issue and confirm
the return even without the Inventory disposition permission. Without
that permission they cannot open the external issue book; the link in the
reminder then takes them to the preview of the issue
Coming with the next update. They confirm the return with the buttons of the
reminder; they can edit the issue in the
material-issue component of the assigned project.
Material issues can be output as a PDF. The document of an internal issue
states name, project, period, room, responsible people and notes and lists
all articles with category and quantity as well as the custom items. For
external issues it serves as the loan slip with issue and return date,
external person or company, material value and defects after return. Both
end with fields for place, date and signatures.
Choose Print in the issue or in the project component; in the edit dialog, use the printer icon.
Check the Document preview. Nothing is saved up to this point.
Choose Create and attach document to generate the PDF. It is attached to the issue as a file and can be downloaded there.
Choose Enter return in the row menu of the external material issue.
The entry appears for people with Inventory disposition and for the
issuing person as long as no return has been recorded. Put damage or
discrepancies in Defects after return. On saving, Artwork enters you as
Received by. If the planned return date is still in the future, it is
set to today, but no earlier than the issue date; the quantity is then
available again. If the physical condition changed, also update the status
of the affected article or individual unit in the catalog.
In the list, badges show the state:
Badge
Meaning
Returned
The return is entered, the articles are free again.
Return open – material blocked
The return date has passed and no return is recorded. The articles stay reserved.
Not returned
Someone reported “Not returned yet”, but the return date has not passed yet.
When the return date is reached and no return has been entered, the issuing
person (Issued by) receives the notification Return date reached
once, depending on their notification settings also by email. Artwork
checks this daily at 8 a.m. If you change the return date, the reminder is
sent again for the new date. The notification links to the issue, in the
external issue book with Inventory disposition, otherwise as a preview
Coming with the next update, and offers two buttons:
Confirm return opens the return dialog; the issue then counts as
returned. For an early return the return date is set to today and the
quantity becomes available again.
Not returned yet sets the status Not returned and records this in
the log; the return can still be confirmed later.
Without an issuing person, no reminder is sent; it follows as soon as you
add the person. The Only overdue returns filter in the external issue
book lists all issues whose return date has passed and for which no return
has been entered, including those reported as “not returned yet”.
Attach packing lists, handover records, photos, or signed loan slips to
internal and external issues. Existing files can be removed and new ones
added while editing. An existing file is deleted immediately when you click
the bin, not only on saving; this requires the Inventory disposition
permission. Images and PDFs appear as thumbnails; a click opens the
viewer, with page navigation for PDFs.
PDF, JPG, PNG, WebP, DOC, DOCX, XLS, XLSX, CSV, TXT and ZIP are allowed, up
to 20 MB per file; active content such as HTML or SVG is rejected. Files
are delivered only to signed-in users who may see the respective material
issue. Direct links to the storage path do not work,
so share files through Artwork rather than copied addresses.
With the Material issue log permission, the history button in the
material issue book opens changes across projects. It covers internal and
external issues, including deleted ones. Filters narrow by period, project,
issue type and search term. Without input, the log shows the current month.
The date filter includes issues whose period overlaps at least one day with
the selected range. With a project filter set, only internal issues appear.
In the project tab the log is reachable without Inventory disposition.
The log supports traceability but does not replace clear names,
responsibilities, and return notes in the issue itself.
Does an internal issue reference the correct project or room?
Are responsible people or external contact details complete?
Were quantities checked over the entire period?
Are custom items processed and required files attached?
Does any overbooking still need coordination?
Inventory System
Inventory settings
Configure categories, properties, statuses, tags, and inventory numbers
Global configuration lives under System → Inventory and requires the
Inventory settings permission. The Material Sets tab is on the same
page and is covered under Material sets;
it is also visible to people with the set permissions who may not edit the
other tabs.
Detailed articles always with quantity 1 makes every detailed record one
physical unit. Its quantity can no longer be edited. Inventory-number settings
control whether the number replaces the name for detailed units and add a
display prefix such as INV-. The prefix does not change stored data.
Under Article images you set the Maximum size per article image
(MB). Values from 1 to 50 MB are allowed, the default is 10 MB. Larger
images are rejected on upload. The server upload limits must allow at least
this size.
Categories form the first navigation level and subcategories refine it.
Properties assigned to a category describe the articles within it and become
the fields of the article form. Subcategories add further fields on top of
those of the category. Use categories for stable areas such as audio,
lighting, or furniture; temporary attributes such as “Festival 2027” are
better suited to tags.
In the Create Category dialog, and when editing, you also define:
the order of the assigned properties by drag and drop. It determines the
order of the fields in the article form and of the columns in the article
overview,
a Default Value per property that prefills the field for new articles
of this category.
Before restructuring a used category, check affected articles and whether
their properties remain understandable.
A category can only be deleted when it no longer contains articles. Articles
in the recycle bin count as well: move the articles to another category or
delete them permanently first. The subcategories of an empty category are
deleted with it. If you delete only a subcategory, its articles stay in the
parent category and merely lose the subcategory assignment. The
confirmation prompt and the note in the categories tab say so as well
Coming with the next update.
Properties may contain text, number, date, year, time, date/time, checkbox,
selection, file, or special room/manufacturer links.
The Room and Manufacturer properties are predefined. You can rename
them and change their options, but you can neither delete them nor change
their data type. An optional Tooltip text appears in the article form as
a hint next to the field. A property only takes effect once it is assigned
to a category or subcategory.
For the Selection data type, enter the selectable values with Selection
Add value; the property cannot be saved without at least one value. If you
delete a property, its values are lost on all articles.
Option
Effect
Filterable
Property becomes available in the inventory filter and in the material set dialog.
Show in article overview
Property appears as a column or overview detail.
Value required
Articles in the category require a value.
Across all articles
One value applies to every detailed unit.
Individual value
Value is excluded from duplication and bulk editing.
Drag and drop controls the order of the properties in this list. The order
of an article's fields is set in the respective
category instead. Use individual value
for serial numbers and other unique identifiers.
Statuses split article quantity by condition. The status catalog is fixed:
Einsatzbereit (ready for use), Defekt (defective), Nicht
auffindbar (missing), Ausgesondert (retired) and fest verbaut
(permanently installed). On the Status Settings tab you can change the
colour (menu Edit) and set the order by drag and drop. You cannot
create, rename or delete statuses.
Einsatzbereit is the default status: only its quantity counts as
available, and article planning uses it as the available base quantity. The
article dialog highlights this status in the status list. The order defined
here applies wherever status quantities are shown.
Agree in your team on what each status means for you: material in
Defekt, Nicht auffindbar, Ausgesondert or fest verbaut is
not available for any issue.
Tags are coloured, combinable attributes. Groups organise them in the filter,
for example by location, safety, or inspection state. A tag needs a name
and a colour; the tag group is optional.
Tag use and editing can be restricted to selected users and departments:
tick Restrict editing of this tag in the tag dialog and select the
people and departments via the search. Without the tick, everyone with
access to the inventory can use the tag. If you remove the tick again,
Artwork deletes the stored releases. The restriction applies to
the whole article: anyone who is not released for all restricted tags of an
article can neither edit nor delete that article, even with the Create &
edit inventory permission. Admins are exempt. A protected tag should
therefore have a clear owner and meaning.
If you delete a tag group, its tags remain and are merely no longer grouped.
If you delete a tag, it is removed from all articles.
Agree on the meaning of the statuses and of ready-for-use stock, then set colours and order.
Create stable categories and subcategories.
Define reusable properties with suitable data types.
Assign them to categories and use required fields sparingly.
Create tag groups, tags, and access restrictions.
Set inventory-number display and detailed-unit quantity logic.
Create sample articles and verify search, table, and planning views.
Only then prepare common equipment as material sets.
Inventory System
Material sets
Prepare recurring article collections and use them in material issues
Under System → Inventory in the Material Sets tab, you manage reusable
collections of inventory articles. The tab is visible to people with the
Create & edit sets or Inventory settings permission; creating,
changing, and deleting sets always requires the set permissions (see
Permissions).
A material set stores a name, optional description, and articles with
standard quantities, for example “small press conference”, “DJ setup”, or
“mobile workshop”.
In the Material Sets tab, click New Material Set.
Enter a clear name and a useful description.
Find articles by searching for article or (sub)category or by narrowing with the inventory filter. A click on an article under Found Articles adds it to the set with quantity 1; every further click increases the quantity by 1.
Under Selected Articles, adjust each standard quantity and review the selection. A set needs at least one article, otherwise it cannot be saved.
Save and test the set in a sample material issue.
The filter in the set dialog is the same as in the inventory overview: it is
fed by the properties marked as filterable and by the tags.
In the form of a material issue, open
the set selection with the Select material set icon and apply a set with
Select. Articles and quantities become a starting point. If the issue
already contains articles of the set, Artwork asks in the dialog Articles
already in this issue: Add quantities adds the set quantities to the
existing ones, Keep existing quantities leaves these articles unchanged.
Articles not yet included are added in both cases.
Period, availability, project, and recipient are defined in the concrete
issue. Adjust quantities there when the individual case differs from the
standard.
A set is therefore neither a reservation nor a stock change. Stock is only
occupied for a period by the saved material issue.
Update a set when the usual equipment changes permanently. Existing material
issues are not changed retroactively. If an article is deleted from the
inventory, Artwork also removes it from every set. Before deleting a set,
clarify whether teams still rely on it as a standard; the action cannot be
undone.
One-off personal selection directly from the catalog
Copy issue
Reusing one specific earlier issue as a starting point
Use clear names and keep the number of sets manageable. Several nearly
identical names make selecting the wrong standard more likely.
To-dos & Checklists
Overview
Understand personal tasks, shared checklists, and templates
The To-dos sidebar entry combines every checklist and task relevant to
you. The interface also calls checklists to-do lists; both terms mean
the same thing. Checklists can stand alone or belong to a project and a particular
project tab. Tasks from funding sources appear in an additional section.
To-dos shows checklists assigned to you or containing at least one task
assigned to you.
A project shows the checklists in its configured checklist component.
Funding source tasks appear as a collapsed subcategory below your
checklists and link to the corresponding funding record.
Notifications can link directly to a temporarily highlighted task.
A public checklist does not automatically appear for everyone. It becomes
relevant in a personal view when the person is assigned to the list or a task.
Checklists in projects follow the project permission: anyone who wants to
create or edit them inside the project needs Write permission in the
project team (or is project
management, the creator of the project, or has Write permissions for all
projects); in addition, the checklist component itself may be restricted.
Ticking off is also open to every member of the project team who may see
the tab of the list, even without write permission. Anyone who may not edit
the list sees the tick-off checkbox greyed out.
Everyone can create, edit and delete their own to-do lists without any
special permission. Other people's checklists are not editable by everyone:
editing is allowed for the creating person, for people to whom the list or
one of its tasks is assigned, and for people with access through a shared
list.
Permission
Effect
Manage all to-do lists
Open, change and delete other people's to-do lists
Checklist templates
Create, edit and delete templates under System → Checklists; includes Manage all to-do lists
Delete in the list menu is only available to the creating person and to
people with one of the two permissions.
If you assign a person to a project checklist who is not yet part of the
project team, Artwork adds them to the project team and notifies them. This
requires that you yourself may write in the project. The person receives
neither write permission nor budget access: assignment makes a task visible
but does not grant write access to all other project data. People coming
from a template are not
added to the project team this way.
To-dos & Checklists
Checklists & tasks
Create lists, assign tasks, maintain deadlines, and document progress
Checklists organise related tasks. Create them under To-dos or inside a
project's checklist component.
Optionally choose a project. When working outside it, also select the appropriate project tab.
Use the Private switch to decide whether the list is private and create it. The switch is only available without a template; a list created from a template is shared at first.
A template-based list inherits its name, tasks, order, assignments, and
calculated deadlines. It then becomes independent and can be changed without
altering the template.
A list without a template is assigned to yourself at first. Create stays
disabled as long as the name is missing (without a template) or no project
tab is selected for a chosen project. The tab must be visible to you,
otherwise Artwork refuses to create the list.
A private checklist is visible only to you and suits personal
preparation or drafts. For teamwork, make it shared and assign users.
Private lists in a project
Coming with the next update
A private list attached to a project stays private as well: in the
project's checklist component and in the app, only you and people
explicitly assigned to the list or one of its tasks can see and edit it.
The project team and project permissions do not open it.
Use Assign users in the list menu to place the complete checklist in
people's personal to-do views. The menu entry is missing on private lists. Assigned users see all its tasks. Project checklists prioritise
appropriate team members in the search.
Alternatively, assign a person only to an individual task. The complete
checklist with all its tasks then appears in their view as well, and they
may edit the list.
A task has a required name (Task) and may contain a deadline (To be
done until?), a description (Comment), and, on shared lists, one or
more assignees. The deadline is a date without a time and lasts until the
end of that day. State the expected result, such as “Approve technical
rider” rather than simply “Rider”.
Whoever creates a task is automatically entered as its assignee. You can
change that again when editing the task.
Open tasks display deadlines and overdue dates are highlighted. Tasks without
a deadline remain possible but should represent genuinely time-independent
work.
For open tasks with a deadline, Artwork sends two reminders: one when the
deadline expires within the next 24 hours, and one as soon as it has passed.
The check runs daily at 9 a.m. On private lists the reminder goes to the
creating person, on shared lists to the people assigned to the list and to
the assignees of the task. Whoever created the shared list is reminded only
as an assignee of the task. If you move the deadline, both reminders are sent
again. Assignment and deadline notifications depend on personal notification
settings.
The checkbox completes a task. Artwork shows who completed it and when; an
accidental completion can be reopened. The checklist menu can switch all
tasks together with Mark all tasks as completed or Mark all tasks as
unfinished. Editing a completed task leaves it completed. If you lack editing rights for the list,
the checkbox is greyed out. Completed work is hidden or shown at the end
depending on the personal filter.
With the required rights, change a task's name, comment, deadline, and
assignees or delete it. A deleted task cannot be restored. Other people's
lists are not editable by everyone; you can edit your own lists, lists
assigned to you and lists shared with you. Drag and drop can move tasks into another checklist; afterwards verify
project context, visibility, and responsibility.
A checklist itself can be:
renamed and changed between private and shared (Edit),
duplicated (Duplicate); the copy takes over the tasks and the people
assigned to the list,
saved as a template (Save as template, requires the Checklist
templates permission, see
Checklist templates),
completed or reopened as a whole,
deleted (Delete, only for the creating person and people with the
Manage all to-do lists or Checklist templates permission).
Deletion also removes its tasks and should not be used as archiving.
A project may contain several checklist components on different tabs. A list
created outside the project must therefore reference both the project and the
correct tab. The project link in My To-dos opens the associated checklist
area directly.
Project checklists follow the project permission: creating and editing
inside the project require Write permission, ticking off is open to all
members of the project team (see
Permissions and project access).
If you assign people to the list or to a task inside the project who are not
yet part of the project team, they join the project team without write
permission and are notified about it. The same applies to the people of a
template when you create a list from a template Coming with the next update.
You can see who belongs to the team in the
project team.
Are responsible people, not only observers, assigned?
Are deadlines realistic and complete?
Does the list belong to the right project and tab?
Is private/shared set correctly?
Is completed work documented rather than deleted?
To-dos & Checklists
My to-dos
Search, filter, and work with personally relevant checklists in list or Kanban view
Under To-dos, Artwork shows only checklists assigned to you or containing
at least one task assigned to you. The page is titled My ToDo-Lists and
is your personal work queue, not a complete list of every checklist in the
organisation. The menu entry appears as soon as the To-dos module is
enabled; no separate permission is required. New checklist creates a
checklist from
here.
Without Show empty lists, only lists with at least one open task
appear. A newly created list without tasks and a fully completed list
therefore only show up with this filter, even when Show completed is
active.
Opposing options in a group are mutually exclusive. Reset restores the
initial view. Filters are stored for your account and do not affect others.
The list view presents wide, collapsible checklists and suits detailed
work. Kanban displays each checklist as a card or column and gives a quick
overview of several smaller lists. Switch between the two with the
List / Kanban toggle; the chosen view is saved personally.
Both views allow completing tasks and reading details. With sufficient rights,
you can edit tasks or move them between lists.
The Funding source tasks subcategory appears below the checklists when
tasks are assigned to you. It is collapsed by default and deliberately kept
unobtrusive. Each task has a name, description, deadline, the avatars of the
assignees, and a link to the funding source. The checkbox marks a task as
completed and also reverts the completion; the tasks are not part of a
normal checklist.
Narrow down with with project or without project and sort by List name ascending, or by Project timeframe ascending to see the lists of the next productions at the top (see Sorting).
Review overdue and upcoming tasks.
Correct unclear responsibility in the checklist.
Complete tasks rather than delete them.
Briefly show completed work at the end and verify handovers.
To-dos & Checklists
Checklist templates
Prepare recurring task sequences with assignees and relative deadlines
Manage templates under System → Checklists. The menu entry requires the
Checklist templates permission; admins always have it. The permission
includes Manage all to-do lists. Anyone who creates a checklist can use
a template. Templates suit
processes repeated across projects, such as production start, guest-performance
preparation, or project closure.
A template contains a name, ordered tasks, task descriptions, optional
deadlines in days after checklist creation, and users who are assigned
automatically when it is used.
Templates store a number of days rather than a fixed date. A task with 7
days in a checklist created on 1 March receives a deadline of 8 March. An
empty value creates no deadline.
Relative deadlines are suitable for workflows starting with the list. If the
real deadline depends on an event date or funding deadline, verify and adjust
it in the created checklist.
Add tasks with name, comment, and Deadline: days after checklist creation.
Drag tasks into the required order.
Create the template and generate a test checklist from it.
Review automatic team assignment
Template users are assigned automatically to the list and to all tasks and
see the list under To-dos. If the list belongs to a project, Artwork
adds them to the project team without write permission and notifies them
Coming with the next update. Use only permanently responsible people as
defaults.
Choose Save as template from a checklist menu when a real process has
already proved useful. You need the Checklist templates permission for
this and are taken to the template management afterwards.
The name of the list, the tasks with name and comment, and the people
assigned to the list are taken over. Artwork does not take over deadlines:
add the relative deadlines in the new template. Also remove project-specific
wording and review the assignments so the result is reusable.
Select a template while creating a checklist. The resulting list can be
renamed, extended, shortened, and reassigned without changing the central
template.
Derive similar workflows with Duplicate in a template's menu instead of rebuilding them.
Delete obsolete templates only when no further use is expected.
Template changes affect only checklists created in the future.
Sources of Funding
Overview
Bring funding, project budgets, and responsibilities together in one place
Use Sources of Funding to monitor restricted funds, grants, and other
budgets across several projects. Each source can hold an approved amount,
runtime, funding period, permitted projects, and the budget items assigned to
it.
The area also supports day-to-day collaboration. Responsible people, users
with write access, open tasks, documents, categories, reminders, and the
change history are available directly on the source.
A specific fund with its own initial amount, periods, and linked budget items
Funding group
A shared overview of several sources, for example all grants belonging to a season or programme
You assign an individual source to a group through Edit, or you select
it when creating the group.
The detail page of a group combines the positions of its member sources. A
group therefore provides an overview; it does not replace the individual
sources.
Initial amount adjusted by the linked budget positions
Used
Percentage of the volume already claimed
Totals per project
Balance of linked income and cost positions per project
Costs reduce the source while income increases the displayed balance. The
calculation is based on budget positions assigned to the source in its linked
projects. It is therefore only as current as those project budgets and their
assignments.
The menu item Sources of funding requires the enabled module and the
permission Manage sources of funding (module Budget & funding). With this
permission you see all sources and groups in the overview. Without it you
cannot open the area, even if you are listed as responsible on a source.
Admins may do everything.
Action
Who may perform it
Open the overview and the detail page
Manage sources of funding
New, Duplicate, Pin
Manage sources of funding
Edit (master data)
Manage sources of funding, Global budget access, the creator, and people listed on the source under Responsible or Write access
Delete
Delete all sources of funding, Global budget access, or the creator
Edit the side panel (sharing, categories, projects, documents, tasks) Coming with the next update
Manage sources of funding, Delete all sources of funding, Global budget access, the creator, and people listed on the source under Responsible or Write access
The edit buttons in the side panel follow the same rule as saving: anyone
who may edit the source also sees them.
Releasing a project on a source does not give the project team access to
the funding sources area. Anyone working in the project budget can,
however, select the sources released for the project when
linking;
only the name of the source appears there, not its amount or funding
period.
Artwork only shows Edit, Duplicate and Delete if you are
actually allowed to perform the action on that source. If an action such as
New, Edit, Duplicate, or Delete is not available, this is due
to your role or the access settings of that specific source; the permissions
are also checked on the server. The module's
settings require the separate
permission Sources of funding settings.
Funding overview, not bank accounting
Artwork evaluates the project budget positions linked inside the system. It
does not import bank transactions and does not replace financial accounting.
Regularly check that all relevant positions are assigned to the correct
source.
Sources of Funding
Create & manage
Create, find, organise, and maintain sources and groups
Open Sources of funding and select New. The tabs Single source
and Group in the dialog let you switch between an individual source and
a funding group.
The following details are available for an individual source:
Field
Meaning
Title*
A clear name used in lists and project budgets
Sum*
The approved or internally allocated initial volume
Source
Name of the funder, programme, or internal origin of the money
Runtime start/end
Overall administrative period of the source
Funding period start/end
Period in which the funds are intended to be eligible for use
Who is responsible?
People with subject-matter responsibility for the source. They receive both sharing roles on the source, Responsible and Write access, and are notified about the access
Belongs to funding Sources Group
Selection of an existing group; the new source belongs to this group after it is created Coming with the next update
Comment / note
Free text for purpose, reference numbers, conditions, or internal notes
Title and sum are required. Periods are optional, but they are needed for
filters, reminders, and quick context on the detail page. Runtime and
funding period may differ: use runtime for the entire administrative
process and funding period for eligible spending.
You can also configure several reminders while creating a source. See
Reminders
for the available types. Reminders can only be set up in this dialog; the
edit dialog of an existing source does not contain them.
Add yourself as responsible
Whoever creates a source is not automatically part of its sharing. The edit
buttons in the side panel of the detail page (sharing, categories, projects,
documents, tasks) are still shown to you as the creator
Coming with the next update. Add yourself under Who is responsible? if you
want to receive notifications and reminders for the source.
Switch to the group tab in the New dialog. An info block there explains what
groups are for: a funding source group bundles several funding sources so
you can keep track of their budgets together — projects and budget items
are still linked to the individual sources. A group needs a title. You can
also assign responsible people, add a note, select existing funding sources
and assign a symbol via Select an icon (as with project groups). The
icon appears in the overview, on the detail page and on the group's sources;
Remove icon takes it away again.
A source can later be assigned to or removed from a group through Edit.
Use groups for funds that belong together operationally. For overlapping
labels, categories
are more flexible.
Search matches the title of a source or group. You can also limit the type to
all sources & groups, sources only, or funding groups only.
Additional filters cover:
one or more categories,
sources with open tasks only,
a selected period.
When several categories are selected, a source must contain all of them. The
period filter includes sources whose runtime overlaps the chosen period.
Entries without a runtime remain visible. Active filters appear as tags above
the list and can be removed individually. Search, filters and sorting are
not saved; after reloading the page the list is back in its initial view.
The Sources with open tasks filter shows entries with at least one open
task Coming with the next update. In the funding groups only view, it and
the category filter also work for groups.
Sort alphabetically, by funding-period start or end, or by creation date.
Selecting the same criterion again reverses the order. Without a selection
the list is sorted alphabetically in ascending order. When sorting by the
start or end of the funding period in ascending order, entries without a
funding period come first.
Use Pin to keep an important source at the top of your own list. Pinning
is personal and does not alter another user's order. Select Undo pinning
to remove it. Descending order reverses this as well: pinned entries are
then at the end of the list.
Where available, each item shows its title, group membership, amount status,
period, description, latest change, and categories. A group symbol or the
chosen group icon distinguishes groups from individual sources, while a pin
marks your pinned items.
Select the title to open the detail page. This page contains key figures,
linked positions, and the side workspace for access, projects, documents,
and tasks.
Edit opens the master data. For an individual source you can change the
amount, origin, periods, group, responsible people, and note; for a group,
you can also change its member sources.
Duplicate creates a copy titled (Copy) …. It takes over the amount,
origin (Source), runtime, note and group membership. It does not take
over the funding period, sharing, funded projects, categories, reminders,
tasks, documents or the links to budget positions. Add these details to
the copy before working with it.
Delete requires confirmation. The links of the source in the budget
cells of the projects are removed; the budget values themselves remain.
The people listed on the source are notified. If you delete a group, its
sources remain and no longer belong to any group. First check whether the
source is still used in project budgets and whether documents or tasks
must be retained.
The three actions only appear if you are allowed to perform them on the
respective source; who may do what is listed under
Visibility and permissions.
Use View history to see when and by whom data was changed. This is
particularly useful when a title, amount, or responsibility has changed
unexpectedly. Changed periods are not listed there; what it records is
described under
Follow the history.
Do not use the source amount as a correction entry
If a budget position is missing or assigned incorrectly, correct it in the
project budget. Change the initial amount only when the approved or allocated
volume itself has genuinely changed.
Sources of Funding
Projects & budgets
Permit projects, assign positions, and understand the funding evaluation
A funding source and a project budget are connected in two stages. First,
permit the project on the source. Then assign the appropriate budget
positions in that project to the source.
Open the source and expand Funded projects in the side panel. Use the edit
button to search for projects or choose from recently used projects. Remove a
project from the selection when it should no longer be linked, then save the
list. The edit button is only shown to people listed on the source under
Responsible or Write access, and to admins.
Permitting a project does not change any amount by itself. It determines
which projects may select this funding source later in their budgets. This
helps prevent the fund from being used in unrelated projects by mistake.
Next, open the budget of the permitted project. Assign the relevant cost or
income positions to the funding source. The exact budget view and column
depend on your organisation's budget structure.
Add the project under Funded projects on the funding source.
Open the project and navigate to the appropriate budget tab.
In the row, open the Cell Details via the plus icon of the value cell and switch to the Linking tab.
Enable Link to funding source, search for the source and choose whether the value counts as Expenses or Revenue.
Save, return to the source and check the remaining amount and project total.
The search on the Linking tab only finds sources that list the current
project under Funded projects. If the column is locked, the link cannot
be changed.
Besides individual cells you can also link sums: the sum of a sub position,
of a main position, or the overall sum of expenses or revenue. Open the
Sum Details of the respective sum cell and switch to the Linking tab
as well. For sums, the choice between Expenses and Revenue decides
whether the value is deducted from the source or added to it.
One cell counts per row
If several cells of one budget row are linked to the same source, Artwork
only counts one of them: the cell in the column marked Relevant for
budget, otherwise the cell in the rightmost column. This prevents an
amount from being counted twice when the plan and the actual column carry
the same link.
The detail page shows the original volume and the calculated still
available amount. A bar also visualises the percentage used.
A cost position uses the source and reduces the available amount.
An income position is included positively.
A negative or exhausted remaining amount is highlighted in red. The
amount is also red once a
remaining-budget reminder
has fired; Threshold reached is then shown next to it.
Consumed always lies between 0 and 100 percent, even if the source is
overdrawn or income lifts the available amount above the initial volume.
On a funding group, positions from the member sources are combined.
Totals per project shows the balance for every linked project. The bars
relate each project total to the initial volume: green for a positive
balance, red for a negative one. Use the project filter to limit the
position list to one project; Totals per project then shows only that
project as well.
Is the expected project listed under Funded projects?
Is the specific budget position assigned to the correct source?
Is the position recorded as a cost or income?
Is the correct value in the relevant budget column?
Is the project filter currently limiting the view to one project?
Are you viewing a group while expecting figures for only one member
source?
A project link without assigned positions does not use any money. Conversely,
remove a source from a project only after its existing assignments have been
resolved.
Correct the source or the project?
Change master data such as funding volume and period on the source. Correct
costs, income, budget columns, and the funding assignment on the relevant
budget position in the project.
Sources of Funding
Collaboration
Use access roles, tasks, reminders, files, and history
The side panel on the detail page brings together all information needed for
ongoing work on a funding source. Its individual sections can be expanded and
collapsed. The edit buttons of the sections, and downloading, editing and
deleting documents, are available to everyone who may edit the source
Coming with the next update: people listed on this source under
Responsible or Write access, the creator, people with Manage
sources of funding, Delete all sources of funding or Global budget
access, and admins.
Person with subject-matter responsibility for the funding source
Write access
Person permitted to edit the master data of the source and to maintain the side panel
Use the edit button to find additional eligible users, remove existing
assignments, or enable Responsible and Write and delete permission for
each person. Both can be enabled for the same person. Responsible people are
shown separately in the overview.
In the Manage release dialog the two checkboxes are called
Responsible and Write and delete permission. The source itself can
nevertheless only be deleted by its creator, admins and people with the
permission Delete all sources of funding or Global budget access.
The search finds all active users. A listed person can only open the source,
however, if their account has the permission Manage sources of funding.
Conversely, this permission allows editing the master data of all sources,
independently of the individual list.
People receive a notification when they are added to or removed from the
source during creation or via Edit; this change is also recorded in the
history. Changes in the Manage release dialog do not trigger a
notification.
Edit sets both sharing roles
When you save the master data via Edit, all people listed there under
Who is responsible? receive both roles again, Responsible and
Write access. A distinction you made in the Manage release dialog
has to be set again afterwards.
An assignment does not guarantee a notification
Adding a person to Sharing controls editing. Agree internally
who monitors funding conditions and who only makes changes when required.
Use Tasks for concrete actions such as “Submit interim report” or “Review
proof of use”. A task contains:
a title,
a due date and time,
an optional comment,
one or more assigned people.
The people selected in the dialog are assigned to the task when it is
created. If you select nobody, the task goes to the responsible people of
the source. Open and completed tasks remain visible on the source.
Authorised users can tick them off directly and revert the completion;
overdue open tasks are highlighted. The Sources with open tasks filter
in the overview finds sources and groups with open tasks
Coming with the next update (see
Narrow down the overview).
Changing the sharing reassigns tasks
When you save the sharing of a source again via the edit button, all tasks
of this source are assigned to the responsible people listed at that point.
A differing assignment of individual tasks is lost. Check the tasks after
changing the sharing.
Assigned tasks also appear — with the avatars of the assignees — as the
collapsed subcategory Funding source tasks in
My To-dos.
Two types of reminder can be enabled while creating an individual source.
They are not available for groups or in the edit dialog of an existing
source. The notification goes to the people listed on the source as
Responsible. If nobody is listed, the reminder still counts as
triggered and nobody is notified. Each reminder triggers only once.
Enable Remind me when this source runs out and enter how many days in
advance the reminder should occur. You can add several times, such as 90,
30, and 7 days in advance. The field Funding period End is decisive, not
the end of the runtime. As long as this date is missing, no reminder is
sent. Artwork checks the deadlines once a day during the night.
Enable Remind me when only a certain percentage of the source still
exists and set one or more percentages. Artwork triggers a threshold
notification as soon as less than that share of the source remains
available. For example, 20 percent warns when less than one fifth of the
initial volume remains. The check runs when a budget value linked to the
source or a link changes. If several thresholds are undercut at once, you
receive one notification for the lowest; the higher ones then count as
done.
On the detail page, Expiration warning sent and Threshold reached show
that a configured condition has been triggered. Use several thresholds when
different escalation stages are useful.
Basis of the remaining-budget reminder
The threshold uses the available amount calculated in Artwork. Missing or
incorrectly assigned project positions can therefore also distort the
reminder.
Use Documents to keep files directly on the source, such as grant
decisions, conditions, cost plans, or reports. Authorised people can upload,
download, edit, and delete files.
In the Upload document dialog you select one or more files and can add
a comment. A click on the file name opens Edit document: there you
replace the file with a new version (Replace document), add another
comment and read the previous comments. A document cannot be renamed; the
name shown is always the file name of the version uploaded last. The file
types and the maximum size of the Project area in the
File settings apply.
Use descriptive file names and distinguish versions clearly. Store
source-specific material here; project-specific files should remain in the
relevant project.
Select View history in the header to open the change log. Where available,
the list also shows the latest change with its time and person. Use the
history when master data differs from what you expected, but do not treat it
as a substitute for checking the original funding documents.
The history records: the creation of the source, changes to title, initial
amount and note, uploaded and deleted documents, and people added or removed
via Edit. It does not record changes to runtime and funding period, to
origin and group, to funded projects, categories and tasks, or the links in
the project budget.
Name at least one responsible person for each source.
Grant write access only to people who actively maintain the data.
Use tasks for concrete deadlines and reminders for automatic warning points
based on time or remaining budget.
Store funding documents on the source and project-specific evidence in the
project.
Review categories and permitted
projects regularly, especially for copied or newly grouped sources.
Sources of Funding
Settings
Centrally create, assign, and safely remove funding-source categories
Under System → Sources of funding, you manage the categories used to
filter sources and classify them consistently across the organisation. The
page requires the separate permission Sources of funding settings (module
System settings). These categories belong to the funding module and are
therefore documented in this chapter.
Create categories for stable characteristics such as funding type, provider,
business area, or programme. Enter the name under Enter Category and
confirm with the check mark or the Enter key. A name must not be empty and
must not contain leading or trailing spaces; otherwise Artwork rejects the
entry with a notice. Each name can only be used once
Coming with the next update: for a name that already exists, A source category
with this name already exists. appears and the category is not created.
Keep the set small and use unambiguous names. Similar values such as “Local”,
“Municipal”, and “City” make filtering and reporting unreliable.
An existing category cannot be renamed. If it should have a different
name, create a new category, assign it to the affected sources and then
delete the old one.
To delete, click the X on the category and confirm the prompt. This
permanently removes all category assignments; the funding sources
themselves remain. Before deleting, use the category filter to identify the
affected sources.
Deleted assignments cannot be restored from the recycle bin
Deleting a category removes its links. Document larger cleanups and review
the affected sources afterwards.
Users & Teams
Overview
Distinguish internal accounts, external workers, teams, and permissions
The Users area manages more than people with their own login. It also
brings together freelancers, service providers, teams, permissions, and
work-related data. Artwork uses this information in projects, shift plans,
checklists, access assignments, and notifications.
Internal staff and other people who work in Artwork themselves
Freelancer
No
External individuals who can be scheduled and given availability, terms, and qualifications
Service provider
No
Companies that can be scheduled as one unit and may contain several contacts
Creating a freelancer or service provider does not grant access to the
application. An internal account is created through an invitation followed by
registration by the invited person.
Search, sort, open, invite, deactivate, and manage internal accounts
Freelancers & Service Providers
Search, filter, create, and edit external people and companies
Teams
Departments or work groups with members and their own icon
Permission presets
Role presets as reusable collections of individual permissions
Permissions explained
Printable read-only overview of all permissions and their effect
Visible tabs and actions depend on your permissions. Inviting, editing other
people's profiles and deactivating accounts require HR administration,
teams require Team administration. Creating and editing freelancers and
service providers requires at least External worker administration; the
tab is also visible to people who may view or plan duty rosters or see
private contact details. Permission presets, a person's user rights and
permanent deletion are reserved for artwork admins; Permissions explained
is available to admins and HR administration.
Team membership can affect visibility in projects assigned to that team.
Crafts and qualifications determine where a person is offered and can be
assigned in the Duty roster.
Work patterns, contract rules, absences, and substitute days off contribute
to target hours and rule checks.
Permissions control not only menu entries but also individual actions
inside an area—and are checked on the server as well.
Handle personal data carefully
Contact details, pay, contract values, and time accounts may be sensitive.
Grant management permissions only to the responsible people and use the
private switches for email and phone when they should not be generally
visible.
The Users tab shows names, email addresses, positions, and team
memberships. Select a person to open their profile—depending on your
permissions, initially on their operation plan or personal data.
Search uses the person query you enter. Sort changes the order, while
Reset removes your saved sorting. Artwork remembers this choice for your
own view.
For people in several teams, the table initially shows only some team icons.
Open the additional selection to see the complete list. A warning badge
Work time pattern missing marks people who work shifts but for whom no
target hours can be calculated.
Accounts that sign in via LDAP or OIDC carry the label SSO next to the
name. If such a connection is active, SSO only narrows the list to these
accounts. Deactivated accounts are not in the list but under Deactivated
(see Deactivate account).
Invite new users is visible to artwork admins and people with the
permission HR administration. The dialog can prepare several email
addresses with the same team and permission settings at once.
Enter email addresses. Separate several addresses with spaces, commas, or semicolons. Press Enter, click the check mark next to the field, or leave the field to add them.
Review the recognised address chips and remove mistakes.
Optionally use Assign to teams to select teams that all invited people should join immediately.
Under User permissions, apply a role preset or select individual permissions. Admins additionally see the admin role above it under Define user permissions; when it is ticked, the selection of individual permissions disappears.
Send the invitation. Each person receives their own invitation email.
The dialog does not accept addresses that are invalid, entered twice, or
already used by an account, and states the reason below the input field.
Review the messages before sending. If an address belongs to a deactivated
account, Artwork rejects the invitation on sending; reactivate the existing
account in that case. An address that already has an open invitation is
accepted without a message, however: the new invitation replaces the old one
including its permissions and teams, and the earlier link stops working.
Teams that are room admin of a room can only be passed on by someone with the
permission Room administration. Without it, such a team is left out of
the invitation without any feedback.
An invitation is valid for seven days. If the link is opened later,
Artwork shows the page Invitation expired and asks the person to request
a new invitation. There is no list of open invitations. To invite again,
enter the address in the dialog once more and set teams and permissions
again; the invitation is then valid for seven days again. Seven days after
its validity has expired, Artwork deletes an invitation that was not
accepted Coming with the next update; the old link then leads to an error
page.
The invitation dialog uses the same permission view as the user rights page:
modules in menu order, with a Role preset selector at the top. An
invitation may include:
a role preset (permission preset) whose permissions are added,
individually selected permissions,
team memberships,
the admin role—only artwork admins can grant it.
Inviters can only pass on permissions they hold themselves. If a role preset
contains permissions the inviting person lacks, those are not included. In
that case, have the invitation sent by someone with the appropriate
permissions or by an admin. See
Roles & permissions for role presets
and individual permissions.
The link in the invitation email opens the page Accept Invitation. The
person enters first name, last name, phone number, position, and password.
The email address is taken from the invitation and cannot be changed.
Company is prefilled with the name of your organisation; the field carries
an asterisk but may stay empty. First name, last name, and password are
required. The password must be confirmed and contain at least ten characters
with upper- and lower-case letters and at least one digit.
Register creates the account. The person is then signed in right away and
lands on the dashboard; there is no separate email confirmation step, because
accounts are created only through invitations, LDAP, or OIDC. The teams and
permissions prepared during invitation are available on the account
immediately. Later they sign in with their email and chosen password.
Inviting is different from creating a freelancer
An invitation creates an account with a login. Create a freelancer instead
for someone who only needs to appear in shift planning and will not use
Artwork personally.
Depending on permission, a profile provides these tabs:
Operational plan
Personal data
User permissions
Work profile
Contract & working hours
Work Times
Substitute days off
Overtime
Users maintain their own contact details and preferences themselves. Contact
details and team assignment of other people, as well as work-related staff
data, are edited by people with the permission HR administration. Reserved
for artwork admins are: editing accounts with the admin role, changing another
person's email address, because it is the login and the target of password
resets, and the profile image, name and application language in other
people's profiles (see
Personal data).
Private contact details the editing person is not allowed to see remain
unchanged when saving.
On the profile, an artwork admin can select Reset Password under
Security. The affected person receives an email for choosing a new
password. Never ask for or share the old password.
Users can also request the link themselves via Forgot your password? on
the login page. Artwork confirms the dispatch regardless of whether the
address is known and limits the number of requests.
Changing your own password is described under
My account.
A deactivated account is suspended but not deleted. Rights, settings and all
assignments to projects and shifts are kept, and the account can be
reactivated at any time. This is the right way for people who leave, are
absent for a longer period or will return later.
In the Users tab, open the person's action menu and choose Deactivate account. Alternatively, use the Account status block under Personal data in the profile.
Confirm the prompt with Deactivate.
Artwork admins and people with the HR administration permission may
deactivate and reactivate accounts. Admin accounts can only be deactivated by
admins. Nobody can deactivate their own account.
Area
What deactivation changes
Sign-in
The person can no longer sign in, not via SSO and not in the app either. Running sessions end. A sign-in attempt shows a notice that the account is deactivated; Forgot your password? sends no link for the account.
Notifications
No more e-mails, hints or summaries are sent to the person.
Calendar subscriptions
Subscribed calendars no longer deliver data.
User list
The account is no longer in the list but under Deactivated, with the note "Deactivated on … by …". Only HR administration and admins see the button, and only while deactivated accounts exist.
People search
The person no longer appears in people searches and therefore cannot be newly assigned.
Existing assignments
In project teams, shifts and similar places the person stays visible: with a grey profile picture and the note Account inactive instead of the e-mail address.
Duty roster
The person only appears while they have shifts in the displayed period. From the day of deactivation no more target hours accrue for them.
To reactivate, open Deactivated in the list and choose Reactivate
account in the action menu, or use the Account status block in the
profile. The person then signs in with their previous credentials. API keys
and app sign-ins stay stored during the deactivation and work again after
reactivation.
Deactivate instead of delete
Deleting removes assignments and cannot be undone. Deactivate an account if
you only want to block access.
Only artwork admins can delete: via Delete user in the action menu of the
user list or via Permanently delete user at the end of the User
rights tab. The action requires confirmation and is marked as permanent.
Nobody can delete their own account.
When deleting, Artwork removes the person's team and project memberships,
crafts and qualifications. What they created or were involved in, such as
events, rooms, projects, comments, tasks and shift assignments, is
transferred to a placeholder entry ("Deleted user"). Working time bookings,
notification settings and calendar subscriptions are deleted.
Before deleting, review at least:
open tasks and responsibilities,
project and team assignments,
planned shifts and time accounts,
responsibilities for funding sources or approvals,
whether permissions should simply be removed and work handed over instead.
Deleting an account is not a suitable way to suspend someone temporarily or
remove them from a team. To block access, use
Deactivate account.
Users & Teams
Profiles & work data
Maintain personal data, scheduling capability, contract & working hours, key figures, and time accounts
An internal user's profile connects contact information with the data needed
for shift and working-time planning. Not every tab is visible to every role:
Operational plan, Personal data, User permissions, Work
profile, Contract & working hours, Work Times, Substitute days
off, and Overtime.
Tab
Visible to
Operational plan
In your own profile with View own roster; in other profiles with View duty rosters, Plan shifts or HR administration
Personal data
Everyone
User permissions
artwork admins
Work profile, Contract & working hours
HR administration
Work Times, Overtime
HR administration; only while work time accounting is switched on in the shift settings
Substitute days off
Plan shifts
artwork admins see all tabs. If the account is deactivated, the profile
header shows the note Account inactive (see
Deactivate account).
Personal data contains the profile image, first and last name, pronouns,
company, position, email address, phone number, and a free description. It
also shows the person's teams. The Position is a free text field.
People change their own data themselves, except for the email address. In
other people's profiles the following applies:
Pronouns, company, position, phone number, description and the checkboxes
under Preferences are edited by people with the HR administration
permission.
Profile image, first and last name and the Application language of
another person can also be changed by people with HR administrationComing with the next update.
The email address can only be changed by artwork admins. Profiles of
artwork admins can likewise only be edited by admins: with HR
administration you see their fields, checkboxes and team assignment
locked there, and the interface does not offer the name card, profile
image and language Coming with the next update.
Team membership is changed by people with Team administration or HR
administration via Edit team membership.
The Account status block for deactivating and reactivating is shown to
people with HR administration and artwork admins, but never in their own
profile.
Email and phone visibility, language, chat, and contrast are personal
settings described under My account.
The Operational plan tab shows the person's shifts over time. Depending
on permission, availability, absence or vacation, and temporary employment
can also be maintained there.
The person sees the Availability area below the operational plan in
their own profile. In other people's profiles it only appears with the
permission Manage availability of others and for artwork admins. New
entry creates an entry Available or Absent: for one day or a
period (one entry per day is then created), All day or with times. A
single day can be turned into a series with Repeat weekly and Ends
on.
Temporary employment is labelled Temporarily employed in the interface.
Only people with HR administration and artwork admins see the switch; a
start and end date are stored with it. The information is a note in the
profile. It blocks neither scheduling nor login outside the period.
Availability and absence may cover single ranges or recurring entries. They support planning but do not
automatically replace a formal approval. If the person is scheduled despite
an absence, the absence list shows the conflict with the assigning person
and the note Assignment made on …. See the
Shift plan manual for scheduling and conflicts.
The work profile defines professional scheduling capabilities:
Setting
Effect
Job title / Job description
Describes the person's professional role
Show as freelancer in the tool
Can additionally flag an internal account in relevant external views
Default project roles
Assigned automatically when the person joins a project team
May be assigned to shifts
Controls whether the person appears as schedulable staff
Global qualifications
Organisation-wide skills of the person
Crafts
Professional areas in which the person can be scheduled
Craft functions
Qualifications within a craft; they determine which function (slot) in a shift the person can take
To appear in suitable shift selections, a person must be schedulable and
match the required crafts and qualifications. Shift planner for instead
describes the crafts whose planning the person may see or edit; it is not the
same as their own qualification. Whether the person may accept or decline
their own shifts is controlled by the permission Accept or decline
shifts under Roles & permissions.
The Contract & working hours tab combines employment contract and work
time pattern in one timeline. Each assignment has a Valid from and
Valid until (empty = open-ended) and thus forms a history. Calculations
use the contract valid on the respective day Coming with the next update: the
overtime deadline, the special-day switch, the three-month average and the
rule checks (details under
Rules & violations).
If the contract changes within an evaluation period, Artwork calculates the
target values of the key figures and the vacation entitlement pro rata by
calendar days; days without a contract count as 0.
Plan change sets a new contract and/or a new work time pattern from a
date. For each part you choose separately what should happen: Keep
contract, Select contract template, Individual values or End
contract, and Keep working hours, Select Work Time Pattern or
Custom weekly hours. The previously open contract period is closed
automatically the day before. If the date lies in the past, Artwork
re-checks the committed shifts of that period against the rules. Each period
can be edited later or removed via Delete period; the rules are
re-checked for the affected period in that case too.
Keep in mind:
Contract periods must not overlap. If the new period collides with
another existing one, Artwork refuses to save and names the affected
period. Adjust the dates or edit the existing period.
Working-hours periods are not closed automatically. If two overlap, the
period with the later Valid from applies on each day. If the new
period has a Valid until, the older open period applies again
afterwards.
Days already booked to the time account do not change by themselves after
a retroactive change (see Rebooking days).
If work time accounting is switched off in the shift settings, working
hours are stored but not used for target hours, the hours account or
overtime. Contracts still decide which shift rules apply.
Without a contract, no rule check applies to the person and there are no
season figures; without a work time pattern there is no daily target for
the hours account and overtime.
In the contract part you choose a Contract template or Individual (no
template). The template opens with a click into the field. Its values are
copied and can differ per person; inherited values carry the suffix (from
template), deviations are counted as chips. While a template is selected,
a 0 in a number field counts as "not set": the template value then applies.
You therefore cannot lower a template value to 0 for a single person; the
switches (checkboxes), in contrast, always apply as set on the period. The
values include:
Free full days per week and Free half days per week – they are
also key-figure targets per season half,
Compensation period (in days),
Overtime rule active with the period within which overtime must be
reduced,
season-related targets such as free Sundays per season, free Sundays with
Saturday/Monday per season half, free Sundays per calendar year, days off
in the first 26 weeks of the season, and 1.5-day combinations. You switch
each of these targets on with a checkbox and then enter the Minimum
value (X).
Contract templates and the rules bound to them are maintained by admins
under System → Shift settings (see
Rules & violations).
The work time pattern is the only source for the target. Choose a
centrally prepared pattern or Custom weekly hours (no pattern) and enter
the hours per weekday (08:00 = 8 hours, not a start time). While a pattern
is selected, the daily values cannot be edited freely; remove the pattern if
this person needs individual times.
There is no longer a separate field "hours per week according to contract".
If a pattern is missing, the target is unknown – not 40 hours: the
operational plan header and the calendar-week tile show "–" with the badge
Work time pattern missing, and the user list marks schedulable people
without a valid pattern with the same warning badge.
A public holiday counts as a special day if it carries the flag Treat as
special day in the
event settings.
This one definition applies to rule checks, weekly target, hours account,
and the nightly booking; school holidays without the flag never reduce the
target.
Whether special days affect a person is decided by the contract switch
Special day rule active: when active, a special day without work
reduces the daily target to 0; when inactive, the normal daily target applies
on every day (for example for contracts where public holidays do not
matter). If a shift or individual time starts on the special day, the
normal daily target stays in place and the hours count as on any other day.
The remainder of a night shift that started the day before does not cancel
the reduction; those hours count as a plus.
The option Use three-month average for target-hour reductions on the
contract template changes how much a special day or a compensation day for
public holiday reduces the target: instead of dropping to 0, the daily
target is reduced by the average actual hours of the same weekday over the
three completed previous months. Only days with recorded work are counted,
sick days and vacation days are left out; if no eligible working day
exists, the pattern target applies. The reduction is never larger than the
daily target. The hours account shows per day in the tooltip which value was
applied. The option exists only on the contract template; with Individual
(no template) it is not available. Whether the option applies on a day is
decided by the contract valid on that day; on days without a contract it
does not apply Coming with the next update.
Hours & remuneration shows the weekly hours according to work time
pattern (read-only) as well as hourly pay and additional notes. Because
this information is sensitive, access is restricted to people with HR
administration. For freelancers and service providers this is the
Conditions tab. In the profile of internal users this tab is currently
not part of the tab bar.
The Work Times tab compares Daily target, Planned, Worked,
and Balance per day, with a Monthly Breakdown for longer periods.
Use Book working hours to add a post-entry, for example for hours worked
outside shifts and individual times.
The Book working hours dialog asks for:
Booking type: Add hours or Deduct hours,
the duration as Hours and Minutes; more than 24 hours is
possible, such as 150:30 for a collective booking,
Of which night hours, also in hours and minutes; they must not exceed
the booked duration,
a date that is not in the future, and a comment (required).
A preview line shows by how many hours the time account changes. Invalid
entries (minutes outside 0–59, zero duration, night hours above the
duration) block saving. The time account can also become negative as a
result. If the person has no work time pattern, the target shows “–” with
the note Work time pattern missing.
Target and actual are calculated with one and the same method everywhere –
the calendar-week column in the duty roster, actual hours in the key-figure
window, the hours account, and the nightly booking therefore match. Sickness
and vacation are target-neutral, special days reduce the target according
to the special day rule. Multi-day individual times are split by day and
not counted twice; an all-day individual time counts at least the daily
target.
Hours appear uniformly as signed H:MM h with the tooltip Planned ·
Target · Difference. Markers in the hours account indicate special day,
vacation, sickness, substitute days off, and night work.
A difference is initially a prompt to review, not automatically a payable
positive or negative balance.
The time account does not change by itself when a past day changes
afterwards, for example through a sick note, a changed shift time or a work
time pattern created later. Such days carry the note Differs from time
account or Not in time account in the Work Times tab; the tooltip
states the difference. Above the period you see how many days are affected
and by how much the time account would change.
With Rebook on the day or Rebook all n days above the list you apply,
after a confirmation, the current state from shifts, absences and work time
pattern. The existing daily booking is replaced; manual bookings remain. This
requires HR administration and only works for people who may be assigned to
shifts; at most 366 days can be rebooked at once. Check the differences
before you rebook all days.
Days marked Booked twice have more than one daily booking from legacy
data; rebooking does not correct them. Days before the first daily booking
are marked Before the start of the time account and only show the hours
actually worked, without target and balance.
Planners open the Key figures window via the info button in the staff
panel of the duty roster; employees see the same values read-only under
My key figures in
My operational plan.
The tabs are Season-related data, Substitute days off,
Vacation, Actual hours (with month navigation), and Overtime.
The last two exist only while work time accounting is switched on in the
shift settings.
The target values come from the person's contract assignment, per
evaluation period (season, season half, calendar year, first 26 weeks)
from the contracts valid there Coming with the next update. If the contract
changes within the period, each contract value is weighted by its
calendar days; days without a contract or with the target switched off
count as 0. A target counts as active if it was active on at least one
day of the period. Likewise, the vacation entitlement in the Vacation
tab results from the contracts of the calendar year. Rows
without a target are hidden by default and can be shown via Show n more
key figures without target value.
The tooltip of each key figure names the counting rule; Last nightly
calculation shows when the values were last calculated.
Only completed days are counted, that is up to and including yesterday
(Counted until). The Vacation tab, in contrast, also includes
future vacation already entered for the calendar year.
The overtime account appears as a badge with sign, for example "+10:30 h".
Key figures: free Sundays per season and per calendar year, free Sundays
connected with Saturday/Monday per season half, free Sundays + Saturdays,
Full free days (day without shift and without individual time; shifts
past midnight occupy both days), Granted half free days, 1.5-day
combinations, Days off in the first 26 weeks (counted from the start
of the season), and granted vacation days in the calendar year. The
targets for full and half free days are "free full/half days per week"
times the weeks of the season half.
Free Sundays are counted more strictly than full free days
The Sunday figures, the 1.5-day combinations and the days off in the first
26 weeks only treat a day as a full free day if there is a free-day entry
or a granted substitute day off, if both half days are free, or if the day
was a working day according to the work time pattern without a shift and
without an entry. A Sunday on which the pattern has no work anyway
therefore only counts as a free Sunday with a free-day entry. For the key
figure Full free days, any day without a shift and without an
individual time is enough.
Without a season the calendar year applies
If no or an invalid season is stored under System → Tool settings →
Communication & Legal, key figures, My key figures, and the BI
module use the current calendar year.
Open compensation days (entitlements with deadline),
Granted compensation days,
Unprocessed violations from the rule check.
Add compensation day creates an entitlement as a full day (1.0) or half
day (0.5). The Deadline is required, the Reason optional. A
Compensation day for public holiday reduces the daily target once it is
granted, on the granted date; a half day reduces it by half. Open
entitlements can be granted or deleted; granted days can be revoked or
deleted. Deleting requires a Reason for deletion. Once the deadline of
an open entitlement has passed, it is marked Deadline expired. For rule-based entries, the triggering
rule remains visible. The complete flow from rule to granted day is
explained under
Rules & violations and substitute days off.
The Overtime tab shows the person's account, deadlines, and payouts.
Changes should be made only by responsible staff and reconciled with the
underlying work-time data. If the overtime rule is switched off in the
contract, the overtime account with all open and compensated overtime is
kept.
At the top you see Time account, Open overtime and Minus hours;
the time account is the difference between the two. Below, the History
shows per month on which day overtime or minus hours accrued and how they
were compensated. Offsetting follows a fixed order: a plus day first
compensates open minus hours, a minus day first reduces the overtime with
the earliest deadline.
With Overtime rule active, each overtime hour gets a deadline from the
contract. Whatever is not compensated by then appears under Deadline
expired and can be paid out. Without the rule there are neither deadlines
nor payouts. If the rule is active but no period is stored, the tab points
this out; nothing becomes payable then.
The Pay out overtime block only appears with the permission Pay out
overtime, with an active rule, and when expired overtime exists. You enter
Hours, Minutes and optionally a Comment. At most the expired
overtime can be paid out, and never more than the positive account balance.
The booking always carries today's date and reduces the time account; the
actual payment happens outside Artwork.
Recommended setup order
First maintain work profile and schedulability, then work time pattern and
contract with validity period under Contract & working hours. Only
afterwards can target hours, rule checks, key figures, substitute days off,
and overtime be interpreted reliably.
Users & Teams
External workers & teams
Manage freelancers, service providers, contacts, and team memberships
The Freelancers & Service Providers tab contains external individuals and
companies. Search by name and filter via All available addresses, All
freelancers or All service providers. Sorting is saved for your view
and can be reset.
The tab is visible to people who may view or plan duty rosters or who hold
one of the permissions HR administration, External worker
administration or View private contact details.
Creating, editing, and deleting requires the permission External worker
administration—including terms, work profile, and absences, but without
access to the profiles of internal colleagues. HR administration includes
this permission. People who may view or plan duty rosters or see private
contact details can additionally open the profiles.
Select Add new Address, choose the type, External employee or
Service provider (company), and go to the second step with Continue:
For a freelancer you enter first and last name; both are required.
Complete the remaining data on the profile.
A service provider initially needs a Company name.
After Create freelancer or Create service provider the new profile
opens directly. Artwork automatically creates the matching CRM contact (see
Contacts & projects). Neither type
receives an Artwork login.
Depending on permission, a freelancer has these tabs:
Operational plan, including availability, absence, and temporary
employment,
Personal data, including image, name, company, position, email, phone,
address, and note,
Conditions, including hourly pay and additional notes,
Work profile, including schedulability, crafts, and qualifications.
The Operational plan is visible to people with Plan shifts,
Conditions and Work profile to people with External worker
administration or HR administration. Personal data is visible to
everyone who may open the profile. The same applies to service providers.
For a freelancer to be offered in suitable shifts, schedulability, crafts,
and required qualifications must all match. External workers do not take part
in the accept/decline flow for shifts.
A service provider is held as a company. Company data contains company
name, image, address, email, phone, and notes. You can also create, edit, or
remove several contacts with first name, last name, email, and phone.
Depending on permission, other tabs provide operational plan, conditions,
and work profile. The service provider appears as the schedulable unit; its contacts
support communication and are not treated as individual shift workers.
Delete freelancers and service providers from their list action menus
(Delete freelancer, Delete provider). The action menu in the list is
shown to artwork admins and to people with External worker administration or HR
administrationComing with the next update. First
review shifts, availability, contacts, and other links. Deleting a service
provider affects the company record; remove a single contact directly from
the company profile instead.
Teams represent departments or work groups. Names and icons identify them in
people lists, projects, and selections. One person may belong to several
teams.
Membership is more than visual: users can gain access to projects assigned to
their team. It does not automatically replace all global permissions or
project-specific roles.
In practice a team takes effect in two places:
Projects: If a team is assigned to a project, all members can open and
edit the project, even without their own entry in the project team.
Restrictions on individual components still apply.
Rooms: If a team is entered on a room as room admin or for requests,
all members count like directly entered people (see
Rooms, areas & booking access).
Adding a person to a team or removing them therefore also changes their
access. The person receives a notification about it.
The permission Team administration allows creating, changing, and
deleting teams as well as adding and removing members. It does not edit other
people's profile data such as contact details; that belongs to HR
administration. Your own team membership can only be changed by another
person, artwork admins excepted. This already applies on creation: you
cannot add yourself to a new team.
For teams that are room admin of a room, Team administration is not enough
to change members or remove all of them. You additionally need Room
administration; otherwise the note "Members of teams with room admin access can
only be changed by people who may edit rooms." appears.
Open a new team with Create Team from the Teams tab.
Choose a clear icon and an unambiguous team name. Both are required; the button stays disabled until then.
Use person search to add the first members.
Create the team and open its profile.
Change its name, icon, and members when required.
The team profile has no save button for name and icon: the name is applied
as soon as you leave the field, the icon when you select it.
The team profile lists members and their positions. Remove individual people
or add others through Edit team. Conversely, user profiles provide Edit
team membership and Remove user from all teams.
Remove all team members keeps the team but removes every membership.
Delete Team in the action menu of the team list, or Delete team
permanently in the team profile, removes the team itself.
Both require confirmation. Before deletion, check whether projects or other
processes still use the team as a responsibility.
A deleted team is removed permanently; it does not go to the recycle bin.
Its assignments to projects and rooms disappear with it, and members lose
any access they only had through the team. All members are notified of the
deletion.
Team, craft, and project role are different
A team describes organisational membership, a craft describes professional
schedulability, and a project role describes a function in one specific
project. They often align, but each grants different visibility and actions.
Users & Teams
Roles & permissions
Understand the user rights page, apply role presets and grant permissions per module in a controlled way
Artwork combines the admin role with individual permissions. This lets
you provide broad responsibility or restrict access to specific areas and
actions. A person's permissions are maintained on their profile under User
rights; only artwork admins can open that tab.
Whether a person can see or do something is decided by several layers in
turn:
artwork admin – can do everything, in every module and every setting.
Module switch – a module disabled under
Module visibility is
hidden for everyone, regardless of permissions.
Global permissions – the permissions on the user rights page.
Project team – write, delete and budget access per project, plus the
project-manager flag.
Tab and component permissions – can only restrict access within a
project, never extend it.
Since version 1.7.7 Artwork also checks permissions on the server in every
area. Anyone who opens a function through a direct link without the required
permission sees an error page stating No permission.
The artwork admin switch sits in the header of the user rights page.
Artwork asks for confirmation when you enable it, because the person can then
do everything, including granting rights to others. Individual permissions
remain stored and take effect again once the admin role is removed.
Only artwork admins can grant the admin role, also in the invitation dialog.
Grant it to a small number of explicitly responsible people. Do not confuse it
with a project role, which describes a function in one project only.
Permissions are grouped by module in the order of the main menu: Projects,
Calendar & events, Duty roster, Staff, Inventory & material issues, Documents &
contracts, Budget & funding, CRM, Business Intelligence, To-dos, System
settings and Interfaces. The Artwork-Tickets card only appears when
Artwork-Tickets has been set up for your instance. The page header summarises
how many permissions are granted and how many modules are disabled.
Each module card contains two kinds of permissions:
Levels build on each other, for example View duty rosters → Plan shifts
→ Commit duty rosters. A higher level automatically includes the lower
ones; when you remove a level that higher levels depend on, Artwork asks for
confirmation.
Additional permissions sit beside the levels and unlock individual
functions, such as View own roster or Open trash.
Every permission has a one-sentence effect ("Can …"). Clicking a
permission opens its effect card with the fields Unlocks, Allows,
Requirements, Includes, Typical for and Note, plus the number of people
who currently hold it. Requirements (another permission, a module switch, a
setting) are checked live against the person's current state. A permission
that is included in another one is greyed out as "included" and set
automatically.
The page offers these tools:
Element
Effect
Search
Filters by permission name and function in both languages
Only granted
Shows only the permissions the person already has
Apply role preset
Applies a permission preset with a preview (see below)
Same rights as another person
After a preview, adds the permissions the selected person has in addition; existing permissions stay. Only with the switch Also remove permissions this person does not have are the permissions set 1:1, and the preview then also shows what is removed
Select all / Deselect all
Grants or removes all permissions of a module in the header of its card
Change history
Logs every change with date, person and diff. The header shows "Last changed by … on …"; Show history next to it opens the list
Changes are saved directly; the save status is shown in the page header. The
fine-grained shift settings permissions sit in a collapsed section of the duty
roster card and only take effect with the shift setting Granular
permissions enabled.
Disabled module
If a module is switched off in the tool settings, its card is greyed out. The
permissions remain stored and take effect again as soon as the module is
enabled.
A permission preset bundles permissions into a role profile. Artwork ships
ten role presets: Basis (all staff), Production management, Disposition /
room planning, Duty roster planning, HR administration, Accounting /
controlling, Contract & document administration, Warehouse / inventory,
Artist relations / CRM and Box office / admission. There is no role preset
for system administration; that is what the admin role is for. Presets
customised by your organisation are kept during updates.
Every shipped role preset contains the permissions of Basis (all staff):
Read all projects, Request room occupancy, View own roster, Subscribe
to roster calendar, View day remarks, View contract modules and View
inventory.
Role presets are applied additively: the preset's permissions are added,
existing permissions stay. This works when inviting and afterwards on the user
rights page via Apply role preset, each time with a preview.
In the Permission presets tab of user management, administrators can
search presets, create a named preset with selected permissions, edit an
existing one and delete an obsolete one after confirmation. A preset is not a
separate account status; it helps set the contained permissions. After
changing a preset, check whether existing accounts also need adjustment.
The permission Accept or decline shifts is not part of any role preset.
Organisations with shift confirmation enabled grant it to the affected people
once.
The Permissions explained tab in user management shows all modules and
permissions with their effect cards as a read-only page, printable for
training and acceptance. People with HR administration and artwork admins
can open it. The complete, always current list of permissions lives there; the
following sections name the most important permissions per module.
The project list is visible to everyone; these permissions control opening
and editing. Access to a single project is also granted by membership in its
project team.
Permission
Effect
Read all projects (level 1)
Can open and read every project
Write all projects (level 2)
Can edit every project, even without being in the team. Edit restrictions on components do not apply; components that only certain people may see stay locked
Delete all projects (level 3)
Can move every project to the trash and delete it permanently; reaching the recycle bin additionally requires Open trash
Create own projects
Can create new projects and edit them afterwards
Can be project manager
Can be marked as project manager in a project team; grants no access to other projects
Anyone who can only read a project cannot edit its tab components. Editing is
allowed for team members with write permission or project manager, the
creating person, assigned departments and people with Write all projects.
Explanation boxes on the user rights page, in the preset dialog and in the
invitation dialog describe this interplay in place. Through the project
permissions, events of other people's projects can only be edited or deleted
by someone with write permission in the event's project; Can be project
manager is no longer sufficient. Independently of that, the person who
created the event, room admins of its room and people with Plan events
directly may do so.
Can book events directly, edit, decline and delete other people's events and answer room requests
View planning calendar
Can see the planning calendar and planned events
Edit planned events
Can edit, move, duplicate and delete planned events
Plan directly in the planning calendar
Can create planned events in all rooms; requires View planning calendar
View / Edit day remarks
Read or maintain the "Day remarks" column (only with the calendar setting enabled)
Calendar and planning calendar are permitted separately: Plan events
directly no longer includes Plan directly in the planning calendar.
Planned events are never room requests: View planning calendar only allows
viewing, creating them requires Plan directly in the planning calendar.
Whether a planned event may be confirmed depends on the verifier assignment
of the event type, not on these permissions. When
the setting Events always directly bookable is enabled, the user rights
page marks affected permissions as "No effect" or "Partially no effect". Room
admins have the same options within their own rooms without these
permissions.
The hint for the group sums this up Coming with the next update: creating
events requires one of the permissions to request, create or plan events, or
a role as room admin or requester in the room. In rooms that can be booked
by anyone, everyone who may create events books directly instead of sending
a request; the room setting itself does not grant a right to create events.
Can see all duty rosters, including shift history, exports and other people's rosters; required for "Show shifts" in the calendar
Plan shifts (level 2)
Can create shifts, assign people, manage substitute days off and record accept/decline replies on behalf of others
Commit duty rosters (level 3)
Can commit calendar weeks per craft; with the approval workflow enabled, submit a commit request
View own roster
Can open the own roster; without this permission it is not reachable
View own uncommitted shifts
Can see own uncommitted shifts although the shift setting Hide uncommitted shifts from own roster is enabled; requires View own roster
Accept or decline shifts
Can accept or decline own shift assignments (only with shift confirmation enabled)
Enter own individual times
Can create, edit and delete individual times for themselves in the own roster from today onwards; requires View own roster
Subscribe to roster calendar
Can subscribe to the own roster as a calendar (ICS)
View hour accounts
Can see working time accounts and weekly hours of others
View staff info data
Can open the info window per person in the duty roster; working times and overtime in it additionally require View hour accounts
Pay out overtime
Can book out expired overtime with a comment, always with today's date; reachable via the info window or, with HR administration, via the person's profile
Manage availability of others
Can maintain vacation, availability and individual times of other people
Shift settings
Can manage crafts, functions, templates, rules and the workflow
Which crafts a planning person may edit is set per craft in the
Shift settings.
Enter own individual times exists since version 1.9.0. With the update to
1.10.0, all people and permission presets with View own roster received it
once. Past days remain reserved for people with Manage availability of
others or Plan shifts.
Can maintain profiles, contracts and working times of others, invite people and deactivate or reactivate accounts; includes External worker administration
External worker administration
Can create, edit and delete freelancers and service providers, including conditions and absences – without access to in-house colleagues
Team administration
Can create and maintain teams; does not allow editing other people's profile data
View private contact details
Can see e-mail and phone marked as private; also opens the profile pages of freelancers and service providers
Other people's profiles are edited by HR administration, no longer by Team
administration. Accounts with the admin role and other people's e-mail
addresses can only be changed by artwork admins. Admin accounts can also only
be deactivated and reactivated by admins (see
Deactivate account).
Permanently deleting users and granting user rights is reserved for artwork
admins as well.
Can see the inventory overview and its articles; without this permission the menu entry Inventory is missing
Create & edit inventory (level 2)
Can create and edit articles
Delete inventory (level 3)
Can delete and restore articles
Inventory disposition
Can plan articles on events and manage material issues; opens the menu entries Article Planning and Material Issues and includes View inventory
Material issue log
Can see the change history of material issues; requires Inventory disposition
Create & edit sets / Delete sets
Can maintain material sets (tab "Material Sets" under System → Inventory)
Inventory settings
Can manage categories, properties, status, tags and manufacturers
View inventory is a permission of its own since the inventory overview is
no longer visible to everyone automatically. During the update, all existing
people and permission presets received it once; admins can remove it
selectively. Members of the project team with write permission create the
material issues of their project even without Inventory disposition.
Can create and assign requests, or edit and delete them and change their status; a person can always answer requests assigned to them by uploading a document, even without these permissions
Can read and maintain contacts; there is no read-only permission
Manage CRM (level 2)
Can manage contact types and properties, see all property groups, import and export contacts, merge duplicates, and restore and permanently delete contacts
Invite externals
Can invite external people to project tabs and their CRM contact
Invite externals only takes effect once the switch Activate external
access under System → External access is enabled; until then the
permission is marked as a disabled feature on the user rights page. See
External access for details.
Most of these permissions open their own entry in the System menu; the
table names the exceptions.
Permission
Effect
Tool settings
Can manage branding, mail, interfaces, module visibility and file settings
Project settings
Can manage categories, genres, sectors, status, tabs, components, print layouts and project roles
Event settings
Can manage event types, status, properties, holidays, BI tags and timeline presets
Calendar settings
Can change the calendar settings
Room administration
Can manage rooms and areas
Checklist templates
Can manage templates for to-do lists; includes Manage all to-do lists
Sources of funding settings
Can manage the categories of the sources of funding
Budget settings
Can manage general budget settings, accounts and cost units; the Budget templates tab additionally requires View budget templates or Edit budget templates
Open trash
Shows the menu item Recycle bin with the tabs Projects, Areas, Rooms, Events and Project Settings; the Shifts tab additionally requires Plan shifts. The tabs Articles, CRM contacts, Budget and Sage API data sets depend on Delete inventory, Manage CRM, Global budget access and the Sage permissions, the tabs Accounts and Cost Units on Budget settingsComing with the next update. Restoring and permanently deleting additionally requires the right to delete the project (Delete all projects or the delete permission in the project team) and, for areas and rooms, Room administration
System notifications
Can maintain the message to all; the button for it sits on the Notifications page, not in the System menu
Manage webhooks
Can manage webhook endpoints and their deliveries in the Interfaces tab of the tool settings; the other sections there require Tool settings. Without Tool settings the entry InterfacesComing with the next update in the System menu leads straight to this page
The Timeline presets page under Settings → Events requires Event
settings, Plan shifts or Shift settings.
Version 1.7.7 merged or removed permissions; existing holders were migrated
automatically:
"Global budget access without document access" has been merged into
Global budget access.
"Manage external worker conditions" has been replaced by External worker
administration.
"Can see, edit and delete all budget documents & contracts", "Use to-dos",
"Create events when creating a project", "Manage inventory stock" and
"Inventory planner" no longer exist.
Do not immediately delete the entire account. Removing a permission, team
membership or project-specific access is often enough. If a person should
not work in Artwork at all for a while or after leaving,
Deactivate account
is the right way: permissions and assignments are kept. When removing a level,
Artwork points out if higher levels depend on it. The change history documents
who made the change.
Users & Teams
My account
Manage your contact details, visibility, display, password, and browser sessions
Open your own profile via Your account in the account menu or by
selecting yourself in user management. It opens on the Personal data tab
and is headed My account. The exact placement of settings depends on your Artwork setup and
permissions.
Maintain first and last name, pronouns, company, position, phone number, a
description, and your profile image. The image appears in teams, project
responsibilities, tasks, and access assignments.
The Email field can only be edited by artwork admins because the address
is also your login. If you need a different address, contact an admin. An
admin who changes their own address confirms this with the current password.
Artwork then sends a confirmation link to the new address, valid for 60
minutes. Until it is confirmed, the old address stays valid, and "Confirmation pending" is shown
below the field. After confirmation, a notice goes to the previous address.
For accounts that sign in through your organisation's identity provider, the
address cannot be changed here.
When changing the image, select a file, review the preview, save it, or remove
the current image. Only image files (PNG, JPEG) are accepted as a profile
picture; the file must not exceed 3,072 KB.
Team memberships are visible on the profile but can only be changed by people
with HR administration, team administration, or admin rights. Even with these
permissions, your own team membership can only be changed by another person;
artwork admins are the exception.
Under Personal data → Preferences, the following options are available:
Setting
Effect
Application language
Switches the interface between the offered languages; emails from Artwork also arrive in this language
High contrast
Increases contrast, especially for event-type colours
Email private
Hides your email address from other regular users
Phone private
Hides your phone number from other regular users
Use Artwork Chat
Enables or disables chat for your account; only people with chat enabled can be found by others in the chat
Administrators or explicitly authorised roles may still need and be able to
see private contact details. Treat these switches as visibility settings
inside Artwork, not as a substitute for internal data-protection rules.
Many specialist views also have their own personal display settings, such as
calendar fields, duty-roster zoom, column widths, or saved filters. Those are
described in the relevant area and do not alter another user's data.
You set a new password via the link in the reset email. Request it with
Forgot your password? on the login page; the profile has no separate form
for changing the password. Admins can also trigger the email in the profile
under Security with Reset Password. A new password needs at least ten
characters with upper- and lower-case letters and at least one digit; an
existing password remains valid even if it does not meet this rule.
Never share your password.
On your own profile, the Security block lists your Active browser
sessions with device, browser, IP address, and last activity. Log out
other browser sessions ends every session except the current one after you
enter your password—for example after working on someone else's computer or
if you suspect unauthorised access. In that case, change your password as
well.
Signing in via OIDC/SSO
If you sign in through your organisation's identity provider, Artwork does
not remember the login permanently. When the session expires, sign in again
through the identity provider; your password is managed there. Because such
an account has no Artwork password of its own, other browser sessions cannot
be logged out here.
My account is your own user profile, opened on the Personal data
tab with master data, profile image, preferences and security.
You only see the Operational plan tab in your own profile with the
View own roster permission.
The tabs Work profile, Contract & working hours, Work Times and
Overtime require the HR administration permission, Substitute days
off requires Plan shifts.
Only artwork admins can open and change User permissions.
There is only one profile per account: changes under My account and in
the user profile affect the same data.
You cannot delete your own account yourself. Only artwork admins can delete
accounts, and only those of other people; the action requires confirmation.
Personal settings are lost. First clarify tasks, projects, shifts,
responsibilities, and retention requirements with your administrator. If
your access should only be suspended, HR administration can
deactivate the account.
Do not delete for a temporary absence
For vacation, illness, parental leave, or a temporary change of duties,
adjust availability, access, or responsibilities, or deactivate the account.
Permanent account deletion is not appropriate.
CRM
Overview
Manage contacts using your own types, fields, and access rules
The CRM is the central directory for external people, organisations, and
other specialist addresses. Depending on your setup, these might include
artists, accommodation, manufacturers, agencies, partners, or completely
custom contact types.
Contacts are not limited to name search. Each type can have its own fields,
required details, list columns, and filters. Confidential property groups can
be released to specific users or entire teams. External contacts can also be
invited to maintain their own data and shared project tabs without an
Artwork account (see External access).
Each contact type appears as a tab with a name, icon, and colour. The order of
the tabs is defined in the CRM settings. The active type determines:
which contacts appear in the table,
which fields a contact has and which of them are mandatory,
which additional columns are shown,
which filters are available,
whether a contact can be created and edited directly in the CRM.
Some system types mirror data from other areas:
System type
Leading area
Users
User management
Freelancers
Freelancer management
Service providers
Service-provider management
These tabs are read-only in the CRM. Create and change records in
User management; a link on the contact takes you straight
to the original profile. This prevents two independent records for the same
person or company.
The CRM menu, reading, creating and editing contacts; the contact popover and artist linking in projects, residencies, and inventory. Only released property groups are visible.
Manage CRM
Additionally System → CRM Settings, import and duplicate check, deleting contacts, the CRM contacts tab in the recycle bin (restore, delete permanently), and access to all property groups, including confidential ones.
Invite externals
The invite buttons in the CRM, on contact pages and in project tabs, plus the External access overview. Only works while the external access feature is enabled in the settings.
There is no read-only CRM permission: anyone who can see contacts can also
create and edit them. Deleting contacts, however, requires Manage CRM.
Confidential property groups can additionally have their own view and edit
access for users or teams.
Two users may therefore open the same contact but see or edit different
groups. Confidential groups are not simply exposed as general contact
information in project cards, and external accesses never see them.
CRM structures contacts, not communication
The CRM stores master data, files, and links. It is not a full email inbox and
does not automatically record calls or conversations unless you configure
properties for that purpose.
CRM
Contacts & projects
Create, search, edit, merge, and reuse contacts in specialist workflows
Select a contact type first. The number on the active tab shows its current
result count. The table always contains the name and, depending on CRM
settings, additional property columns. Long lists are split across pages.
Search covers the name and the values of all text, textarea, and link
properties of the contact type that you are allowed to see, so for example
the email address or phone number as well. Use the column headers to sort by
name or by one of the properties shown as a column. If filterable properties
exist, the filter button opens an additional dialog. Its badge
shows the number of active criteria.
Filters behave by field type:
Field type
Filter behaviour
Text, textarea, link
Search by entered content; part of the value is enough
Number
Exactly this number
Date
Exactly this date
Checkbox
All, yes, or no
Selection
One or more options; several selected options are alternatives within that field
Multiple choice
One or more options; contacts appear if at least one of them is set
Active filters appear as tags in the dialog. Remove them individually or
reset everything.
Select contacts using the checkboxes at the start of each row. As soon as one
is ticked, a bar appears above the table with Select all on this page and,
with the Manage CRM permission, Delete selection. The selection
applies per page and is cleared when you change pages, search, filter, or
sort. The mirrored tabs have no checkboxes.
New contact is available only for directly maintained types. Choose the
type under Contact type and enter a clear display name. The fields are grouped by the property
groups of the contact type; mandatory fields carry a red asterisk, and help
texts appear directly on the field. Groups with mandatory fields start
expanded; open the others as needed. Only groups you may edit are offered.
Two things stand out in daily use:
The dialog requires only the name. Artwork asks for empty mandatory fields
only when you later edit the contact and want to save.
Fields of type Upload are missing from the dialog because a file needs an
existing contact. Upload them on the contact page after creation.
The mirrored tabs for users, freelancers, and service providers do not have
the button; a note below the page title points to the corresponding
management area.
Open a contact by its name and select Edit. The display name and all fields
released for that type become editable. Artwork saves field entries
continuously in the background. Save changes ends edit mode and also
applies a changed name. Asterisks mark required fields: as long as one is
empty, edit mode stays open and the field is highlighted.
Available property types include:
short and multiline text,
number and date,
checkbox (yes/no),
selection from prepared values, single or as multiple choice,
web link,
file upload.
Links open directly in view mode. Uploaded files can be downloaded or, with
edit access, replaced and deleted. Fields are organised in collapsible
groups. Confidential groups are marked and available only to authorised
users.
Use Upload profile image on the contact's avatar to add or replace a
picture. It also appears in the short profile that Artwork shows when you
click a CRM contact in the project team or the name of a linked artist in
the project, the calendar and the shift plan. It contains name and contact
type, plus email, phone and city, provided the properties Email,
Telefon and Stadt are in a group visible to you. With Use CRM,
the icon next to the name (Open CRM contact) leads to the contact page.
Mirrored system contacts are read-only here. A note with Open profile
takes you to the original user, freelancer, or service-provider profile where
you change the data.
Files on contacts
Upload properties accept PDF, JPG, PNG, WebP, DOC, DOCX, XLS, XLSX, CSV, and
TXT up to 10 MB. A profile image must be an image file of at most 2 MB. Active
content such as HTML or SVG is rejected. Files of upload properties are
delivered only to signed-in users who may see the contact. Direct links to the storage
path do not work, so share files through Artwork rather than copied
addresses.
Use Change type to move a free CRM contact to another contact type, for
example when a contact was accidentally created under the wrong contact
type. The Change contact type dialog shows beforehand which stored values
have no field in the new type and would therefore be deleted permanently. If every value also exists in the new type,
the dialog confirms this. The action requires Manage CRM. Mirrored
contacts cannot be retyped, and mirrored contact types are not offered as a
target either. The button is also missing for contacts backed by their own
record of a system type, for example a contact that was created as an artist
or manufacturer through an external-access invitation, and for every contact
of the Accommodation type Coming with the next update. If a free contact is
moved to the Accommodation type, the new accommodation record takes over its
values for Email, Phone, Address and Note.
Contacts of the Accommodation system type have an additional Room
types section. There you create items such as single and double rooms with
their Cost per night, rename them, change the cost, and remove them
again. Artwork saves name and cost when you leave the field. Room types are
saved only with the Manage CRM permission.
Accommodations for residencies
Coming with the next update
The
Artist residencies
component offers the CRM contacts of the Accommodation type for selection.
In daily work this means:
Every contact of the Accommodation type automatically gets its
accommodation record, whether you create it with New contact, by
import, with Change type or through an
external-access invitation. It appears in
the accommodation selection of a residency, and its room types are
available there as well.
If you rename an accommodation in the CRM, the new name also applies in
the selection.
Because every accommodation contact is backed by this record, Change
type is missing for it, and under Find duplicates it can only be the
main contact, not be merged into another contact.
The Accommodations page still has no menu entry. You reach it by
appending /accommodation to the address of your installation. There you
additionally maintain the defaults Daily allowance and Deduction per
breakfast, which a new residency in this accommodation takes over. On
the detail page of an accommodation contact, the link Open accommodation
page leads directly to these defaults Coming with the next update, provided
you may open the page. Empty
defaults mean that the general default from the
project settings
applies. An accommodation created there with Create new Accommodation
gets its CRM contact, and changes made there appear in the CRM.
In the Project Artist component, use Link with CRM artist to search and
link existing contacts of the Artist contact type; other contact types cannot
be linked here. Create new CRM artist and link creates a new CRM contact
right there. Linking and unlinking require that you may edit the project;
creating additionally needs Use CRM.
Expand a card to see permitted contact details and, with the Use CRM
permission, open the full CRM profile via Open in CRM. A project may have
several artists. Unlink removes only the relationship, not the contact
itself. Under Also artists via CRM contact lists the component names
people who carry the special Artist role in a
CRM contact list of the project.
The CRM contact list project component collects any CRM contacts in a
project tab, for example the people travelling with a guest performance. You
create new contacts of the allowed contact types there or add existing ones
with Link existing CRM contact. If roles are enabled in the component
settings, you assign the contacts to roles; one person can have several roles.
Remove from list only removes the link, the contact stays in the CRM. Setup
and options are described in
Tab configuration.
If the option CRM contacts in project team is enabled in the
project settings under System → Projects,
the dialog for editing the project team contains the CRM contacts
section. There you search contacts of all contact types, add them as
external team members, and assign them project roles. They appear in the
project team and in project outputs labelled with their contact type, but do
not receive an Artwork account. If a project role is deleted in the
settings, it is also removed from external team members.
If you switch the option off again, Artwork hides the CRM contacts in the
project team. The assignments stay stored and reappear once the option is
switched on again.
In the
Artist residencies
project component, use Assign existing artist to select a CRM contact of
the Artist contact type, or enter a new person. For a new person Artwork
creates a CRM contact of this type on saving, unless you choose Do not
save artist in database.
The dialog shows the properties assigned to the Artist contact type with the
contact's values. For an existing contact you can change them only with the
Manage CRM permission. As soon as you have changed a value, Apply
changes to artist in CRM appears:
Ticked, Artwork writes the changed values to the CRM contact.
Unticked, the CRM contact stays unchanged.
You choose the accommodation of a residency from the CRM contacts of the
Accommodation type Coming with the next update, see
Accommodation and room types.
A document request can be linked to a
CRM contact. The link stays stored on the request, and the contact data
released to you can be expanded there. When uploading a contract, Link CRM
contact only serves to take over the name as contract partner; no link is
stored on the contract itself.
Once project links exist, a Projects tab appears on the CRM contact. It
shows project name, period, and link date. The Linked via column shows
whether the relationship comes from an Artist linking, the Project
team, a CRM contact list, or an Artist residency. Team members list
their assigned roles, contact lists the title of the list with the contact's
roles, and residencies their period. If a contact is linked in several ways,
all of them appear in the same row. The name opens the project.
This tab is an overview and does not provide a general Add Project action.
Create or remove the relationship in the relevant project component.
The External access block on the contact page shows whether the contact
has been invited to maintain their own data and shared project tabs. The
External access page describes invitation,
release, and management.
With Manage CRM, Find duplicates in the contact list opens an
overview of all contacts of the same type that share a name or an email
address. Each group shows what the contacts have in common (Same name or
Same email address), the creation date, and whether a contact is linked
to a profile.
Set the main contact in the group. The contact linked to a profile is suggested, otherwise the oldest; use Keep as main contact to choose another.
Choose Merge into main contact and confirm the dialog.
Then open the main contact and review values, projects, and residencies.
When merging, the main contact keeps its values; empty fields are filled from
the duplicates. Project links, residencies, and external accesses are
transferred. The duplicates move to the recycle bin, where they can still be
restored. Merge all duplicates applies this rule to every group found at
once.
Contacts mirrored from user, freelancer, and service-provider profiles are
not included; clean up such duplicates in the respective management area.
Contacts linked to a profile or record, including all accommodations
Coming with the next update, can only be the main contact and cannot be merged
away (Cannot be merged (linked)). The comparison ignores upper and
lower case; for the email address the Email property counts.
With Manage CRM you can delete directly maintained contacts individually
from the row menu or in bulk via the selection. The action requires
confirmation. The dialog says it cannot be undone; in fact deleted contacts
go to the recycle bin under the CRM contacts
tab, where you can restore them, delete them
permanently one by one, or empty the whole tab. First review project,
residency, and document links as well as uploaded files.
On deletion Artwork revokes all external accesses of the contact; after a
restore you have to
reactivate them
yourself if needed. Files uploaded to upload properties are kept in the
recycle bin and disappear only with permanent deletion.
Unlink or delete?
If a person simply no longer belongs to a project, unlink them. Delete the
CRM contact only when the record as a whole should no longer be maintained.
For duplicate records, merging is the better choice because links are kept.
CRM
External access
Invite external contacts by link so they maintain their own data and shared project tabs without an Artwork account
External access lets you invite people without an Artwork account, such
as companies, agencies, touring partners, or artists. They receive a personal
access link by email and can use it to read or fill in shared project tabs
and maintain their own contact data. No password or user account is needed.
Typical uses are technical riders, contact persons and travel details that a
guest production enters itself, or logos and press material that an agency
uploads straight into the project tab.
After a fresh installation or an update the feature is switched off. Only
when an Artwork admin enables Activate external access under System →
External access do the invite buttons appear and external access links
work. Existing accesses are kept when the feature is switched off and keep
working after it is switched on again.
The System → External access page is visible to Artwork admins only and
holds all installation-wide defaults. There is no save button: switches take
effect immediately, number and text fields when you leave the field, and
Saved briefly appears at the top. Rejected values show their error
message directly below the field.
Setting
Effect
Activate external access
Switches the feature on or off as a whole (default: off).
Allow file upload for external accesses
Only with this switch can invited people upload their own files in a File upload component (formerly “Documents”) and remove them again (default: off). Without it they can only view and download documents. The file types and size limit of the “project” area from the file settings apply, and in addition the limits of the upload area the component is placed in (file types, file size, number per project). The same switch also enables file fields under My data.
Company name (override)
Name used in invitation emails; leave empty to use the name from the tool settings.
CRM access default (months)
Default for how long an invited person may maintain their own contact data (default: 12 months).
Tab access default (days)
Default end date of a tab release (default: 90 days).
Expiry reminder (days before, 0 = off)
This many days before a tab or CRM access expires, the inviters receive a reminder (default: 3).
Security & rate limiting
Validity of the access link, session duration, and limits for link requests; change with care.
Under Blanket notification recipients you can additionally add users or
departments who receive a copy of every external access notification.
Without an entry, only inviters and project managers are informed.
The upload switch applies to the whole installation
Decide both switches deliberately: file upload applies to every external
access of your installation, not per project or person.
Who may invite is controlled by the Invite externals permission in the
user permissions. It requires
the CRM module and has no effect while the feature is disabled; the
permissions page then shows it as a disabled feature. The permission unlocks
the invite buttons in the CRM, on contact pages and in project tabs, plus
the External access overview.
Tab invitation: a person should read or fill in project tabs. No CRM contact is created; an email address, an optional name and the tabs are enough. This is the only way to grant tab releases.
CRM list
Invite external in the header
Contact invitation for a new person: a new CRM contact is created who should maintain their own master data (address, bank details …) in the CRM. The dialog points out that tab releases are granted via the project. An already existing contact is best invited from its contact page.
Contact page
External access block with Invite contact for external access or Invite again / extend
Like the CRM list, but the contact is already set and the access is linked to it. The block shows email, CRM access period, the shared tabs with project and end date, and the time of the last submission.
The invitation is tied to the email address. Inviting the same address again
extends the existing access and adds the newly selected tabs; the same
person can receive the same tab in several projects. Addresses that belong
to an Artwork user account are rejected. From the contact page, an address
whose access is already linked to another contact is rejected as well.
The collapsible help box How does external access work? explains the
process, what the invited person sees, the CRM link, and management. Which
details follow depends on the starting point.
Enter the E-mail address and optionally a Name. The name appears in
notifications and in the tab status; no CRM contact is created for the
person.
Select Shared tabs. The current tab is preselected if it contains
externally visible components; otherwise it shows No externally visible
components. For each tab set the Access, either Read only or Read
and write (preselected), plus From and Until. Read and write is
only offered if you yourself may write in the project; you can only share
tabs that you can see yourself.
Read the notes and choose Send invitation. The person receives an email:
“… has invited you to fill in information for the project … at …”, noting
that no account or password is needed, entries are saved automatically and
are submitted at the end in the form.
Set the contact. From the contact page the contact is already set; the
dialog there also shows existing accesses of the contact. From the CRM list
you create a new contact: choose the Contact type via the search field
and complete the name details asked for (for custom contact types only the
name). Confidential mandatory fields must be filled in by you; the external
person never sees them. If Artwork finds the email address on an existing
contact or access, it does not create a second contact but links the
invitation to the existing one. For the Freelancer and Service Provider
contact types Artwork also creates the corresponding freelancer or
service-provider profile. The Users contact type cannot be invited; the
dialog then reports This contact type cannot be invited for external
access.
Check the email. The invitation goes to the contact's stored address.
Send to a different email address instead stores a separate Email for
external access; the contact's own address stays unchanged. If the contact
has no address yet, the entered one is saved on the contact.
Set CRM access until. Up to this date the person can maintain their own
contact data. Left empty, the default period from the settings applies.
Choose Send invitation. The person receives an email with the access
link.
The dialog shows two notes when relevant:
Important: The external person sees every component of the selected
tabs, regardless of their internal visibility settings. Create a dedicated
tab for exchange with externals (see
tab configuration).
File upload disabled: If a selected tab contains a File upload
component and the upload switch is off, the person cannot upload files there.
Shown externally are text fields, dropdowns, checkboxes, multiple choice
(checkboxes), text areas, titles, separators, disclosures, links and link
lists, project title, project basic data, artist names, the File upload
component, and the CRM contact list. With
write access, text fields, dropdowns, checkboxes, multiple choice, text
areas, links, link lists, disclosures, the file upload, and the contact list
can be filled in. Other components, such as
budget, checklists, or shifts, never appear externally. Hint texts stored on
fields are shown to the external person below the field.
The link from the invitation email first opens the Confirm login page.
The session starts only after a click on Sign in, so a link preview in
the mail client does not consume the link. The link is valid only briefly
(default: 15 minutes) and can be used once. Afterwards the person can request
a new link to their email address at any time via Request login link, as
long as the access has not expired or been revoked.
External sessions have a fixed maximum duration (default: eight hours, sign
out after two hours of inactivity). After that a new click on a fresh link is
required. External users stay entirely within the /external area and see
nothing of the internal application.
Anyone who has exactly one shared tab and no running CRM access lands
directly in that tab after signing in. Everyone else sees the overview first.
After signing in, the Overview shows a greeting, for contact invitations
the validity of the CRM access, and the Shared with you list with
project, tab, and access type; each entry leads straight to its tab. The
navigation contains Overview, My data (only while CRM access lasts),
the shared tabs per project, marked “read only” where applicable, and
Logout. On a phone the navigation sits behind the menu icon in the header
bar.
Under My data the person sees their own CRM contact with its
non-confidential property groups and can adjust it with Edit. Which
master fields are offered depends on the contact type, for example first
name, last name, email, phone, and address for freelancers; artist name,
first name, last name, email, phone, and position for artists; or name,
contact person, email, phone, website, and address for manufacturers;
accommodation and custom contact types show their respective fields.
Confidential groups never appear.
File fields (properties of type Upload) can only be filled in if Allow file
upload for external accesses is enabled. Allowed are PDF, JPG, PNG, WebP,
DOC, DOCX, XLS, XLSX, CSV, and TXT up to 10 MB. The file is reviewed with the
submission and stored on the contact only when it is accepted. Without the
switch the person only sees the name of the current file.
Changes are not applied directly: Submit changes for review sends a
submission to the inviting person (see
Approving contact data). The status — open,
applied, partially or fully rejected — is shown to the person under My
data; a new submission replaces one that is still open.
A tab shows the project, tab name, whether editing is possible, and Access
valid until at the top. The content is divided into section cards that
follow the tab's headings; disclosures also work externally. With write
access, Artwork saves every entry immediately as a draft; the person can
close the tab and continue later. Internally these drafts are visible
directly in the components.
Only the Submit entered data button tells the inviting person and the
project management that the entries are complete. From that moment the tab
is locked for the person until someone reviews the data internally: if
the tab is returned for revision, the person can continue editing and
finish with Submit entered data again; if it is confirmed, it stays
closed. In both cases an email reports the outcome. When a tab is returned,
the reviewer's comment, if they wrote one, appears in the email and at the
top of the tab.
If the tab contains a CRM contact list — such as “Names of all arriving
people” in the Production inquiry template — the external person can
create contacts of the allowed contact types with Add …. They see and
fill in only the non-confidential fields; only the public mandatory fields
are required. They may Edit and Remove only contacts they
created themselves (marked added by you). A configured Maximum number of contacts limits the
list.
In a File upload component the person sees all files of the tab with name,
size, and date and can retrieve them at any time with Download. Active
content such as HTML is never rendered in the browser during an external
session.
If Allow file upload for external accesses is enabled and the tab is
shared with write access, the person can additionally upload their own files
and delete them again with Remove — only their own, marked uploaded by
you. Without the switch, a note explains that uploading is not enabled for
external accesses.
Tab status: Next to Invite external to this tab, the tab shows a
round icon for every external person with a current release for this tab.
The tooltip gives name and status: Invited – not logged in yet, In
progress – not submitted yet, Submitted on … – waiting for
confirmation, Confirmed by … on … or Returned for revision by … on ….
Clicking an icon opens the External persons in this tab dialog with
every person, their email address and status. Expired releases and revoked
accesses are not listed.
While a person with write access has already logged in but not yet
submitted, a note in the tab points this out.
Review: In the dialog, Confirm and Return for revision are
available for a person who has submitted. Only returning asks for an
optional Comment for the external person; confirming has no comment.
Confirming also marks the externally created contacts as reviewed;
returning reopens the tab for the person and is still possible after a
confirmation. Anyone who may edit the project may review, as well as the
person who released exactly this tab, as long as they may still see the
project.
Notification: When a tab is submitted, the inviting person, all
project managers and the blanket recipients registered for it receive a
message that the external person submitted the data for the tab. It states
the number of fields changed since the last submission, the number of
contacts added if any, and contains the link Open project. Individual
field changes do not trigger notifications. The messages belong to the
External access group in the
notification settings.
CRM contact list: Externally created contacts carry the badge
External · not reviewed and the note Added externally by … – not yet
reviewed. If Artwork detects a contact with the same name, it warns with
Possible duplicate in the CRM and offers Merge into existing
contact. Internally you can add contacts to the same list, include
existing ones with Link existing CRM contact, Open in CRM or
Remove from list — the contact itself stays in the CRM.
Project history: Every submission creates an entry “External person …
submitted data in tab …” with the external person as the actor, not an
internal account.
Externally uploaded files: In the project's File upload component such
files carry the badge Uploaded externally by …; the tooltip shows the
access's email address.
Contact page: The External access block shows accesses, periods,
shared tabs, and the time of the last submission. If a contact-data
submission is pending, the note There is a data update request to
review appears there with a link to the review.
The person's own contact data, including property values, always goes
through approval by the inviting person: what the external person submits
under My data is written to the CRM contact only after review. The
inviting person or an Artwork admin may review.
The Review external submission page, reached via the note on the contact
page, the notification, or the access detail page, compares the current and the
proposed value for each field. Decide per row with Accept or Reject
and apply the selection with Apply decisions, or choose Approve all
or Reject all (optionally with a reason). For a file field the proposed
file is shown for review instead of a value. The external person then
receives an email stating whether their changes were applied, partially
applied, or rejected.
The External access button in the CRM list opens the External access
overview (permission Invite externals). It lists all accesses with
email, linked contact, status (Active, Expired, Revoked), CRM
access until, number of scopes, Invited by, and Last login;
filter buttons narrow by status.
Details opens the detail page of an access:
Area
Options
Header
Resend invitation (new access link while the access is still active), Revoke access with reason, Reactivate, Re-link to another contact
CRM access
Show validity and set a new expiry date with Extend. For pure tab invitations this only shows Tab access only (no own CRM contact); extending is not available then.
Tab access
Table with project, tab, access, validity, and Last submitted; per row Extend (new end date), Make read-only or Make writable and End now. As with inviting, extending and Make writable require that you can see the tab yourself; write access additionally requires that you may write in the project.
Recent submissions
The last 20 contact data submissions with date, number of changes and status; open submissions have the link Review
Audit log
The last 100 actions on the access, its tab releases and its submissions with time and actor: invitation resent, CRM or tab access extended, access revoked or reactivated, access type changed, tab access ended, tab data submitted, re-linked to another contact, data change submitted and decided. External actions carry the badge External. Individual field entries and file uploads in the tab are not listed here.
The actions on the detail page are open to the person who sent the invitation
and to everyone with Manage CRM. Re-link to another contact is
reserved for Manage CRM. Its dialog expects the CRM contact ID of the
target contact, that is the number at the end of the contact page's address
(/crm/contacts/…); a contact data submission that is still open lapses in
the process. Anyone with only Use CRM can view other people's accesses
but not change them.
An access is never deleted, only revoked; it can be reactivated at any time.
If the linked CRM contact is deleted, Artwork revokes its accesses
automatically.
Once the CRM access and all tab releases have expired, sign-in no longer
works until you extend the access or invite again.
Every morning Artwork checks which tab and CRM accesses expire within the
days set under Expiry reminder and notifies the inviting person, for tab
releases also the person who granted the release, and the blanket recipients
registered for it. The message states the expiry date and leads to the
access detail page via Manage external access. Each release is reported
once; after an extension the reminder applies again. Revoked accesses are
not reported. With the value 0, or while the feature is switched off, the
reminder is off.
Recommendations
Create a dedicated tab per project for exchange with externals and share
only that one.
Keep bank details, conditions, and internal notes in confidential property
groups; external accesses never see them.
Give tab releases a clear end date and end them after the production with
End now.
Review submitted contact data promptly so the external person is not left
waiting for feedback.
CRM
Import contacts
Map CSV and Excel files to contact types and properties, detect existing contacts, and review results
With the Manage CRM permission, import contacts from CSV, XLSX, or
XLS. Files may be up to 10 MB. Import creates new CRM contacts and can
optionally detect and update contacts that already exist. Only the first
worksheet of the file is read. You can import into all directly maintained
contact types; the mirrored types Users, Freelancers, and Service Providers
are not offered. Start the import with Import in the header of the
contact list.
Handle duplicates deliberately
Without the Detect existing contacts option, every row becomes a new
contact, even if a contact with the same name already exists. Enable
detection when the file contains known contacts and, if needed, use
Find duplicates
after the import.
Provide a display name or separate first/last-name columns that can map to
correspondingly named properties.
For selection properties, use exactly the configured Artwork values,
including upper and lower case.
For a multiple choice property, separate several options in one cell with
a semicolon, for example Light;Sound.
In CSV files and text cells, write numbers with a decimal point rather than
a comma and without thousands separators. Real number cells of an Excel
file are read regardless of how they are displayed.
Write dates in one of the supported formats, see
Supported values.
Upload properties cannot receive files through this table import.
Disable Determine different contact types by column in Excel, choose a
type, and upload the file. Then map every relevant source column to the
display name, a property, or Skip. The selectable fields are the
properties of the groups assigned to the contact type in the
CRM settings.
Artwork attempts to match similar headers automatically. Always check the
preview. Each CRM property and the display name can only be mapped once.
If the right contact type is missing, create it with New contact type
directly in the upload step, including the property groups it should have.
You do not need to leave the import.
Enable the type column when one source column contains values such as
“Artist”, “Agency”, and “Accommodation”.
Upload the file.
Select the column containing the contact type.
Map every source value to a CRM type or deliberately skip its rows.
For each used type, separately map columns to its name and properties.
Review the preview and required details, then start the import.
The type column itself is not imported as an extra property. Rows with
unknown or deliberately unmapped type values are skipped. If a contact type
is missing, create it in the CRM settings and restart the import so it
appears in the mapping.
In the mapping step you can enable Detect existing contacts. Artwork then
checks every row against the existing contacts of the same type:
Setting
Meaning
Match by
The name or one of the mapped properties used to match a row to an existing contact, such as the email address. The value must match completely; upper and lower case and surrounding spaces do not matter.
Skip row
On a match, the existing contact stays unchanged and the row is skipped as a duplicate.
Update existing contact with the values from the file
On a match, the mapped values from the file are written to the existing contact. Empty cells overwrite nothing: an existing value stays.
When importing several contact types from one file, matching is done via the
contact name within the respective contact type.
Detection also works within the file: if the same match value occurs again
in a later row, that row is treated like a match, so it is skipped or written
to the contact that was just created.
Every imported type needs a display name. This can come from a directly
mapped name column or be built from first and last name when matching
properties are mapped.
Required fields are marked during mapping. Map them where possible and verify
that the source cells actually contain values. Unmapped properties remain
empty on newly created contacts. Missing required fields do not stop the
import: the mapping lists them under The following required fields are not
mapped, and the contacts are created without these values. Artwork asks for
them only when someone edits the contact later.
A valid numeric value with a decimal point, such as 1250.5
DateComing with the next update
DD.MM.YYYY, DD.MM.YY, YYYY-MM-DD, DD/MM/YYYY (day before month) or an Excel cell formatted as a date, each with or without a time; the time is discarded
Checkbox
1, true, yes, ja, or x means yes; other values mean no
Selection
Exact match with a configured option
Multiple choice
One or more options separated by a semicolon; each must match a selection value exactly
Upload
Not importable; upload the file later on the contact
Empty cells are always allowed. If a cell contains an invalid value, however,
the whole row is skipped, not just that one field.
How the import reads dates
Coming with the next update
Two-digit years:00 to 69 count as 2000 to 2069, 70 to 99 as
1970 to 1999; 15.03.26 therefore becomes 15 March 2026.
Slashes: the day comes before the month; 05/06/2026 is 5 June.
12/31/2026 is invalid.
Excel date cells are recognised as dates, also with a time. Only a
value without a leading zero that results in a date from 1 January 1930
counts as such a number. Small numbers such as 12.05, 5, 010124 or a
bare year such as 2026 are invalid.
Any other format is invalid and skips the row with a message, like other
invalid values. The import never stores a guessed date.
the number of other skipped rows with row number and reason.
Common reasons include an empty name, unmapped type, invalid date,
non-numeric number, or selection value absent from the configuration. Put
only failed rows into a corrected file before importing again, or enable
detection of existing contacts on the second run so that successfully
imported rows are not duplicated.
Cancel ends the mapping process and discards the temporary upload. If the
import session expires, start again from the upload step.
CRM
CRM settings
Design contact types, groups, properties, and access rules
System → CRM Settings defines the CRM structure for all users. The page
requires the Manage CRM permission. Changes affect entry forms,
profiles, tables, filters, imports, and some project components.
Organises fields into sections and may be confidential
Contact details, bank data, technical data
Property
Stores one specific value
Phone number, date of birth, website
A property is first created in a group. You then assign the groups a contact
type needs and define per property how it behaves in that type. Start with
property groups when the CRM is still empty.
Create a contact type with New type. It has a name, icon, and colour
shown on its tab and profiles. Custom types can be edited and deleted after
confirmation. A contact type can only be deleted while no contacts are
assigned to it; move the contacts beforehand with
Change type or
delete them. Drag types in the list
to change their order, and with it the order of the tabs in the CRM.
System types carry a System marker. Other Artwork functions depend on
them, so they cannot be deleted. Name, icon, colour, and the property
assignment may be adjusted without changing the underlying system function.
When creating a contact type, and later via Edit contact type and property
assignment, you select the property groups that apply to the type in the
same dialog. Drag the assigned groups into the desired order; it defines the
layout of the contact page for this type. Expand a group to enable its
individual properties and set per property:
Option
Effect
Mandatory field
Marked with a red asterisk and must be completed before editing a contact can be finished. The New contact dialog and the import create contacts even with empty mandatory fields.
Show in list view
Adds a sortable column to this type's tab
Filterable
Offers the field in the contact list filter
Uploads cannot be filtered. Some system groups and properties cannot be
deselected because other functions rely on them; the dialog marks them
accordingly.
Keep the result focused: too many columns make the list difficult to scan,
and every mandatory field increases effort during creation and import.
Create a group with New group. It has a name and icon. The list shows how many properties each group
contains and which contact types use it. Groups can also be reordered by
dragging.
Enable Confidential when its fields should not be visible to all CRM
users. Confidential groups are visible only to people with Manage CRM
and to the users and teams you authorise under Manage access. For each
entry you grant separately:
Can view — the group and values are shown.
Can edit — the group's fields are additionally unlocked for editing.
Can edit only works together with Can view: without view access the
person does not get to see the group at all. If you turn off confidentiality,
Artwork deletes the access list. If the group becomes confidential again
later, enter the releases anew.
External accesses never see confidential groups
Contacts who maintain their own data through
external access never see confidential
groups, regardless of any release. Keep bank details, conditions, and
internal notes in confidential groups.
Select Add property in the desired group, then provide a name, type, and
an optional help text (Tooltip text) that appears directly on the field in
the entry form. Available types are:
Type
Suitable for
Text
Short values such as phone, city, or reference number
Textarea
Notes and longer descriptions
Number
Purely numeric values
Date
Calendar dates
Checkbox
Binary characteristics (yes/no)
Selection
Controlled list of prepared values, exactly one value per contact
Multiple choice
The same kind of list, but several values per contact
Link
Web addresses displayed as clickable links
Upload
One file stored directly on the contact
For Selection and Multiple choice, define the allowed options under
Selection values using the intended spelling and add more with Add
option. Change the order by dragging, without deleting options. Imports
check these exact values.
For a Multiple choice property you additionally choose under Display
whether it appears as Checkboxes or as Dropdown with multiple
selection. An existing Selection can be converted into a Multiple choice;
the existing values are kept. There is no way back: a Multiple choice cannot
be changed to another type, and other types cannot be turned into a Multiple
choice afterwards.
Drag properties within their group to change their order. This affects the
contact page and entry forms.
Custom groups and properties can be edited or deleted after confirmation.
Before deletion, assume that existing values and assignments will no longer be
available. Deleting a group also removes all properties it contains.
System items are protected:
System properties can neither be renamed nor changed in type nor deleted;
the list offers no edit and delete icons for them.
System groups can be edited (name, icon, confidentiality) but not deleted.
A custom group cannot be deleted either as long as it contains a system
property.
Test structural changes first
Create a new field as optional and assign it to one contact type. Test entry,
list, filter, and import. Only then make it mandatory and roll it out to more
types.
Do not create duplicate properties with slightly different spelling.
Group privacy-sensitive values into dedicated confidential sections.
Keep selection values short, stable, and consistent.
Reserve mandatory status for genuinely indispensable data.
Do not treat protected system fields as freely interchangeable master data.
Documents & Contracts
Overview
Store contracts securely and request missing documents within the team
The Documents & Contracts area combines a central contract repository with
an internal request workflow. Completed contract files are assigned to a
project, supplemented with the key contract details and shared specifically
with people or teams. If a document is still missing, you can first create a
document request and assign it to the responsible person.
Store completed files by project, download, edit, filter and evaluate them
Document requests
Record internally which document is needed, who should provide it and by when
Contract modules
Make reusable templates or text modules available centrally
A document request is not yet a contract. It first collects the assignment,
responsibility and preparatory information. When a file is uploaded through
the request, Artwork creates a contract, links it to the request and changes
the request to Completed. Anyone allowed to create or edit requests also
sees the open requests of other people in the overview's Assigned to
others tab.
The Documents → Contracts page is your permission-based overall view; the
requests are under Documents → Document requests. Project-related
contracts can also appear in the document/contract area of the respective
project. Clicking the project name in the contract list takes you directly to
that project.
Which contracts you see depends on their sharing settings: your own contracts
and documents shared with you personally or through one of your teams are
visible. Artwork admins can see all contracts.
Two things are regulated separately: what someone may do in the area in
general (user permissions) and which individual contracts someone sees (the
share on the contract, see
Who can see a contract?).
Permission
Effect
View contract modules
Menu Documents → Contracts; see and download contract modules
Manage contract modules & project contracts
Additionally upload and delete contract modules, upload contracts in all projects you may see, and the menu Documents → Document requests
Create document requests
Menu Documents → Document requests; button Create document request; tabs Unassigned and Assigned to others
Edit document requests
Menu Documents → Document requests; Edit and Delete on a request, set the status; tabs Unassigned and Assigned to others
Without any of these permissions the Documents menu is missing. You can
still upload contracts in projects where you have write access. You can also
answer a request assigned to you or created by you with Upload document
without a contract permission, provided the request is assigned to a project
and you store the contract in exactly that project. You then reach it through
the link in the notification or in the project. The full overview is in the
user permissions.
Internal workflow
In the current interface, document requests are assigned to internal Artwork
users or created without an assignee for the time being. They do not send an
external upload link to a contract partner. External details can nevertheless
be taken from and displayed through a linked CRM contact.
No professional assessment
Fields such as artists' social security (KSK), foreign tax or reverse
charge support filing and evaluation. Artwork does not determine whether a
legal or tax obligation applies and is no substitute for professional advice.
Documents & Contracts
Managing contracts
Upload, assign, complete and retrieve contracts in day-to-day work
Under Documents → Contracts, you will find every contract you are allowed
to see through its sharing settings. The table shows the contract partner,
project, people or teams with access, and the file name. Click the file name to
download the document; click the project name to open the associated project.
Select New contract and add the contract file together with its associated
project and contract partner. The project is mandatory: without a selection the
dialog reports Please select a project. The project assignment ensures
that the document can be found both in the overall view and in the correct
project context.
You can upload in projects where you have write access or, with the Manage
contract modules & project contracts permission, in all projects you may
see. Which file types and which file size are allowed is defined by the
“Contract” area in the
file settings.
The following details can be used to describe the contract:
Detail
Benefit in daily work
Project
Assigns the contract to the relevant work and project view
Contract partner
Shows immediately who the agreement is with
Link CRM contact
Takes over the name of a CRM contact as contract partner and shows its contact details during the upload
Legal form and Contract type
Support consistent classification and later filtering
Amount and currency
Records the agreed financial scope, such as a fee or co-production contribution
KSK-liable
Artists' social security: with the box ticked you enter the KSK Amount, without it KSK Reason is available for the justification
Foreign tax
With the box ticked you enter Foreign tax amount, City and Country, without it Foreign tax reason is available
Reverse Charge Amount
Records a corresponding amount separately
Deadline date
Makes a contract-related deadline filterable and traceable
Contract status and Contract status comment
Describe the contract's individual business status
Comment / Note
Holds additional internal information; the entry made during the upload is saved Coming with the next update
Not every field has to be completed for every contract. Agree within your
team which information is mandatory for your filing and evaluations. The
centrally maintained contract types and legal forms help keep values
consistent.
If the upload comes from a document request, Comment / Note is
pre-filled with the request's comment; whatever you change there is saved
Coming with the next update.
You can select a project through search or from your recently used projects.
If the project has a budget deadline, Artwork enters it as the Deadline
date when you select the project and overwrites a date set before. Check
the date before saving: the relevant contract deadline may differ
from the project deadline.
Instead of entering only a free-text name, you can select an existing CRM
contact with Link CRM contact. Artwork uses the contact's display name as
the contract partner. Show CRM details shows the contact information
available to you; View in CRM opens the complete contact profile if you have access to it.
Only the name is stored on the contract. No permanent link to the CRM
contact is created: the contact no longer appears in the Edit dialog,
and a later name change in the CRM does not change the contract. A CRM
contact stays permanently linked only on a
document request.
During upload, select individual people and/or teams under Document access
for. Anyone with access may not only view and download the contract but also
edit and delete it. Therefore include only those who need the document for
their work. The
selected shares are shown in the contract list using profile pictures and team
icons.
The person creating the contract receives access automatically. Other people
do not automatically gain access merely because they work on the project; the
contract share or a higher-level administrative permission is decisive.
People with access receive a notification when the contract is uploaded, when
they are granted access later and when the contract is deleted.
One or more tasks can be created together with the contract. Each task can
have a name, a due date and time, responsible people and a comment. You find
the tasks in the dialog under Add further details or task. This is
useful for obtaining a signature, requesting a tax review or remembering a
contract deadline.
Open the task form with New task, fill it in and confirm with Save
task in contract. Only then is the task in the list and saved with
Upload contract; a form that is still open is lost on upload. Without a
time, Artwork sets 00:00. For every additional task the button is called
Further task.
If you create several tasks before saving the contract, each one gets the
people chosen for it Coming with the next update.
The responsible people see the task on their dashboard under Next tasks.
It does not appear on the Tasks page.
When a task is assigned, the responsible people receive a notification
Coming with the next update, except for the person who assigns it. For open
tasks with a deadline, Artwork sends reminders as for
to-dos:
once when the deadline expires within the next 24 hours and once as soon as
it has passed. The check runs daily at 9 a.m. The notification contains the
contract name and the link to the project only if the person may open both
the contract and the project; otherwise it names the task and the deadline
and links to the dashboard. Whether the notifications arrive is controlled
by the notification types New tasks and Reminders for Tasks in the
notification settings.
Via Edit on the contract, the tasks are listed in the same
area with a checkbox: ticking it and saving marks the task as done. You can
also create further tasks there.
Coordinate task assignment and document access
Assignees must also be granted access to the contract. Artwork does not check
this itself: add them under Document access for as well so that they can
open the file associated with their task. Every task needs at least one
responsible person; without a selection it cannot be saved.
Use a row's action menu to update contract details and access settings later
and to replace the file with a new version. Changes to the project context are
also reflected in the project area. Artwork asks for confirmation before a
contract is deleted.
Anyone who has access to the contract may edit and delete it. There is no
separate user permission for this.
Deletion is permanent
A deleted contract does not go to the recycle bin. Artwork removes the entry
and the contract file immediately and irrevocably. Download the file
beforehand if it might still be needed.
Once deleted, colleagues can no longer access the file through either the
contract overview or its project context. Check linked tasks and completed
document requests before removing it.
Two different status fields
The freely worded Contract status field is part of the contract
information. A document request, by contrast, uses the fixed stages Open,
In Progress and Completed. The two fields serve different purposes.
Documents & Contracts
Document requests
Assign missing contract documents internally and track them through upload
Document requests coordinate the creation and upload of a missing contract
or other contract document within Artwork. A request keeps the requester,
responsible person, project, deadline and all already known contract details
together.
Open or ongoing requests for which you are responsible
Created by me
Open or ongoing requests that you commissioned, including those without a responsible person
Unassigned
Open or ongoing requests without a responsible person
Assigned to others
Open requests assigned to other people — with Requested by, Assigned to, status and deadline
Completed requests
Finished requests from the items you created or were assigned
The tabs Unassigned and Assigned to others are visible to people
with the permission to create or edit document requests, and to admins. The
counters on the tabs show how many requests each view contains. Assigned
to me and Unassigned show Requested by, project, status and
deadline. Created by me shows Assigned to, project, status and,
instead of the deadline, the Document column, which stays empty as long
as no document has been uploaded. Completed requests list
Requested by, Assigned to, project and the File, which can be
downloaded directly.
Completed requests only contains items you created or that were assigned
to you. If you complete a request from Unassigned, or someone else
uploads the document for a request that is not theirs, it afterwards appears
only for the person who created it and, where applicable, for the assignee.
Select Create document request. The button requires the Create document
requests permission. Under Assign to user you can assign an internal
person immediately or create the request without an assignee for the time
being. You may also select a project through search or from your recently
used projects; Artwork only accepts a project you may see. Set the project right
away if it is known: it cannot be changed on the request later.
All further contract details are found under Pre-filled document metadata
(optional) and are preparatory information. They include:
Contract partner or a linked CRM contact
Contract value, Legal form and Contract type
Comment / Note for hints or a work instruction
KSK-liable (artists' social security), Foreign tax and Reverse
Charge Amount with their amounts or reasons
Deadline date
Contract status as a freely worded state with Contract status
comment
The more information is already known, the fewer questions arise during the
later upload. A request can nevertheless be created with only a few details
and completed later.
When you select a CRM contact, Artwork uses its display name as the contract
partner. Expandable details only show CRM properties available to you. If a
project with a budget deadline is selected, that date is entered as the
deadline date.
When assigned directly, the selected person receives an Artwork notification
with a link to the document requests. Without an assignee, the item appears in
the Unassigned tab and can later be assigned by an authorised person.
A notification is only sent for the assignment made on creation. Anyone who
assigns a request to a person later via Edit should let them know
personally.
No external request
The person search selects an internal Artwork user account. The function does
not currently send an upload link to an external contract partner. Use the CRM
link to keep external contact information available on the request.
Use Edit to change the responsible person, preparatory contract details and
processing status. The project is assigned when the request is created and is
shown in both the overview and details.
Saving an edit requires the Edit document requests permission. This also
applies to requests assigned to you: without the permission you can view them
and answer them with Upload document, but change neither details nor
status. In the Assigned to me tab, Edit is then not in the action
menu either Coming with the next update.
The fixed status stages mean:
Status
Recommended use
Open
The request has been recorded, but work has not yet started
In Progress
The responsible person is preparing the document or clarifying missing information
Completed
The document is available; uploading it through the request sets this status automatically
The freely worded Contract status field in the metadata is separate. For
example, it can represent a business state such as “draft reviewed”, while
In Progress describes the request workflow.
View details provides a summary including status, requester, assignee, project,
CRM contact, deadline date, tax details, comments and, after completion, the linked
file. The dialog is read-only and omits empty fields. The KSK-liable and
Foreign tax blocks only appear when the respective box is ticked. A KSK
Reason or Foreign tax reason entered without the tick is therefore only
visible via Edit.
The Upload document action is available under Assigned to me and
Unassigned. It opens the regular contract upload and carries across details
such as project, contract partner, contract type, legal form, contract value
Coming with the next update and other amounts, deadline date, comments and CRM contact. Review and complete this information,
define access and select the final file. The person who created the request
is already entered under document access and receives access to the contract
in any case. If the request has no project yet, you must choose one in the
upload, because a contract always belongs to a project.
After a successful upload:
The file is stored as a contract.
The contract and request are linked.
The request automatically changes to Completed.
The person who created the request is notified.
The project's document area is updated if a project was assigned.
The file is then available in Completed requests, the contract overview and
the associated project, subject to its access permissions.
With the Edit document requests permission you delete requests through
the action menu in the tabs Created by me, Unassigned and Assigned
to others. The action is not available in Assigned to me and
Completed requests. Artwork asks for confirmation first. A contract that
has already been uploaded is kept when the request is deleted. Delete a request
only when the assignment is no longer required. If it is still needed but work
has not started, Open is the more suitable status.
Documents & Contracts
Access, modules & export
Share contracts selectively, provide templates and evaluate the contract list
Contracts often contain sensitive information. Artwork therefore separates
general permission for the contract area from access to a specific document.
Contract modules provide a shared working basis, while filters and Excel export
support evaluation.
For regular users, a contract is visible when at least one of the following
applies:
the person created the contract,
the person was explicitly granted access to the contract,
one of their teams was granted access to the contract.
Artwork admins can see all contracts. Project managers may open the
contracts of their project even without a share of their own. They find them
inside the project itself, provided they see the contract area there, that
is with the Manage contract modules & project contracts permission or
with budget access in the project. In the overall view under Documents →
Contracts these contracts appear for them only if they are additionally
shared or if they created the contract themselves. Two people working on the
same project may therefore see different contracts in their overview.
Anyone who can see a contract may also download, edit and delete it; there
are no graded shares such as “read only”. Who may upload new contracts, by
contrast, depends on the project and on the user permissions (see
Permissions).
Project access is not automatically contract access
Working on a project alone does not grant access to its contract files; only
the project management sees them without a share of their own.
Add the required people and teams to the contract, especially people assigned
a follow-up task for that document.
When uploading or editing, select the people and teams that genuinely need the
contract contents. A team share is useful when an entire organisational unit
regularly works with the document. An individual share is suitable for a
specific responsible person outside that team.
The contract list displays up to three shares directly. If there are more, the
additional counter opens the complete list, allowing you to review access at a
later date.
Contract modules appear to the right of the contract overview if you have
the View contract modules or Manage contract modules & project
contracts permission. They are not tied to an individual project or contract.
Typical examples are sample agreements, clause collections, appendices or
other reusable files used when drafting a contract.
People with Manage contract modules & project contracts use the upload
icon to add one or more files through file selection or drag and drop. If a
file fails, it stays in the dialog with its message while the others are
uploaded. The file is stored with its name; the dialog has no note field
Coming with the next update. Allowed file types and file size come from the “Contract” area of
the file settings. With View
contract modules you download a module through the download icon. Deletion
requires Manage contract modules & project contracts.
Module or completed contract?
Store general templates under Contract modules. A signed or
project-specific version belongs under Contracts, assigned to its project
and with its own access settings.
Several criteria work together: a contract must meet all of them. Within
legal form or contract type, one of the selected entries is enough.
Active criteria appear as filter tags above the table and can be removed
individually. The deadline period includes both its start and end dates;
it hides contracts without a deadline date. Your
filter selection is stored for your user account and is available again the
next time you open the contract page.
The selection in the filter dialog takes effect and is stored as soon as you
select Apply. Reset only clears the selection in the dialog; you have
to confirm that with Apply as well. Removing a filter tag is stored
immediately.
A filter does not change contract data or access. It only reduces the current
list within the contracts you are already allowed to see.
Select Export to create an Excel file containing contract data. The export
dialog provides the same criteria as the list. Active list filters are used as
the starting point and can be adjusted before export.
This is useful for deadline lists or internal evaluations by contract type,
legal form, artists' social security and foreign tax.
The export contains the same contracts as the list
Coming with the next update: those you created yourself, those shared with you
personally or through a team, and all contracts for Artwork admins. The
active filters apply as in the list.
Protect exported files
Once downloaded, an Excel file is outside Artwork's access control. Store and
share it in accordance with your organisation's privacy and retention rules.
Contract type and legal form lists are maintained administratively in the
project settings. People with the Project
settings permission can create or update their names and colours. Avoid duplicate or only slightly different entries, as these
unnecessarily split filters and evaluations.
Deleted contract types and legal forms are kept in the
recycle bin in the Project settings tab. There
they are called Project category - Contract type and **Project contracts
corporate form**. Opening it requires the Open trash permission;
restoring and permanently deleting additionally require Project
settings.
While an entry is in the recycle bin, the affected contracts show no
contract type or legal form, and the entry is missing from the selection
lists and the filter. After restoring, the assignment on the contracts is
back.
Notifications
Notification centre
Organise, process and archive changes, requests and tasks by topic
The Notification centre collects personal notices from all important
Artwork areas. Open it through Notifications in the navigation or the
dashboard quick link. Opening the page resets the general notification
indicator; individual messages remain unread until you process or archive
them. The page has two tabs: Notifications with the messages and
Settings for the personal delivery channels.
New document requests, requested documents that have been provided, and contracts shared with you or deleted
External access
External people have filled in their data or submitted content in shared tabs; an external access is about to expire
All nine groups are always listed. Whether messages arrive in a group
depends on the enabled modules, your permissions and your responsibilities. A
collapsed group shows its count of new messages; expanding it loads the latest
entries. Select Show more to retrieve older messages.
Duty roster committed: the message "Your shift schedule … week n has
been finalized" goes to every person assigned to one of the committed shifts,
also when the commitment was made through the approval workflow. The
message opens your personal roster in the affected week.
Changes after commitment: when a committed shift is changed or deleted,
only the people assigned to that shift and the planners entered on the
craft are notified. If no planner is entered on the craft, the message goes
to the craft manager.
Rule violations go to the people entered on the rule under Notify on
rule violation, and only while they hold View duty rosters or Plan
shifts or are artwork admins. The message links to the duty roster
starting on the day of the violation.
Rest time and consecutive days are additionally checked by artwork on
every assignment. The assigned person receives "You have been scheduled
with insufficient rest time" or "You have been scheduled for more than 10
consecutive days". Whoever schedules another person this way receives the
notice "Person scheduled with insufficient rest time" or "Person scheduled
for more than 10 consecutive days"; other planners do not receive it.
A notification shows its reason, the person who caused it where applicable,
and additional details. Depending on the process, relevant actions are
available directly in the message, for example:
open the calendar, project, budget, duty roster or task,
accept, decline or change the room of a room booking request,
review, edit or delete an event,
answer a budget or verification request,
view the history of a project, event or absence.
For notifications about changed events, View history opens the
event history: who changed date, time, room, event type, name,
admission, project assignment, properties or schedule and when, who
confirmed the room or converted the event into a planning event. The
event history can only be reached through these notifications, not from
the event form.
for return reminders on external material issues, choose Confirm
return or Not returned yet directly.
After a decision, the message may show who already accepted, declined or
deleted the item. This is helpful when several authorised people receive the
same request.
Act first, archive afterwards
Some messages require a decision. Artwork does not allow them to be dismissed
as completed while that action is still open. Process the item using the
buttons provided first.
The main section of a group contains new or unread messages. Passive notices
can be archived individually using the archive icon. Archive all moves all
archivable messages in that group; messages that still require an action
remain, and Artwork states their number. With many messages, archiving runs
in the background and may take a moment.
View old notifications opens the group's archive, Close archive
returns to the unread messages. The archive is a history
aid, not permanent record storage. Archived messages are automatically removed
after 30 days, and even unprocessed messages are eventually removed after one
year.
Archiving a notification does not delete or change the underlying project,
event, task or document. Only your personal notice moves to read history.
An organisation-wide announcement with a title, description and image may
appear on the right. It is also visible on the personal dashboard. People
with the permission System notifications and artwork admins can use
Change notification to all to create, update or delete an announcement
with an expiry date and time. Files of the type .jpeg, .svg, .png and .gif
are accepted as the image.
Such an announcement reaches all users, including external accounts. Use it
for genuinely organisation-wide information and ensure its text and image do
not contain confidential material.
In-app messages result from your responsibilities, project assignments and roles.
Email and hint in artwork can be controlled personally by area and message
type in the Settings tab. The link Settings for this type below a
message leads directly there.
Switching off email or hint does not remove messages from the notification
centre.
You are not notified about processes you triggered yourself. Automatic
reminders are the exception, for example about expiring sources of funding
or returns that are due.
Missing actions may be caused by insufficient permission or an item already
processed by someone else.
Personal delivery channels are explained under Email &
push.
Notifications
Email & push
Choose which notices are delivered outside Artwork for your account
Next to the Notifications tab, the notification centre has the
Settings tab. There you decide for your own account what reaches you in
addition to the messages in the notification centre: an E-mail and a
Hint in artwork. The messages in the notification centre itself are
unaffected.
The page is structured by area. Each message type has a row with the switches
E-mail and Hint in artwork and the selection E-mail frequency.
Changes are saved immediately. Only message types that can concern you are
shown: types of disabled modules are missing, and messages for duty roster
planning are only shown to people who can receive them.
Above the list there are tools for all message types at once:
Element
Effect
Search notifications
Filters the message types by a search term
Frequency for all e-mails
Sets the same frequency for all message types
Turn off all e-mails / Turn on all e-mails
Switches e-mail off or on for all message types
Turn off all hints / Turn on all hints
Switches the hint in artwork off or on for all message types
Restore defaults
After a confirmation, resets everything: e-mail and hint on, frequency to the default of each message type
The link Settings for this type below a message in the notification
centre leads directly to the matching row.
Each area has the switch All e-mails in its header. It switches e-mail on
or off for all message types of the area together. If only some types are
active, the switch carries the addition "(partially)". Individual message
types are controlled with the E-mail switch in their row.
For every message type with e-mail enabled, you also select a frequency:
Frequency
Use
Immediately
The email is sent soon after the message is created
Daily
Messages arrive bundled in a summary, daily at 9 a.m.
Twice a week
Summary on Mondays and Thursdays at 9 a.m.
Once a week
Summary on Mondays at 9 a.m.
You receive at most one summary per day. It only contains messages that are
still unread in the notification centre and were not part of an earlier
summary. It lists at most 50 entries per area; if there are more, it states
the remaining number with a link to the notification centre. The default for
new accounts is Daily; replies from external people are sent
Immediately by default.
Choose Immediately for processes requiring prompt action, such as room
requests or short-notice staffing changes. Summaries are better suited to
purely informational changes.
Immediate and summary emails arrive in the language you chose as application
language under Personal data → Preferences. This also applies to subject,
salutation and the links in the email. The sender is the
business email address from the
Tool settings,
otherwise the system mail. At the end of every email, Change notification
settings leads back to the Settings tab.
Event-related emails contain the line "Room | Event type | Event | Project |
Time" with the values of the affected event. Emails about a committed duty
roster state date, time, craft and project and link directly to the affected
view.
The second delivery channel is called Hint in artwork in the interface.
It is a short hint in the top right corner of the window that appears while
you are logged in to Artwork and disappears again after about eight seconds.
Clicking it leads to the notification centre.
It is not a push notification of the browser or operating system: if Artwork
is not open, you do not see the hint, but the message is in the notification
centre.
Hints are switched per message type with Hint in artwork or for a whole
area with All hints. There is no frequency for them: an active hint
appears as soon as the message is created.
Keep all areas active in which you regularly have responsibility.
Enable decision and deadline messages as email with the frequency Immediately and leave the hint in artwork switched on.
Move purely informational changes to a daily or weekly email summary.
Disable message types only when another reliable team process covers them.
After a few working days, check that important notices arrive in time without creating unnecessary distraction.
In-app remains the complete source
Switching off an email or a hint does not make the process disappear. Artwork's
notification centre remains the reliable overview of your messages and open
actions.
E-mail is switched off for the message type; the E-mail frequency
selection is then locked as well.
The message is set to a summary and therefore does not arrive immediately.
The hint in artwork is switched off, or Artwork was not open at that moment.
You triggered the process yourself: your own actions create neither a
message nor an email for you, automatic reminders excepted. The short hint
in artwork can still appear.
Your account is deactivated; deactivated accounts receive no emails, hints
or summaries.
You are no longer responsible for the underlying area and no new message is generated.
Another authorised person has already processed a shared request.
Do not disable delivery for sensitive or time-critical workflows without
confirming how you will reliably receive that information instead.
Notifications
Chat
Enable, start and configure direct and group chats within artwork
The chat is a direct line between users within artwork – for a quick
question to scheduling or a word within the craft, without email or
messenger. It does not replace notifications from the
notification centre: business processes such as
room requests or shift changes still run through notifications.
Open Your account via your profile picture and tick Use Artwork Chat
under Preferences. The setting takes effect immediately; accounts
created by invitation already have it set. People with the permission to
manage staff and admins can also change it for others.
When the chat is active, a round chat button with the number of unread
messages appears at the bottom right of every page. Only people with the
chat enabled can be found by others in the chat.
Type into Write a message and send with Enter (up to 10,000
characters). Messages arrive in real time and are stored encrypted. Your own
messages carry a tick as a read receipt: a single tick with the note
Unread, a double tick once the message has been read. Hovering over it
shows the time, in a group chat per person. A click outside the window
closes the chat; the conversation is kept.
In a group chat, every member can rename (pencil; up to 55 characters,
as when creating it Coming with the next update) or delete (trash can) the
chat. Deleting removes the chat with all messages for all members
and cannot be undone. Direct chats with one person can be neither renamed
nor deleted.
With the bell active, a short notice with name and the beginning of the text appears for every incoming message; clicking it opens the chat. Without the bell, only the number on the chat button remains. There are no email or browser notifications for the chat.
Change Chat position (arrows)
Chooses one of eight positions for the chat window, such as Bottom right (default) or Top left; your choice is saved.
What the chat is for
Short arrangements that do not change anything in artwork: "Can you take
over the rehearsal at 3 pm?" or "The rider has been uploaded to the
project". Binding decisions – swapping a shift, releasing a room, moving
an event – belong in the respective functions so they remain traceable in
the history and in notifications.
System & Administration
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 your permissions and
enabled modules: most menu items have their own permission in the System
settings module of the
user rights,
such as Calendar settings, Sources of funding settings or Budget
settings. Shift settings, CRM Settings and Inventory depend on permissions
of their own module. 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 and the
description of the Artwork API for connected programs. 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.
Appearance, communication, season, regional formats, external user sources, interfaces, modules, file rules and the mail account; plus the display of the installed version
The table follows the order of the menu. The System menu appears as
soon as you hold at least one of the related permissions and then shows
only the entries your permission covers. The External access entry is
reserved for artwork admins. Anyone who only holds the permission Manage
webhooks gets no menu entry and opens the
webhooks through the direct
address.
Since version 1.7.6, Material Sets is no longer a separate menu entry but
a tab under System → Inventory; people who only hold the set permissions
land directly on that tab. The former entry System → Projects → BI Export
has been removed; the export lives in the BI dashboard and in the project
tab. The Recycle bin below the System menu requires the permission
Open trash; which additional tabs it shows is decided by the
permissions of the respective modules (see
Recycle bin). Below the
recycle bin sits the User manual entry, which opens this documentation
and is visible to everyone.
Hide a module, define the season, choose currency and number format
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.
System administrators maintain branding, modules, file rules, external access and technical integrations. The mail account and login sources can only be changed by people with the artwork admin role.
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.
System & Administration
Tool settings
Manage branding, organisation, season, regional formats, login sources, interfaces, webhooks, modules, upload rules and the mail account
Tool settings under System → Tool Settings define Artwork's basic
appearance and technical framework. All tabs require the permission Tool
settings. There are three special cases:
The webhook section of the Interfaces tab also opens with the standalone
permission Manage webhooks.
In the Mail tab only artwork admins may save and send test
emails.
The page has eight tabs in this order: Branding, External User
Management, Communication & Legal, Regional formats,
Interfaces, Module visibility, File settings and Mail.
Below the title, the page header shows the Installed version of your
artwork installation. The Changelog link next to it opens the entry for
this version in the manual. If the changelog lists a newer version, it has
not been installed for you yet.
Login page, header of every email (200 pixels wide), expanded navigation, external access pages and PDF exports
Small Logo
Collapsed navigation (square, cropped at the edges) and the icon in the browser tab
Login Illustration
Image area of the login page
If no big logo is stored, the email header shows the small logo.
Files can be selected or dropped onto the upload area. Only PNG, JPEG and
WebP files up to 10 MB are saved. The Branding area in the
File settings can restrict this further but cannot extend
it. SVG files are no longer accepted for security reasons. Hint texts and
the file picker name exactly these formats Coming with the next update; the
page rejects any other file before the preview with the notice Only logos
and illustrations of the type .jpg, .png and .webp are accepted. Artwork shows a
preview and saves the selected graphic immediately. Use clear, high-contrast
logo variants and then check the login page, navigation and a typical email.
This tab holds organisation-wide sender and framework details:
Page Title: shown in the browser tab after the name of the page and
used as the sender name of system emails,
Our Organization: the organisation name, visible in your own account
and when an invitation is accepted,
Link to Legal Notice and Link to Privacy Policy as a full web
address starting with https://; the server also rejects addresses with
http://Coming with the next update, values already saved stay untouched.
Both links appear on the login page, on
the external access pages and in the footer of every email,
Invitation Email: sender of the invitation emails to new users,
Business Email: sender of almost all system notifications. If the
Mail tab has no From address of its own, emails are sent with
this address,
Email-FooterComing with the next update: the text appears in the footer
of every email above the links to the legal notice and privacy policy,
with the line breaks you enter,
Playing time window start and Playing time window end; the start
must be before the end,
the Letterhead: name, street and house number, postal code, city and
email. It appears only in PDF exports, currently in the per diem statement
(Per Diem Export) of
artist residencies,
below the big logo from Branding; empty fields are omitted there.
Fields save when you leave them if the content is valid. Email and web
addresses are checked. As long as one field is marked red, the page does not
save the other fields either; correct or clear it first. The season window (playing time window) is
functional: it is the default period of the BI Dashboard and the BI exports
and the reference for the season-related duty roster key figures (such as
free Sundays and days off). If no window or an invalid one is stored,
Artwork uses the current calendar year.
Do not change the season casually during reporting
A new season can shift default periods and figures. Set it deliberately at the
season change and inform people preparing BI, working-time or contract reports.
The Regional formats tab defines how Artwork writes numbers, amounts and
dates for the whole installation. Every selection is saved immediately; the
Preview below shows a sample number, a sample amount and a sample date
in the chosen format.
Field
Options
Default
Number format
Germany, Austria, Switzerland (German), Switzerland (French), United Kingdom, United States. Defines the thousands and decimal separators.
Germany
Currency
EUR, CHF, GBP, USD
EUR
Date format
The list shows sample dates: 31.12.2026, 2026-12-31, 31/12/2026 (day first), 12/31/2026 (month first)
31.12.2026
Number format and currency apply in the interface and in many PDFs and
exports, for example in the budget, in BI and for sources of funding. The
date format currently only takes effect in individual places of the
interface, such as budget comments, sources of funding, document requests
and BI snapshots. PDFs and exports keep their own date format.
The currency does not convert anything
The selection only changes how amounts are written. Values already entered
remain the same numbers. Houses in Switzerland set CHF here once.
In the interface this tab is called External User Management. Artwork
can obtain user accounts from a central source:
LDAP/Active Directory for directory services,
OIDC/SSO for login through an identity provider.
Only artwork admins may add, edit, activate and delete sources. With the
permission Tool settings alone you see the sources and can use Test
Connection and, for LDAP, Sync now. The collapsible box How does the
external user management work? at the top of the tab summarises the
following rules in the interface.
A source has a name, a type, the Active switch and a Default Role
that newly created accounts of this source receive.
If Group Mappings are stored for a source, its card lists the names of
the directory groups that grant permissions and roles in Artwork, marked
"including nested groups" where subgroups count as well. The list is
display only: the interface of version 1.10 has no dialog for creating or
changing group mappings. Ask the people who run your installation
technically.
OIDC: The account is created on the first successful sign-in through
the SSO button on the login page.
LDAP: The account is created on the first login through the normal
login form with email address and directory password, or in advance by
the synchronisation.
Synchronisation: It runs automatically every 30 minutes and on demand
with Sync now. It imports everyone the user filter finds. Newly
imported people receive a one-time welcome email. An inactive source
cannot be synchronised.
On every login and every synchronisation Artwork checks in this order:
If the identity is already known by its stable ID at the provider, the
linked account is used and its name and email address are updated.
Otherwise, if an Artwork account with the same email address exists, it
is linked to the provider. It keeps all roles, permissions and
assignments. With OIDC this only happens if the provider reports the
email address as verified.
Otherwise a new account is created with the default role of the source.
The email address only counts for this first link. Afterwards Artwork
recognises the account exclusively by the stable ID. An account can be bound
to one provider only; if the address belongs to an account of a different
provider, the login is rejected. People deleted in Artwork are not created
again, neither by the synchronisation nor by a login. Anyone who should
regain access is invited again.
Password login and Forgot your password? in Artwork are disabled for
these accounts; the password lives at the provider. OIDC accounts sign in
through the SSO button only.
For LDAP the directory takes precedence: if Artwork finds the email
address in an active directory, only the directory password counts.
People who are not in any directory keep logging in with their Artwork
password.
In the user overview, linked accounts carry an SSO badge; its tooltip
names the provider.
Users signed in via OIDC do not stay signed in permanently: once the
session expires, they must sign in again through the identity provider.
Group mappings are applied on every LDAP synchronisation. If a person leaves the
group, or a mapping is deleted or changed, the next run revokes the
permissions and roles granted through it. Whatever a person had already
received by hand remains.
Deactivating or deleting a source blocks sign-in
Linked accounts have no local password. If their source is deactivated or
deleted, these people can no longer sign in until the source is active
again. The accounts themselves are kept. For this reason the last admin who
can still log in locally cannot be bound to a provider. In an emergency
your IT can reset a single account to local password login on the server
with the command php artisan auth:break-glass.
LDAP requires server, port, base, service account, filter and security
options. New sources use Use StartTLS by default; alternatively, Use SSL
(LDAPS) is available. If both are off, the source warns that passwords are
sent to the directory in clear text. After an update, check whether your LDAP
server supports StartTLS and test the connection. The connection test in
the dialog lists the first users found, so you can judge the filter right
away.
Allowed Email Domains are optional. If set, the synchronisation and the
login only accept people with an address from these domains.
Under Provider you choose Google, Microsoft or Custom.
Microsoft requires your own Tenant ID; the generic values common,
organizations and consumers are not accepted because any Microsoft
account could sign in through them. Custom requires the Discovery
URL. It must start with https:// and be publicly reachable; addresses
in private network ranges are rejected.
For every provider you enter Client ID, Client Secret and the
Allowed Email Domains. Only Custom adds the requested scopes
(default: openid, profile, email), the Identifier Claim and the
Groups Claim; for Google and Microsoft they are fixed. Only the
immutable identifiers sub (default) and oid can be chosen as identifier
claim.
Under Allowed Email Domains you enter the domains of your users, such
as house.org, not the address of your Artwork installation. Only
identities with an address from these domains may sign in. An active OIDC
source needs at least one domain, otherwise it cannot be saved.
The option Trust email addresses from this identity provider controls
when new accounts are created: without it, Artwork only creates an account
if the provider reports the email address as verified. Microsoft Entra
usually does not send this confirmation. Enable the option only if the
connection is limited to your own tenant or directory.
The redirect address (redirect URI) shown in the dialog after saving must be
registered with the identity provider exactly as shown, otherwise the
provider rejects the login. Stored service passwords and client secrets are
never displayed again; they must be re-entered on every edit of a source.
Change only with IT ownership
Incorrect filters, identifiers or domain rules can omit, duplicate or
unintentionally admit accounts. Treat service passwords and client secrets as
credentials, test the connection and validate changes with selected accounts
first.
The Interfaces tab has up to three collapsible sections: Artwork
interface, Webhooks and Sage interface.
The Artwork interface manages API keys with a name, permissions,
creation and expiry date, and status. A new key is shown in full only when
it is created. Copy it immediately into the intended protected password or
secret store. Expired or revoked keys no longer work; Revoke cannot be
undone. Log shows the requests made with each key, with date, IP
address, method and URL. This tells you whether a key is still in use
before you revoke it.
Use a separate named key for each connected system. This lets you revoke one
integration without interrupting others. Never share keys in unsecured email
or chat messages.
The Artwork API page describes the permissions a key can
have and the data the interface provides.
A webhook sends data from Artwork to another system as soon as something
happens. In the webhook section of the tab you use Add endpoint to
create targets with a name, URL and subscribed events, review the
deliveries under Log, and redeliver failed deliveries with Send
again. The Active switch on an endpoint pauses its deliveries
without deleting it. The permission Manage webhooks is sufficient for this; the
other sections of the tab still require Tool settings. Anyone who only
holds Manage webhooks finds the entry Interfaces in the System menu
instead of Tool SettingsComing with the next update, which leads straight
to this tab; the other tabs stay hidden for that person.
URL: It must start with https:// and be publicly reachable;
addresses in private network ranges are rejected. For intranet
installations, check in advance whether the configured targets are still
accepted.
Endpoint secret: It is shown only once when the endpoint is created.
Store it in the receiving system right away.
Signature: Every delivery is signed. The receiving system verifies
the header X-Artwork-Signature as
sha256=HMAC_SHA256(timestamp + "." + body, secret); the timestamp is
sent in the header X-Artwork-Timestamp.
Retries: A failed delivery is retried up to five times, after
1 minute, 5 minutes, 30 minutes, 2 hours and 6 hours. The log shows date,
event, number of attempts and status for each delivery.
Deleting: Deleting an endpoint also removes its logged deliveries.
In version 1.10 only the test event webhook.test can be subscribed to.
Your IT triggers it on the server with php artisan webhooks:ping to check
reachability and signature.
If available in your installation, the Sage integration can import bookings
automatically into project budgets. The Sage interface section only
appears if Sage settings have already been created for your installation;
otherwise contact your technical support. It stores host, endpoint, user,
password, initial booking date (Query data from this booking date), daily
retrieval time (Query daily at) and the Interface enabled switch.
Save interface settings asks for confirmation and then tests the
connection. If the test fails, an error message appears; the values you
entered are saved nevertheless.
The daily retrieval only runs if Interface enabled is ticked and the
integration has also been enabled on the server. Without a time it starts at
08:00. It fetches all bookings from the initial booking date onwards. After
every import this date moves forward automatically to the last imported
booking date, so the next run continues from there.
Only https:// addresses are accepted as Host. An existing http
connection keeps running but requires an https address the next time you
save.
The stored password is no longer displayed: leave the field blank to keep it,
or enter a new one to replace it. If you change the host, you must enter the
password again. The option Verify TLS certificate of the Sage server is
enabled by default and should stay that way. Only disable it deliberately if
your Sage server on an internal network uses a self-signed certificate,
because the connection fails otherwise.
Authorised users can also:
start the retrieval again right away: the round refresh icon next to
Execute data retrieval from Sage again. Like the daily retrieval it
starts at the initial booking date. For a complete retrieval, clear this
field first and save,
under Import a specific booking date, import data for a cost center
(KTR), a period (From, Until) or both. Without Until only
the day in From is imported,
under Delete bookings, delete bookings by cost center and/or period.
Unassigned records are always deleted, assigned ones only with the
checkbox Also delete already assigned records. Artwork asks for
confirmation first,
use Open protocol to review the import and deletion runs and export
each run as CSV,
under Column Order, define the meaning and order of the first two
budget columns.
Import and deletion change budget data
Targeted imports can overwrite existing data. Deleting assigned records
directly affects project budgets. Before large corrections, agree a review
plan and inspect the Sage log and affected projects.
The trash icon at the top deletes all Sage data
At the top right of the section, next to the refresh icon, there is a trash
icon. It deletes all imported Sage bookings: unassigned ones, already
assigned ones and their comments. It only works when the interface is set
up and no import is running, and it asks first in the dialog Delete all
Sage dataComing with the next update. The deletion cannot be undone. For
targeted deletion use the Delete bookings section.
In the Module visibility tab each of these modules can be switched on
or off as an entry of the main navigation: Projects, Calendar,
Shifts (the duty roster), Inventory, Tasks (to-dos), Money
Sources (sources of funding), Users, Contracts (the Documents menu item), CRM,
Planning Calendar and Business Intelligence. Clearing a checkbox
hides the corresponding navigation entry immediately for all users until
the module is re-enabled.
Hiding is more than a hidden menu entry: the pages of the module are
blocked as well, direct links included. Two exceptions:
artwork admins still see and reach hidden modules. Only the planning
calendar is blocked for admins too while it is switched off.
Your own account and project pages stay reachable: without the Users
module you can still open your account and your operational plan, and
without the Projects module project pages that other modules need keep
working. In both cases only the overview page is blocked.
Hiding a module does not delete its data and does not change any
permissions; everything reappears as soon as the module is switched on
again. It does interrupt work, because users can no longer reach the area.
Inform the team and check dependent links, roles and workflows first.
In the File settings tab you define for the four upload areas
Project, Room, Branding and Contract:
which file types are accepted,
the maximum size of one file, from 1 to 1024 MB, via the slider or as a
number in the field next to it. The value is saved when you release the
slider, leave the field or press Enter; Artwork resets a rejected value to
the saved state.
Allowed types appear as tags and can be removed individually. The selection
list Select file types adds types Coming with the next update. In the
Project, Room and Contract areas it offers image formats (PNG, JPG, JPEG,
GIF, BMP, ICO, TIFF, WebP, AVIF), the entry * for all file types as well
as documents (PDF, TXT, CSV, JSON), Office formats, archives (ZIP, RAR),
audio, video and font formats. A removed type can thus be added back
individually. In the Branding area only PNG, JPG, JPEG and WebP are
offered, exactly what the branding upload accepts. The list does not offer
executable or active formats such as EXE, MSI, CAB, JS, CSS or SWF; settings
already saved with such types remain valid.
The setting affects future uploads in that area;
Replace file and files on sources of funding follow the same rules.
Existing files are not automatically converted or deleted. The Project area
also applies to uploads by external people in shared project tabs (see
External access).
New installations start with these lists and a limit of 150 MB per area.
When updating to version 1.7.8 the four lists are reset to them once, while
the size limits remain unchanged:
If you had allowed further types before the update, such uploads have been
rejected with a message since then. You can add such types again from the
selection list.
HTML, SVG, XML, PHP and similar active or executable content is not accepted
at any upload location, even if an area allows all types with *. They cannot be
added to the lists. Both the file extension and the actual content are
checked; the stored extension follows the content, not the file name. Profile
pictures, key visuals and all branding images accept images only.
The page shows how many MB per file the server currently accepts and warns
when a slider is set above it: values above the server limit only take effect
after IT raises the server settings. In the upload dialog, users see a clear
message when a file is too large (including the applicable limit), when its
format is not allowed in the area, or when its type is always rejected.
Allow only formats your users need and your security rules permit. A limit
that is too low blocks legitimate files; a very high one increases storage and
transfer requirements.
The Mail tab defines which mailbox Artwork uses to send all emails:
invitations, notifications, summaries. Empty fields fall back to the server
configuration (.env); the effective fallback values are shown below each
field.
Anyone with the permission Tool settings can view the tab. Only artwork
admins may Save and send test emails; everyone else sees the fields
locked with the note "Only administrators can change the mail settings and
send test emails." The reason: whoever controls the mail server can read
invitation and password links.
Section
Fields
SMTP server
Host, Port (1–65535), Encryption (Fallback (.env), TLS for STARTTLS, SSL for implicit TLS), Username, Password. The password is never displayed; an empty field keeps the stored password, and the checkbox Remove stored password (fall back to the server configuration) deletes it.
Sender (From)
From address and From name. When set, they apply to all outgoing mail. If left empty, Artwork uses the Business Email from Communication & Legal and the name of the respective notification.
Test mail
Recipient (prefilled with your address) and the Test mail button. Only saved settings are tested, so save your changes first.
Both come either from this tab or both from the server configuration;
Artwork does not mix them.
If you enter a Username, enter its Password too. Without a
password the settings cannot be saved.
If you leave both fields empty, Artwork logs in with the access data from
the server configuration. This only applies while the Host is also
the same as there. For a different host the server's access data are
never used; enter them here in that case.
If you change the Host, enter the password again. The stored password
belongs to the previous server and is not sent to a new one.
Below the access data the page states how the saved state sends:
Note on the page
Meaning
"login with the user name and password stored here"
The access data from this tab apply.
"login with the access data from the server configuration (.env)"
No user name is entered here; the server's access data apply.
"emails are sent without login. Many mail servers reject this."
There are no access data, neither here nor on the server for this host.
Red note "A user name is stored but no password."
The mail server will reject the login. Enter the password.
The browser does not fill in user name and password with your Artwork
login. Enter the access data of the mailbox by hand.
Changes take effect immediately after Save, including for mails already
in the queue. The test mail uses the same server and the same sender as
real mails. If it fails, the page names the cause as far as the mail server
reports it:
Message
What to do
The mail server rejected the login
Check user name and password
The mail server rejected the sender address
Enter a sender address the mailbox may send from. Without a From address of its own this is the Business Email.
The mail server only accepts emails after login
Enter user name and password
The TLS certificate of the mail server could not be verified
Check host and encryption, clarify the mail server's certificate with IT
If the server cannot be reached at all, the message stays generic; the
technical cause is then in the server log.
Involve IT and privacy for integrations, SSO and file rules.
Securely document existing values and credentials.
Make the smallest change and test the connection or display.
Run through one complete typical user workflow.
Inform the team and assign ongoing ownership.
System & Administration
Artwork API
Read Artwork data from other programs with an API key. Access, permissions, endpoints for room occupancy and inventory
The Artwork API lets other programs read data from Artwork, for example an
annual planning tool that needs to know which rooms are occupied. The API is
versioned (/api/v1) and always responds with JSON. Each program needs its own
API key with the matching permissions.
Open the tool settings, tab
Interfaces, section Artwork interface. This requires the
permission Tool settings.
Create a key with a descriptive name (e.g. the name of the connected program)
and select only the permissions the program needs.
Set an expiry date if needed. The key is valid until the end of that day.
Without an expiry date it expires after the standard lifetime, normally
one year. A later expiry date does not extend it: the earlier of the two
dates always applies.
Copy the key immediately into the protected secret store of the connected
program. It is shown only once.
The program sends the key with every request in the header
Authorization: Bearer <key>.
Permission
Allows
calendar:read
Read rooms, areas, events and event statuses (room occupancy)
inventory:read
Read inventory categories and articles (inventory)
ticketing:read, ticketing:write
Reserved for the Artwork ticket shop
All permissions are read-only except ticketing:write. A key cannot retrieve
any other data or change anything in Artwork.
Older keys whose Permissions column shows "None — created before
permissions were introduced" are rejected by these endpoints.
Permissions cannot be added afterwards; create a new key for the program.
The Log of a key in the same list shows whether and when it is used.
Rotating keys
To rotate a key, create a second one, switch the program over, then revoke the
old key. Both keys work in parallel in the meantime. A revoked or expired key
is rejected immediately.
All rooms not in the recycle bin with id, name, area (area_id,
area_name), room categories, capacity, colour and the details of temporary
rooms. Use areas=3,4 to get the rooms of specific areas.
Last day, inclusive; at most three years after from
rooms
no
Room IDs, e.g. rooms=31,32
areas
no
Area IDs; combined with rooms, both apply (the rooms and all rooms of the areas)
updated_since
no
Only events changed or deleted since this point in time
page, per_page
no
Page and events per page (default 500, at most 1000)
Every event with a room that touches the period is returned with its real start
and end times. Each event contains, among others:
id, title (project name; without a project the event name or event type),
project_id, project_name, event_type
room_id, room_name, area_id, area_name
start and end as timestamps (end = the room is free from then on),
all_day, start_date and end_date (first and last calendar day,
inclusive)
status (event status) and room_request_pending (open room request)
series_id for event series, updated_at, deleted_at
Not included: planning events, events without a room, events in rooms in the
recycle bin, and personal data, descriptions and comments. Deleted events only
appear in requests with updated_since, with deleted_at set.
Longer lists are split into pages: links.next holds the address of the next
page and is empty on the last page. A request without updated_since always
returns the complete current state.
All event statuses with id, name, color, order and default, plus
status_enabled. The id matches status.id on the events. This lets a
connected program decide which statuses count as occupied. If event statuses
are switched off in the event settings,
status_enabled is false and events have no status.
Inventory categories with their subcategories and articles, paginated (per_page default 15, at most 100)
GET /api/v1/inventory/articles
Articles, paginated (per_page default 50, at most 100), filterable with search, category_id, subcategory_id
GET /api/v1/inventory/articles/{id}
One article with inventory number, name, description, category, total quantity (quantity), properties and images
The former addresses without a version number (/api/inventory,
/api/inventory/articles) still return the same data but are deprecated.
Switch connected programs to /api/v1.
Recycle bin
Restore deleted items or remove them permanently after careful review
The Recycle bin is the safety stage between regular deletion and permanent
removal. Deleted items generally remain restorable for about 30 days and are
then removed automatically. Do not wait until the deadline if an item was
deleted accidentally.
The Recycle bin menu entry is unlocked by the Open trash permission
from the user permissions; Artwork
admins always have it. Which tabs you see inside and what you may do there
is additionally decided by the module permissions. The table under
Recycle-bin categories lists them per tab.
Permanent deletion cannot be undone
Delete permanently and Delete all remove data immediately. It cannot be
restored through Artwork afterwards. Check the name, category and dependencies
and confirm only the exact item intended.
Use the tabs to move between available object types:
Tab
Content
Visible with
Projects
Deleted regular projects and project groups
Open trash
Areas
Room/building areas and their assignments
Open trash
Rooms
Permanent and temporary rooms
Open trash
Events
Deleted calendar events with period, type and project context, individually or as a whole series
Open trash
Shifts
Deleted standalone shifts (without an event) with Deleted on, commit status and the number of assigned people
Open trash and Plan shifts; you only see your own crafts
Project Settings
Genres, categories, sectors, project statuses, contract types, company types and currencies
Open trash
Sage API data sets
Deleted, unassigned Sage bookings with booking text, creditor and document number
A Sage permission for project or global Sage data
Accounts and Cost Units
Deleted accounts and cost units from the budget settings
Budget settingsComing with the next update
Articles
Inventory articles including category and quantities
Delete inventory
Budget
Deleted budget templates. The budget table of a project is not listed separately in the recycle bin; it goes and returns with its project
Global budget access
CRM contacts
Deleted CRM contacts and contacts merged away as duplicates, with contact type and deletion date
Manage CRM
Artwork admins see all tabs. A missing tab therefore does not necessarily
mean no deleted items exist; you may not have permission for that area.
A visible tab does not automatically allow every action. Restore and
Delete permanently additionally check the permission of the feature
area: Room administration for rooms and areas, Project settings for
the project settings, and the delete permission for the respective entry
for projects and events. Restore seriesComing with the next update
requires the delete permission for every event of the series. Delete
all in the Projects tab requires
Delete all projects. Without the permission Artwork shows the page No
permission.
Many tabs provide a search. It filters on the server and resets the list to
the first page. Projects, events and shifts are sorted by deletion
date, with the most recently deleted at the top. The search in the
Events tab also matches the project name. Use the X beside the search field to clear it. Larger lists are
split across pages.
Project rows can show their name, shares and recent change information. Events
show the period, event type and previous project; events from a recurrence
are marked Part of a series. Articles include category, total quantity
and individual stock units when detailed quantities are used. CRM contacts
show the contact type and Deleted on.
Select the correct tab and identify the item unambiguously using search.
Choose Restore from its action menu.
Open the original feature area and verify that the item and its links are visible again.
For projects, rooms and events, pay particular attention to access, assignments and dependent planning.
Restoring returns the object to its former area. Whether every relationship is
immediately usable depends on whether linked objects still exist. If an
associated room or master-data category was permanently deleted, follow-up
work may be required.
A project comes back with everything of it that is in the recycle bin: its
events including their shifts, timelines, comments and sub-events, its
checklists, its budget table and its contracts. This also applies to events
of the project that were deleted individually before the project.
Coming with the next update
The project files, the comments of the project and the tasks in the
checklists come back as well, and so do the categories of the project, which
stay attached to the project when it is deleted. For files, comments,
checklists and tasks: what went to the recycle bin together with the project
comes back. Anything you deleted individually before stays in the recycle
bin.
Project first, then the event
If you restore an event or a series while its project is still in the
recycle bin or has been permanently deleted, the event comes back without a
project. The link does not return even if you restore the project later.
Restore the project first; its events come back with it.
Nothing is permanently removed any more when deleting recurring events:
whether you delete “Only this event”, “This and following”, or “Whole
series”, all affected events land in the Events tab. There, an event that
belongs to a series offers Restore series in addition to Restore.
This brings every event of that series back from the recycle bin; no date is
created twice. How series are created and edited is described under
Editing series.
When you restore an event, only the shifts that were deleted together with it
come back; they are checked against the working-time rules again. Open room
requests of a restored project, event or series are open again, without
Artwork sending new emails for them.
The Shifts tab only holds standalone shifts, that is shifts without an
event. Shifts attached to an event are deleted with their event and come
back with it from the Events tab. For each row the tab shows date, time,
craft, room, Deleted on, whether the shift was Committed and how
many assigned people are restored with it. A shift whose room is itself in the recycle bin is locked with
room in recycle bin: restore the room first. After Restore the shift
and its people are back in the duty roster, and the rule check runs for it
again.
In the CRM contacts tab you restore deleted contacts or delete them
permanently. Contacts that were merged away when
merging duplicates
are also listed here. After restoring, check the contact's project links,
because they were transferred to the main contact during the merge.
Delete permanently removes one row. The red recycle-bin icon at the top of
a tab offers Delete all for the entire current category. Both actions ask
for confirmation.
Search does not limit Delete all to the currently visible results: the
action always deletes the entire recycle-bin category, including entries on
further pages. In the Shifts tab it covers the shifts of the crafts you
may plan. Use it only after a complete review.
When a project is permanently deleted, its events in the recycle bin, its
files and its budget table disappear with it.
Project Settings combines several kinds of entries. The type label in
front of the name tells you the kind, for example Project category -
Genre, Project category - Project status, Project contracts -
corporate form or Project contracts - Currency. Check this type before
restoring or deleting it.
Restoring makes a master-data option selectable again. Permanently deleting it
can make historical assignments and evaluations harder to understand. A
contract type, corporate form or currency that a contract still uses (even a
contract in the recycle bin) cannot be deleted permanently; Artwork refuses
with a message such as This currency is still used by contracts and cannot
be deleted permanently.Coming with the next update
Coordinate such deletions with people responsible for projects, contracts and
budgets.
A nightly run permanently removes entries that have been in the recycle bin
for more than 30 days. This applies to all tabs: shifts, events, projects,
rooms, areas, articles, CRM contacts, Sage data sets, accounts, cost units,
budget templates and the project master data. Events of a deleted project
are not removed individually but together with the project.
The run skips entries whose permanent deletion would change data that is
still in use. They stay in the recycle bin until the dependency is
resolved:
Entry
Stays as long as …
Project
it still contains events that are not in the recycle bin
Room
it still contains events or shifts
Area
rooms are still assigned to it
Account, cost unit
the same number has meanwhile been assigned to an active account or cost unit again
Contract type, company type, currency
a contract still refers to it
Because the run takes place once a night, an item does not disappear at the
exact minute of its thirtieth day. Never rely on that remaining time for a
necessary recovery.
The recycle bin is not an archive
Do not deliberately retain data in the recycle bin. Records that must be kept
belong in their designated feature area or an approved document archive. The
recycle bin exists solely for short-term recovery from mistakes.