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.
Core concepts
| Concept | What it means |
|---|---|
| Project | 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). Statuses can be marked as a "planning status" — events of such projects then appear as provisional. |
| Properties | Category, genre and area — 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. |
Everything is composable
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 write permissions are also granted per component. What your project view looks like therefore depends on your venue's configuration; this documentation describes the default tabs as shipped.
A typical project workflow
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 and edit the project, 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.
Project Overview & Creating
The project list, search, filters, pinning — and creating new projects or project groups.
The Project View
Tabs, team, checklists, comments, documents & contracts, printing.
Project Schedule
Create and bulk-edit project events and connect them with calendar and shift planning.
Documents & Additional Data
Documents, contracts, requests, artist residencies, and material issues.
Project Budget
Budget table, positions, verifying & committing, templates, Sage integration.
Business Intelligence
Attendance, tickets, revenue, capacity, production data, snapshots, and Excel export.
Project Settings
Categories, genres, areas, project statuses, creation settings, project roles.
Tabs & Components
Assemble the project view from components — the construction kit behind the tabs.
Permissions
| Permission | Allows |
|---|---|
| Read access to all projects (Leserechte für alle Projekte) | View all projects (otherwise only your own or team projects) |
| Create & edit own projects (Eigene Projekte anlegen & bearbeiten) | Create projects and edit your own |
| Write access to all projects (Schreibrechte für alle Projekte) | Edit any project |
| Delete right for all projects (Löschrecht für alle Projekte) | Delete any project |
| Be project manager (Projektleitung sein) | Be assignable as project management |
| Define system settings for projects (Systemeinstellungen für Projekte definieren) | Manage the project settings and the tab construction kit |
There are additionally rights per project (write access, delete right, budget access — granted via the project team) and visibilities per component.