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.
Access and responsibilities
Sharing distinguishes two roles:
| Role | Meaning |
|---|---|
| Responsible | 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.
Tasks on a source
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.
Expiration and remaining-budget reminders
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.
Remind before expiration
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.
Remind at a remaining-budget threshold
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.
Store documents
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.
Follow the history
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.
Recommended division of work
- 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.
Last updated on