Tool settings

Tool settings define Artwork's basic appearance and technical framework. All tabs require permission to change tool settings. Coordinate changes with internal IT and, for login sources or interfaces, the respective system owners.

Branding

Upload three central graphics:

Files can be selected or dropped onto the upload area. JPEG, SVG, PNG, WebP and GIF are supported. Artwork shows a preview and saves the selected graphic. Use clear, high-contrast logo variants and then check the login page, navigation and a typical email.

Communication & Legal

This tab holds organisation-wide sender and framework details:

• page title and organisation name,
• HTTPS links to legal notice and privacy policy,
• invitation and general business email addresses,
• email footer,
• season window start and end,
• letterhead name, street, postal code, city and email.

Fields save when you leave them if the content is valid. Email and web addresses are checked. The season window is functional: it is used as the default period for the BI Dashboard and as a reference for season-related work and contract evaluations.

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.

A source has a name, type and active status. Once configured, you can test, edit or delete it. Group mappings show which external groups Artwork takes into account and can include nested groups.

LDAP requires server, port, base, service account, filter and security options. OIDC requires a discovery address, client ID, client secret, scopes, unique identifier, group claim and allowed email domains. The redirect address shown after saving must be registered with the identity provider.

Interfaces

Artwork API

The Artwork interface manages API keys with a name, 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.

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.

Sage interface

If available in your installation, the Sage integration can import bookings automatically into project budgets. It stores host, endpoint, user, password, initial booking date, daily retrieval time and enabled status.

Authorised users can also:

• restart a complete retrieval,
• import by cost unit and/or date range,
• delete bookings by cost unit and/or period,
• optionally remove already assigned data,
• review and export import/deletion logs,
• define the meaning and order of the first two budget columns.

Module visibility

Each available module can be enabled or disabled in the main navigation. Clearing its checkbox hides the corresponding navigation entry for all users until it is re-enabled. Administrators may retain exceptional access depending on the system context.

Hiding a module does not delete its data, but can effectively interrupt work because users can no longer reach it through navigation. Inform the team and check dependent links, roles and workflows first.

File settings

For each upload area, define:

• which file types are accepted,
• the maximum size of one file, from 1 to 150 MB.

Allowed types appear as tags and can be removed individually. The setting affects future uploads in that area. Existing files are not automatically converted or deleted.

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.

Safe change sequence

1. Record the objective and affected users.
2. Involve IT and privacy for integrations, SSO and file rules.
3. Securely document existing values and credentials.
4. Make the smallest change and test the connection or display.
5. Run through one complete typical user workflow.
6. Inform the team and assign ongoing ownership.