Customers and customer portalSelf Service and employee pool

Self Service: Permissions and customer employee pool

Differentiate between own and all projects and check immediate pool changes.

Self Service: Permissions and customer employee pool

Self Service and orders are separate permissions

In the customer portal, Orders is the ordering process; Self Service is your own project planning. A visible menu item does not mean that you may perform every action in it. The available functions are configured by customer role.

These rights are granted separately for Self Service:

  • Create Self Service project
  • View all Self Service projects and View own Self Service projects
  • Edit all Self Service projects and Edit own Self Service projects
  • Delete & cancel Self Service project

For customer users, “own” means: you are stored as the responsible client buyer of the Self Service project. That is not automatically every order you have ever created. For agency users, the creator is used for this ownership check. In addition, the project must belong to the appropriate customer/agency area. Self Service rights do not grant blanket edit access to normal orders.

Open Self Service in the main menu. The submenu for project creation or loading a template appears only with the create permission. The basic workflow is explained in Create project, Project planning, and Publication and assignment. Note the Self Service differences there; a saved project or a loaded template is not yet proof of publication or of a delivered invitation.

If an action is missing, have exactly the required permission and responsibility for the relevant project checked. Reloading multiple times does not extend permission. The customer roles matrix describes where rights and conflicts between order and Self Service functions are managed.

Edit a customer's employee pool

Check first: Moving is already a save action and can trigger emails. Do not use the pool as an informal selection for later.

  1. In the agency, open Customers → desired customer → Employee pool. The tab appears when Self Service is available. Save a new customer first before editing its pool.
  2. Active employees who are not yet in the customer pool are on the left; active employees in the customer pool are on the right. Filter the visible entries by name or email.
  3. Move the desired people to the right. The assignment is requested immediately; the general Save button in the customer profile is not needed for this.
  4. To remove them, move the people back to the left. This also requests the removal immediately. Open the tab again and check whether the people are on the expected side.

Permissions: Visibility of the tab and permission to change it are different. The permission Edit all Self Service projects is required for these pool changes; a pure view right or only the right for own projects is not sufficient for this pool action.

Notifications: For people actually added, an email is triggered for each person and each configured customer recipient. If no recipients are stored for the customer, no agency recipient list is used as a fallback. The event recipients are configured separately. Successful pool assignment is not delivery confirmation of the email.

If someone is missing: Active, not deleted employees from the agency area are offered. The left candidate list is limited to 200 entries; the visible name/email filter filters these already loaded entries. A missing result therefore does not prove that the person does not exist. Have the status and pool assignment checked specifically. After an error message or unclear feedback, do not trust only the moved screen row; reload.

Pool assignment does not assign the person to any specific shift yet. Removing them from this pool is not, in itself, a cancellation of existing shift assignments.

Self-Service person list: entry point and rights

The following guide concerns Employees in the Self-Service customer area and My lists, not the separate customer portal personnel overview. List management assigns people to customer lists; it does not plan a shift and does not send an invitation.

As a customer user, open Employees in the main menu. Access requires at least one of the six Self Service permissions mentioned above. View/edit own Self Service projects can open the area, but does not automatically allow list changes.

ProcessDifference you should check
Load people and customer listsSelf Service access and assignment to customer and agency. The people overview loads active people from the customer pool, not an agency population you can freely choose.
Save as new list / My lists in the people overviewThe buttons appear with the list management right (original name Manage Employee Lists).
Save new list, rename, delete list, add or remove memberThe actual save check requires Edit all Self Service projects. The right for own projects alone is not sufficient here; the action does not belong to an individual project.
Deleting a listThis is a list change, not the right to delete/cancel a Self-Service project and not the deletion of a person.
Export and messageSeparate active buttons; do not equate this with the visibility right of the two list buttons. Profile column rights are not a guarantee for export.

In the list editor, the actions there are available without the same additional button hiding. A visible button therefore does not prove successful save permission. If access is denied, have the specific permission, your customer/agency assignment, and the selected customer list checked. My lists means lists for this customer, not exclusively lists you created personally. Do not assume department rights for orders are additional people filters: there is no department selector in either of these overviews.

The agency manages the customer pool via the customer profile described above. Customer lists and agency lists remain different list types; a list with the same name is not automatically the same list. Import, creation of new people, sedcard generation, and bulk activation are not integrated into these two overviews. Do not use Save as new list as a substitute for those.

Search, sort, and check the selection of people

  1. Enter a search term in the Search Employee field. Every keystroke reloads the first page of results. A single search part is checked against first name, last name, email, mobile number, and employee number. For multiple parts separated by spaces, the first is used as the first name and the second as the last name; this is not an arbitrary full-text search.
  2. The table shows checkboxes, photo, first name, last name, age, first address as place, mobile number, and email. Use the sortable headings and the page selector to change the display, not the profile. If sorting fails, especially for calculated age, switch back to first or last name and reload; an empty table can also be a failed query.
  3. At the start, all matching people are considered selected, not only the first page. Individual checkmarks remove people from the selection. Before a bulk action, check search, filter, list, and deselections together.
  4. Watch the header checkbox: If no people have been deselected yet, a click removes only the currently loaded rows from the selection. Other pages remain selected. If deselections already exist, the next click resets all deselections. It is not a reliable button for “select nobody in the entire pool.”

The selection count is only an indicator: deselections remain when you change the search or filter and are not reliably reduced to the new set of results. Do not rely on the number alone. In the list editor, selecting or clearing a list resets search and deselections; check again afterward. The checkmarks are selection state, not saved list membership.

The overview enforces active employees in the customer pool and takes the customer-side exclusion list into account, unless this is explicitly included. Not every follow-up action uses exactly the same search conditions: New list and message retain the search text, Excel does not. In addition, the overview adds the customer reference for exclusion separately; list creation, messages, and export do not add it in the same way. Therefore, visible results and the follow-up result are not generally the same. Check a newly saved list or file before further use.

If people are missing, first clear the search, check the filter and the selected list, then have administration check the active status and existing pool membership. If a loading error is shown, do not assume deletion.

Open filters and apply them to the people overview

Open Filter, change the required criteria, and wait for the result calculation. With Apply selected filters, you transfer the criteria to the people overview; it then reloads page one. The x closes the dialog via its reset path and is not the apply button. Changing a filter does not save employee profiles and does not create a customer list.

In the customer context, Customer pool offers the customer's own lists with the optional condition “on all selected lists”. The three agency list types and the marketplace switch are not equivalent additional list filters here. Agency rating and other documents have their own visibility rights. Changing the location is not enabled in this view.

For the individual filter fields and the result paging list, see Lists and employee filters. Pay explicit attention there to the customer view: internal agency notes, imported job history, images, work information, bank details, and job interests are not customer filter areas. Loading a filter template is not list creation. In particular, the explanation of a CV filter is not proof that a CV was uploaded.

Before a follow-up action: Check the people overview again after applying. The result display in the filter and the checkboxes in the overview are different states; existing deselections in the overview are not automatically cleared when applying. An unchecked filter result count is therefore not a recipient list.

Create a new customer list or copy one from an existing list

  1. Narrow the people in Employees and check the deselections. In the list editor, either choose an existing list as the starting point or leave the list selection empty for the pool.
  2. Select Save as new list. The dialog is called Save as list; the name field may show the original placeholder List name. Enter a unique name, preferably 2 to 50 characters. The field contains these length requirements; the save action itself checks in particular that something remains after outer spaces are removed. An already existing name is rejected during creation.
  3. Click Save. While the request is in progress, the button is locked. The x closes without this save action. There is no automatic saving while typing here.
  4. After a successful response, the dialog closes. In the people overview, open My lists for verification and select the new list. In the list editor, the lists are reloaded and the returned new list is selected directly; search and deselections are reset in the process.

A new member list is saved from the people determined at the time of the action, not from a continuously updated filter rule. If you copy one, the source list remains. An empty result set can also create an empty list. Duplicate names are checked when creating the list; this does not imply the same duplicate check when renaming later.

If the name is missing, the dialog stays open and shows an error. If a request fails, the button becomes available again; the dialog remains open for correction. If the response is unclear, first check My lists before creating the same list again. A saved list is neither a pool assignment nor a shift assignment or message.

Select, rename, and delete My Lists

Open My lists and choose a customer list at the top via Search/select list. The name search in the selection field searches the loaded list names. Without selecting a list, the active customer pool is shown. The x only clears the selection and reloads the pool; it does not delete any list. When changing or clearing the selection, person search and deselections are reset.

Rename: Select a list and click the pencil (edit list, if the translation is missing). In the dialog, list name shows the current name. Change it and click Save. An empty name is rejected. While the request is in progress, the input, Cancel, and Save are disabled. After success, the dialog closes and the list selection is updated. Cancel discards the unsaved change. If an error occurs, the dialog remains open; after an unclear response, reload the list and check the name.

Delete list: The trash can next to the list name (delete list) opens a confirmation prompt. Decline if you only wanted to clear the view. Only confirming requests the deletion. The selected list and its memberships are deleted, not people, the client pool, or shift assignments. After success, the selection is cleared, the pool is shown, and the list selection is reloaded. There is no undo button here. If an error occurs, do not conclude from individual rows disappearing that the deletion was successful; reload the list.

The Employees link takes you back to the people overview. Switching views does not replace a successful save response. No general “save all” button bundles these changes: renaming, creating a list, confirmed deletion, and adding a member are separate save actions.

Add people to a list and check removal

First select the correct list in My lists. On the right, Employee by name or email appears. Type part of a first name, last name, or email and click the matching result. The click requests membership immediately, without another save button. After success, the member table and the offered people are reloaded. A person who already belongs to the list is not offered there again.

If someone is missing: The selection loads at most 200 active, not deleted agency pool members who are not yet in the chosen list. The text input filters these loaded results; in this interface it does not start a new server-side search. If no result appears, have pool membership and status checked. Existing membership is a prerequisite: this process does not add anyone to the client pool anew.

Known limitation when removing: The table provides a remove icon for each person. In the reviewed version, however, this action does not pass the person ID in the form expected by the list editor. Therefore, this click does not request a removal; no follow-up confirmation prompt appears either. The visible action is not proof of a removed membership. Do not click repeatedly or delete the whole list as a substitute.

As a separate path, you can open the person profile and change the client list selection in Client pool, provided you have the required permission; see the profile section below. After each change, reselect the relevant list and check the membership. In case of errors, the previously saved state is authoritative, not just a local selection marker. Removing a list membership does not deactivate a person and does not remove them from the client pool.

Choose Excel columns and verify the actual export

  1. First check the filters or the selected list and any deselections. Select Export.
  2. Select the required additional columns: employee ID, address, email, mobile number, age, language, shoe size, upper-body size, driving licence, last assignment, number of assignments, roles, employee lists, employee number, and last login. These checkboxes select export fields, not people. A status field is not included here. When reopened within the same view, the field checkboxes remain selected.
  3. Click Export Excel. While the request is in progress, the button is disabled. If the response returns a file path, the file opens in a new window and the dialog closes. If no window appears, check the browser’s download/pop-up settings. The x closes the dialog without exporting.
  4. Before sharing the file, compare it with the intended number of people and the required columns. If an error message appears, the button is enabled again; without a returned file path, a successful download has not yet been confirmed.

Important: Free text search is not passed to the export from either the people overview or the list editor. A screen limited to one name can therefore export more people. Use a controlled client list or the appropriate filters and check the file. The export respects deselections; it is neither a save of the list nor a message sent to the people.

The details for assignments, roles, last assignment, and client lists are determined for the client context. This is not a promise that all export columns follow the same visibility rules as the profile. Also note the differences described above between the overview and follow-up actions in exclusion cases. Further reading: Self-Service: Export and messages.

Send a message to the verified selection of people

  1. Check the filter, selected list, search text, and individual deselections. Open Send message. When opened, subject and text are cleared and Push Notification is preselected.
  2. Choose Push Notification or Email. Fill in Subject and the message. Both must be filled in for the action. In these two dialogs, there is no active SMS switch, no message template loader, and no button to attach a file.
  3. Check the selection before Send: unlike with Excel, the search text is passed along. In the list editor, the selected client list is also used. Without selecting a list, the starting set is the pool. The differences to the visible overview in exclusion cases also apply here.
  4. Send starts the message process immediately; there is no additional confirmation prompt. While the request is in progress, the button is disabled. The x closes the dialog without this sending action.

After a successful HTTP response, the dialog closes. If the explicit recipient count is zero, “no employees selected” is reported. A success message or counted recipients do not prove delivery: Push is queued, and email uses the agency sending system and requires its complete email configuration. A client SMTP setting is not a verified substitute here for missing agency configuration.

If there is an error, do not send again blindly. Individual recipients may already have been processed. Even a technical response without a reliable recipient count can lead to a misleading success message. Therefore check the feedback and the actual receipt with the intended recipient; if the response is unclear, have administration or support check the sending status before retrying. A message from the overview is not the same path as communication from an individual profile.

Person profile: client lists and automatic save actions

The person link opens the existing employee profile in the self-service context. This is not a new profile and not a switch to the separate customer portal personnel ratings overview. The actual profile rights and the client context still apply; a visible or greyed-out area alone is not permission to make changes.

Change a person’s client lists: Open Client pool in the profile. The multi-select there contains the client lists and the current memberships. Add a list or remove a selected list. Each change immediately requests the saving of the complete desired client list selection for that person. There is no general save button afterward and no additional confirmation prompt. Existing pool membership and Edit All Self Service Projects are required. Clearing the selection removes this customer’s memberships, not the person from the pool. After an error, the local selection is not automatically reset to the confirmed server state: reopen the profile and then check the list.

Do not confuse this with a hidden field: A similarly named client list selector within the agency area Employee lists is not accessible to customer users. Use the actually visible Client pool area. Likewise, the customer’s own internal note in the reviewed profile is embedded under an area hidden from customers; here it is not an operable automatic save path, even though the software contains a save function for it.

General profile autosave is not the same path for customer viewers as the active client list selection. The profile guide describes additional profile areas and their limitations; do not transfer agency actions wholesale to your customer view. Import, sedcard, or individual communication are not additional actions of the two person tables described here.

Self-service filters in detail and table options

Getting started, default values, and applying

This guide supplements the people overview Employees → Filter in Self Service. My lists does not have its own filter dialog: there, the client list selected at the top together with the person search determines the table. Filters from the people overview are not automatically transferred into the list editor.

When the people overview is opened fresh, active is preset; a status selector is not shown in this filter. Lists, date limits, attributes, and languages are initially empty, yes/no checkboxes are off, and both distance sliders are at 0. Neither a project nor a default assignment location is taken from the customer settings. The search remains within your own client pool and the agency context. The dialog is not generally read-only: in addition to search criteria, it contains its own save and sending actions. A greyed-out area is not a promise about permissions.

  1. Open Filter and expand the desired section. Multiple sections may be open at the same time. Choose specific criteria; several different sections restrict the result set together.
  2. After making changes, wait for the new result display. Number fields sometimes only trigger recalculation when leaving the field. Select date values via the calendar and then check the display. Remove no-longer-needed rows completely instead of leaving an empty criteria row in place.
  3. The number selected / matching opens the result side list. The name search there searches only first or last names in the loaded results. Select all applies to all filter results, not just the rows currently visible by name. Deselect all switches to explicit individual selection; then check the desired people.
  4. Apply selected filters recalculates and then loads page one of the people overview. This is not a save as a template, client list, or profile change. Individual deselections in the filter and the separate deselections in the overview take effect one after the other; the overview keeps its own existing deselections. The display in the filter is therefore not a reliable count of later export or message recipients.

Close and reset are different: the x closes without the apply step and without immediately reloading the overview. Still, do not rely on everything being discarded: directly changed criteria can remain in the overview’s memory and affect the next search. For a controlled restart, use Clear filters, set the desired criteria again, and choose Apply selected filters; then also check the overview deselections. Reset removes criteria and individual filter selections, restores active and distance 0, and is not a deletion of saved templates or lists. A role/client reference taken from a template can remain. If the results are inexplicable, reopen the people overview and start without a template.

Field groups in the client filter

The following references apply only to the explicitly named shared fields, not to all agency functions on the linked page.

SectionSpecific operation and limitation in this client view
Personal detailsGender male/female/other, smoker and video self-portrait each yes/no, age from/to and number of children from/to. The shared fields are explained under Person details, ratings and comments; do not transfer status and internal comments there. Multiple genders are alternatives. For smoker, tattoos, and piercings, no also includes values that are not set. A children-count limit of 0 does not reliably restrict the search to people without children.
RatingsCustomer rating from/to is available; agency rating only with the View Agency Rating right. Both search rating averages in the agency context, not only the rating you personally submitted. If no rating is present, 0 is considered; an empty lower/upper limit corresponds to 0/5. Select or clear stars and wait for new results.
Client poolUnder Client employee lists, choose one or more of your own client lists. Without selecting a list, the client pool remains the starting set. Normally one of the selected lists is enough; with the switch for all lists, the person must belong to every selected list. Remove a selection chip or clear the selection to remove this narrowing. This does not change membership. The client pool is not a freely switchable customer and not a marketplace. See only the paragraph about the client view under Combine lists and client pools.
Future jobs / Job historyChoose From and/or To, leaving one boundary open if needed. Future jobs checks assigned or confirmed assignments in the selected period, but does not additionally force a date after today. Job history checks actual dates before today, not just confirmed assignments. Neither is a client-exclusive proof of assignment nor an availability check.
AppearanceEye/hair color may be selected multiple times; body height, shoe size, top size, trouser width/length from/to; visible tattoos/piercings yes/no. Operation of the shared fields: Assignments, appearance and pictures, appearance paragraph only. Pictures and imported history cannot be selected here.
SkillsCV uploaded is not a reliable proof of a CV file: the checked entries are training, work experience, or language entries. For training, work experience, and languages, use Add criterion, set the desired values, and use the remove icon only to delete the search line. Multiple rows are initially alternatives; the respective all switch requires every row. The full fields and certificate limits are under Select competencies precisely.
AddressPrimary/secondary address distance are separate sliders, initially 0; a location field is not available here. Without a stored starting address, the sliders do not impose any distance restriction. Only an appropriate loaded template can bring a starting address. If address resolution fails, a displayed result set is not proof of the desired distance. “Valid from” for the primary/secondary address can be restricted independently by date limits.
General availabilityHere the form without a role selector applies: add or remove weekday and from/to time; also set date ranges. Use complete weekly rows and choose To after From. Incomplete/invalid weekly rows are skipped; minutes are rounded up to the next hour. Date ranges exclude overlapping stored unavailability; they do not write to a calendar. Remove empty date rows. See Address and availability, paragraph without role reference.
Transportation informationPublic transport subscriptions, driving licence categories, driving licence document yes/no, driving skills, car availability, make/body/size and car sharing as under Mobility, job interests and further documents, only mobility and documents. Within the public transport, driving licence categories, or driving skill group, multiple checkmarks are alternatives, not a requirement for all categories. Car availability and car sharing are also checked as alternatives.
Further documentsOnly when document types exist and with View Further Documents. Choose Yes or No for each displayed type; both or neither do not narrow that type. Multiple individually restricted types must all match together. The search is for a non-deleted document entry, not a validity or content check. Type names come from the respective language version, or alternatively English, German, or the stored name.

Occupation selection: Open the occupation selector in a work experience row, choose the category first and then the entry. Back returns to the category list; clicking outside closes the selector. The selection applies only to this search row. Level is a separate selection for the type of employment/experience and is checked against the stored value, not as arbitrary search text. For languages, the level is a specific level, not a minimum level. For mother tongue, the certificate selection disappears; certificate values already set can still apply. Reset them before switching or remove the language row and create it again.

Internal agency comments, the three agency list types, imported job history, pictures, work information, bank details, and job interests are not shown in this customer filter. The similarly labeled customer list field within the agency list area is also not a second accessible selector. The rights for agency rating and further documents control the display; this does not imply any general API security guarantee.

Templates and lists directly in the filter

Load template: Click Load template, search via Search template, and choose a name. This closes the template dialog and recalculates the filter, but does not yet apply it to the overview via the Apply step. For customer users, templates from their own customer are loaded. The template contains not only criteria, but also saved individual selections/deselections. When loading, numerous agency fields are removed; inactive statuses are set to active, with a warning if necessary. Even so, a template is not a guaranteed empty customer filter: hidden residual values, the starting address, or role reference can be carried over. Check the selection and, if there are unexplained restrictions, start fresh without this template.

Save as template: Open the action, enter a name (field limit 100 characters; the placeholder may be Name your template) and save. The request requires template edit rights or the corresponding Self-Service edit right; a visible button is not enough. A successful save stores the filter body and then runs the Apply path. If the subsequent hit calculation fails, that does not necessarily mean the template was not saved: first reload it and check. If the name already exists, a prompt to overwrite appears. Do not overwrite blindly here: the checked overwrite path does not reliably restrict same-named templates to your own customer. Decline the prompt, use a new unique name, and involve administration if a correction is needed. The x next to the name only ends name entry; it does not delete a saved template.

Save as customer employee list: With Manage Employee Lists, this additional action is also available directly in the filter. The fact that the people overview has its own list button does not hide the action in the filter. Enter a name with at least two characters (field limit 50; possible placeholder Name your list) and choose the save action with the same name. What is saved is the currently server-determined set of members taking the filter selection into account, not a rule that grows later. The free person search and separate deselections in the overview are not part of this filter-dialog save path. Saving additionally requires the Self-Service edit right explained above. After success, reopen My lists and check the new list; the filter dialog remains open. If the name is missing/too short, the entry remains. If rejected or if the response is unclear, first check the list inventory, do not save repeatedly. Agency list and blacklist are not available to customer users here.

Hit email and troubleshooting

The envelope in the filter sidebar opens Subject and Description. This is the separate sending path described under Email directly from the filter hit list: Send email requests sending immediately to the people selected in the filter, without a second confirmation and regardless of a side-only name search. No attachments, SMS, or message templates; the x closes without sending. The dialog closes immediately after the click, without confirming success or delivery. If the response is unclear, do not send again. For a more controllable process, first check the people overview with its selection and use the message dialog described above.

If no hits appear, first let it load, then check customer lists, date limits, repeated criteria, and both selection states. If lists, document types, or templates are missing, their loading may also have failed. Filter calculation and template search do not reliably end a loading indicator in every case when there is a network error. If loading persists, reopen the view; do not use any save or send action as a repair. If a request is rejected, have the specific access or save permission checked. A hit is neither a shift confirmation nor proof of valid documents.

Table options in Employees and My lists

Both tables start with 20 rows per page and first name ascending. A separate selector for page size is not embedded here; page changes and sortable headings reload server-side. The entries/pages shown are not the full filter selection. The specific columns and the differing header-checkbox behavior are explained above under Search, sort, and check selection of people. In these two tables there is no column configurator, no directly editable cells, rating stars, or time approvals. The additional Excel field checkboxes change only the export, not the table columns.

The image and normal data cells lead to the Self-Service profile; a row itself does not trigger a bulk action. The people overview has no row actions. My lists shows the remove button; the limitation described above remains unchanged: the active button passes the wrong event format and does not trigger removal. Even without a selected list, it is not a pool-delete action. Do not click repeatedly; use the controlled profile path described earlier. Profile editing and assignment/time approvals are separate processes, not table functions enabled here.

People profile in Self Service: display and independent actions

Open a person from Employees or My lists. First check the name at the top: both entry points lead to the people profile, not to the customer master data profile. The header shows, among other things, place of residence, age, email, and mobile number. A missing or rejected view is not an empty profile; do not try any changes as a repair. To check again, return to the people overview and reopen the person there. Simply changing the address in the browser does not replace this entry point.

Distinguish display, editing, and saving

The profile is not completely nonfunctional or read-only. The normal customer-pool read view locks many master data fields; additionally assigned profile rights may differ from this. Customer lists under Customer Pool remain a separate, directly saving process as described above under People profile: customer lists and automatic save actions. Reset password is also a separate action. A greyed-out field proves neither lack of keyboard operation nor lack of server rights. If a supposedly locked field nevertheless accepts changes, do not keep editing; instead, ask administration for clarification.

Under person details, first name, last name, nickname, gender, number of children, smoking status, as well as date of birth and age can be read. First/last name and nickname have a 24-character limit in the form; first/last name are required fields with at least two characters. If profile editing is not available, the name and number-of-children fields are in fact read-only; the smoking switches are locked for customer users. Age is a displayed value, not a separately stored input value. A required-field marker is not an invitation for customers to add other people's personal details. Coordinate corrections to such master data with the responsible administration.

No general cancel promise: For fields whose editing is explicitly enabled, leaving a field can mark changes for saving. The normal profile saves such staged data on a timer; Enter is not a separate save button for the name fields. Individual actions have different save paths. Leaving the profile is also not a reliable way to discard staged changes. An error message can trigger an automatic page reload; after that, check the actually saved state instead of blindly repeating the entry.

The agency areas internal remarks, employee lists, imported job history, the additional image section, work information, withholding tax, bank details, and job interests are not shown in this customer view. A data value existing in the background or a similarly named field does not make them customer functions. In particular, there is no reachable customer remarks editor in the hidden agency area here. Hiding it is not a data security guarantee: use personal, contact, health, or family information only for the authorized purpose and do not copy it unnecessarily into messages, screenshots, or exports.

Read ratings correctly

In the ratings tab, the stars are a display, not an input. The customer rating is determined for your customer and this person, not only for your own portal user. The number in parentheses counts the underlying rating entries, not all assignments ever completed. If there are no such entries, the value is 0. In the event of a loading error, the initial value 0 may also remain: do not infer a poor rating from that. employee rating by agency appears in the tab only with View Agency Rating; this display condition is not a promise that the value does not appear elsewhere in the profile. There is no customer selector here to switch to other customers' ratings.

Temporary password as a separate profile action

The Reset password button in the profile header appears with the Reset Employee Password right, even if the master data is read-only. After loading, it opens its own Reset Employee Password dialog. A temporary password already stored there may be visible: do not copy it into support messages or screenshots.

  1. Check the person in the profile header and open the button.
  2. Under temporary password, enter at least eight characters with upper- and lower-case letters, a digit, and a special character. The error message does not fully name the special character; the input check still requires it.
  3. Save requests the change immediately, without a second confirmation prompt. Cancel or the x closes without this save request. Simply typing it in does not save here via the profile timer.
  4. Wait for Temporary password saved. or the translated success message. If the dialog remains open or a rejection appears, do not save repeatedly; administration should check access and the person reference.

This process stores a temporary password. It is neither an invitation nor an email send, and it does not confirm a successful login. A visible button alone does not guarantee that the server allows the specific process.

Notification dialog in the customer people profile

Send notification in the profile header is not the same dialog as sending a message from the people list. It can be opened for customer users, but Subject and message are read-only in this customer view. The displayed Send button does not lift this lock. Empty fields therefore cannot be filled in here to create a new customer message. The x closes the dialog; instead, use the separate message dialog from the people overview described above and check the recipient selection there.

In the profile dialog there is no active email/SMS selection, no attachments, and no message templates. The stored path is a notification for exactly the open person. Send is an immediate request without a second confirmation, not a proven delivery. Even a green response here is not a reliable proof of sending: a server-reported sending failure is not always recognized as an error. If the result is unclear, do not send again. A permanently visible loading indicator also does not prove that sending is ongoing or successful.

Read personal details, appearance, and contact information safely

Personal details shows, besides the names, gender, number of children, smoking status, birthday, and age. The status is visible only with the corresponding display right; changing the status has its own right and is requested immediately, not only with the usual profile save. The three birthday selections belong together. The age is calculated from them; it is not a freely entered field.

Under Appearance, you will find eye and hair color, body height, shoe and clothing sizes, as well as visible tattoos and piercings. The size aids are reference tables, not changes to stored data. The descriptions for tattoos and piercings are read-only in the customer portal; the associated switches are also locked. For the selection fields, the additional input lock depends on the profile edit right. Do not add personal features based on an assumption.

Under Address and Contact information, the main and secondary address as well as the residence indicator are separate. These include street, house number, address supplement, postal code, city, country, and, in Switzerland, the canton and the validity date. Landline, mobile number, recovery email, and emergency contact are different details from the login email. The prefixes are locked for customers; the text fields are read-only if there is no profile edit right. Have an incorrect emergency number or login address corrected by the responsible administration, not by changing a similarly named field.

If profile editing is explicitly allowed: address changes can reset the validity date. An address selection can change multiple address components at once. Manual entries are not confirmation of correct map coordinates; when saving, the server may recalculate the coordinates. Phone details are combined with their prefix and may be subject to duplicate checking. If rejected, check the actual state after reopening.

Saving affects more than the last field touched. Normal automatic saving transfers the entire current profile object. Changes are usually staged when leaving a field or making a selection and checked every two seconds; during an ongoing save and in a restricted profile, the timer is not triggered again. This is no guarantee that every entry is saved within two seconds. A new entry during an ongoing request can lose its staging because of the older response. Leaving can also request a save. Therefore, do not use navigating away or closing as an undo function. In case of errors or an unclear state, reopen and check; do not make repeated blind changes.

The additional password dialog belongs to changing the login email, not to Reset password. It opens only when a actually different email has been entered and the field is then left. In the customer view, its password entry is read-only. It is therefore not a usable customer path for changing the login; do not share access data or include it in support images.

Competencies, profile media, and separate save paths

Under Competencies you will find CV, Education, Professional experience, and Languages. Education includes type, educational institution, from/to, and ongoing education. Professional experience separates profession, Level, company, from/to, and current position. In languages, the designation and level are separate; for a native language, no language certificate uploader is shown. Selecting an ongoing entry locks its to-date. Open existing supporting documents only for the authorized purpose via Show CV or Show certificate.

These records are not simply additional text fields of normal profile saving. If editing is actually enabled, complete education, experience, and language details request their own saving when the field changes or when a selection is made. Incomplete new entries are not saved in this process. For languages, the profile may additionally be staged as changed. Add entry first creates a row; the customer mode blocks this creation in the handler even if a button appears because of additional rights.

Deletion is not discarding: Removing an education, experience, or language row asks for confirmation. Only Yes requests the deletion; a row not yet saved is only removed locally. A confirmed deletion cannot be undone by closing the profile. The greyed-out row buttons are not a reliable technical lock. In the customer portal, do not click such operational changes to test them; report permission deviations to administration. The right to view the profile alone does not confirm write permission for the respective endpoint.

Profile picture, short video, CV, and certificates have their own upload paths. A successful direct upload replaces the document immediately, independent of the profile timer; a subsequent profile change or leaving does not undo it. The greyed-out upload areas in the profile body are not to be used as a customer upload workflow. Existing file and image links may still intentionally remain usable. For the profile picture, the upload area lies outside this general greyed-out state and is separately limited by the profile edit right. Enlarge only opens the image view; clicking outside the image closes it.

Take photo can open a camera dialog even though saving the photo is blocked in customer mode. Simply opening it may request camera permission. For pure profile viewing, do not grant camera permission or create a photo; close the dialog. File deletion icons in the profile body are hidden and the associated file deletion handlers are additionally locked. This is different from the deletion of entire competency rows described above.

A feedback message about profile completeness can appear after a save or upload response. Start closes this notice; it does not itself trigger a new application or an invitation. A completeness note does not replace checking the saved profile.

Mobility information and technical input limits

Mobility information distinguishes subscriptions for public transport, driver’s license types, driving experience, car availability, and car sharing. For the regional transport network, a name can be entered; when a car is available, vehicle selections such as body type and size appear. Driver’s license documents and driving experience appear depending on the stored license categories. The absence of a document area therefore does not prove that no driving authorization exists.

The mobility switches are in fact locked for customers. The additional vehicle selections are not protected by the same input lock, even if they look greyed out. Do not treat such fields as approved customer editing. If a selection was changed by mistake, do not edit further fields or rely on discarding when closing: the change may have been staged for the general profile save. Administration should check the saved state.

The file areas for the front and back of the driver’s license also have separate upload rules. Showing existing files must be distinguished from replacing and deleting. In the customer view, do not try an upload or camera function to correct them. Driver’s license documents contain identity data; view them only with authorization and do not copy them into support messages or sample files.

Read availability, do not manage it from the customer view

Under Unavailability period, the table shows existing entries. In the customer profile, the add, edit, and delete actions are not shown. The date dialogs, approvals, and rejections available in other profile views cannot be inferred from this as customer functions. The separate dialogs for permanent employee groups and time management also have no active opener here.

The weekly availability is separate from these dated absences. The switches for evenings, weekends, and day and hour selection are locked in customer mode; the selection labels are additionally intercepted in the handler. The grid editing, in turn, depends on the profile edit permission. Anyone who sees a grid area that is unexpectedly operable should not change it, but should inform administration: the grid path has its own immediate save and is not a non-binding draft of the profile timer.

Any change to an absence belongs in the employee or administration workflow approved for that purpose. Do not try to reproduce it through client lists, mobility details, or a similarly named dialog.

Further documents: read permission and edit limitations

Further documents appears in the customer profile only with View Further Documents. A document with a stored file can be opened in a new window via its row. If the file path is missing, clicking the row does not request a file. Document type names may be translated in an organization-specific way; do not derive a standardized list of required documents from this.

The add bar is not shown for clients. The associated dialog is therefore not an accessible client creation path. If profile edit permission is additionally granted, edit and delete buttons can appear. Saving and updating further documents remain blocked in client mode in the handler. Deleting an existing document record is separate from this: a delete button visible with additional rights can trigger a separate delete request after confirmation; this confirmation/delete path does not have the same client guard. Therefore do not rely on guaranteed deletion protection, do not try the action, and contact the responsible administration. This is not a promise that deletion will succeed. In the possibly opened edit dialog, the document type remains locked; closing or canceling discards the new file only staged there, but does not replace any file already saved earlier.

Do not assume an upload succeeded just because a file name is displayed. The general create/replace path for these documents uploads only upon explicit saving and then stores the record separately. For clients, this path is canceled before upload. Open existing documents only for their intended purpose; in particular, do not pass on identity, authorization, or health documents as examples. The read permission for this area is neither a general profile write permission nor a statement about all server-side data delivered.

Do not consider is a consequential single action

For certain applicant statuses, Do not consider may appear under the profile. Even if the button is greyed out, that is not the same as a real input lock. It is not a harmless way to merely clean up your own customer list. For purely list maintenance, continue to use Customer Pool or the list editing from the people overview.

The Do not consider this employee dialog contains a prepared subject and message text. These texts are read-only for customers; however, that does not automatically make Send ineffective, because the texts are already filled in. When opening, it checks whether assigned or confirmed assignments exist from today onward. Such assignments block the process. A failed precheck is not proof that no assignments exist.

Cancel or the x closes the dialog without this single action. Send opens an additional confirmation prompt. Only Yes requests the process. With sufficient server-side Change Employee Status permission and a matching agency-person relation, it can remove the person from the agency pool and request a notification. This is neither merely an unsubscribe from your client list nor a complete deletion of all person data. The interface warns that the action cannot be undone.

The actual request checks upcoming assignments again. A success message is still not proof of delivery of the notification; the removal process can continue independently of whether it was sent. If the result is unclear, do not send it again. As a client, coordinate the desired non-consideration with the responsible administration instead of trying a greyed-out button.

Self-Service Live View: find assignments and open time check

  1. Open Self Service → Live View. Make sure you are in the correct customer account. Self Service to the right of the search field takes you back to the self-service project overview, not to orders. Access to the self-service area and opening a time check are authorized separately; a visible assignment does not yet grant any editing or validation rights.
  2. The list shows assigned assignments from Self-Service projects for today and tomorrow according to the server date. It is neither the complete project archive nor an overview of all open staffing requirements. For client users, their own client is used; for agency users, the agency area is used. Do not understand the list as a guarantee that only your personally managed projects are displayed.
  3. Enter part of the last name, project name, role name, or location name under Search person, project, location. Each keystroke re-requests the matches from the server and starts again at page 1; there is no separate apply button. The visible first name is not searched. Clear the search field for the unfiltered list. For names with special characters or unexpected results, search with a simple name fragment and check the row.
  4. Compare Date, From, To, Project, Role, Location, First Name, and Last Name. The time columns are the planned shift times, not confirmed actual hours. Use the page navigation to switch between multiple pages. The view is initially set to 15 rows; counters and visible rows are not proof of completeness.
  5. The sortable column headers trigger a new server query. This sorting is not reliably protected: if there is no reaction or an error, reopen the view and narrow it via search instead of assuming a correct new order. The default order is by date, start, project, and last name.

Note the refresh: the page reloads when opened and then roughly every 20 seconds. Even after a page change, this automatic refresh queries page 1 again; the page number and the displayed data can therefore diverge. Older responses can also overwrite newer search results. Always compare person, date, and project again before clicking a row. An unchanged display or Nothing Found proves neither that the refresh has completed nor that all assignments are absent. If there are unexpected entries, loading problems, or missing assignments, contact administration with project, date, and name; do not trigger changes by repeatedly clicking.

Read status and location warning correctly

DisplayMeaning and limit
StatusThe color uses the stored clock-in status and the local browser time. Green means there is a clock-in status, not necessarily currently clocked in, fully recorded, or validated. Gray/red refer to the planned start when no status exists; the display is not a reliable minute-accurate proof of lateness. Check the tooltip and detail view.
WarningThe warning triangle with a distance in meters or kilometers concerns the stored location deviation when clocking in. It is not live location tracking and not a general check of all break, time, or expense errors. A dash without a warning is not proof of correct attendance: geodata, assignment location, or alarm configuration may be missing.
ImageProfile picture for orientation; still compare name, date, and project. An image confirms neither identity nor presence.

For Self-Service assignments, the client value applies to the location warning; otherwise the agency value applies if the client value is not set. An existing saved distance is not constantly recalculated here. Loading alone can recalculate and store missing location distances and alarm flags. Therefore the display is not a guaranteed side-effect-free test. It does not, however, save any time approval or send any invitation. Clarify alarm thresholds in the settings with the responsible administration; do not infer them from a missing triangle.

Check an assignment without approving it yet

Click the appropriate table row. As a client user, it opens the client time check; as an agency user, the agency time check. The return path to the Self-Service Live View is included. The destination view has its own access and detail rights; a rejection or navigating back is not proof that the assignment has been deleted. Have the permission for exactly this assignment checked instead of using a different identifier or someone else’s link.

Clicking a row is navigation, not saving, clocking, confirming, validating, payroll export, or sending. This Live View does not include its own add, edit, delete, export, or bulk approval actions. Only the separate time check view can offer further authorized actions. Check person and assignment again there before changing anything; this guide does not pre-empt its save, expense, or approval workflows. Switching back to the list does not undo changes already saved elsewhere.

Self-Service project overview: find the right project

Open Self Service and then the project overview. Client users see their own client area; agency users can see Self-Service projects from their agency across multiple clients. This list is not the order overview. A visible menu item or project link does not mean you are also allowed to edit, publish, or bill the project.

For client users, the results also depend on the Self-Service visibility rights, responsibility as Client Buyer, and the allowed departments. Without permission for all Self-Service projects, the view is restricted to your own buyer assignment; projects without a buyer assignment remain hidden in the client portal. Projects without a department require the corresponding visibility permission. Other existing project visibility rights can also restrict access. A filter on project management does not grant any additional rights.

Select exactly one tab: Open Projects, Ongoing Projects, Past Projects, Draft Projects, Archived Projects, or Canceled Projects. Switching reloads the list from the beginning. There is no multiple tab selection here and no split into individual date rows as in other project overviews. Order drafts and submitted orders are not separate tabs in this view.

Open Projects can also contain projects with pending follow-up assignment requests. Therefore, a match there is not automatically a purely future or unstaffed project. The number on the tab and the visible rows can differ: search text is not passed to the separate tab count, other tab counts are not all recalculated while typing, and local automatic drafts are additionally shown. The note about pending follow-up assignment requests on the tab is also not a reliable proof for the visible Self-Service list; check the specific project. A sum of the tabs is not a number of distinct projects.

If a project is missing: first check the client account, tab, and filters. Then ask administration to check the buyer assignment, department, and visibility rights exactly for this project. State the project name and period; an empty result is not proof of deletion.

Apply search, project type, project manager, and period

  1. Enter part of a name in Search by project, location. In the agency view, the field is Search by project, client, location. The search queries the server again with each keystroke and starts again at the beginning of the list. It searches the project name, stored client name, and location name, not the description or project number in general. In the client portal too, the client name remains part of the search, even though the placeholder does not mention it. For special characters and unexpected hits, check again with a simple name fragment.
  2. Under Project type, select the desired project type and under Project manager one or more contact persons. Here, project manager refers to the client contact for the project, not the agency project manager and not the Client Buyer. In the agency view, prefixed client names help when contacts and project types have the same name. A selection within the same field allows multiple values; the different filters narrow the result together. The collective display selected people can also appear for project types and is then only the label for the multi-selection.
  3. Enter From and To in the format dd.mm.yyyy. Both date limits are required for the period to narrow the results. Projects with at least one stored assignment date in the selected period are searched, not only projects whose start and end both lie fully within it. Do not enter From later than To; there is no guaranteed correction for swapped dates here.
  4. Click Filter. The selection and date are only staged beforehand. CLOSE in a selection list only collapses it; it does not apply the filter and does not discard the selection. After filtering, check the fully loaded list: first a preliminary query is triggered, then the actual list is loaded again. Project types are only fully included in the subsequent list query. If the preliminary query fails, the refresh may not occur.
  5. To reset, click the x next to Filter (tooltip Delete). This clears both date fields as well as the project type and project manager selection and applies these empty filters. The search text and the selected tab remain unchanged. To also clear the search, empty the search field; if the refresh does not occur, press a key and wait for loading to complete. The x does not delete a project.

Filters and search are not project changes. The applied filters are remembered in the local browser; they are not a server-stored personal filter for all devices. When reopening, old values can reappear from the same browser storage, even from a different project overview. Tabs and date values in the link can partially override these defaults; not all selection values are restored from the link. A copied link therefore does not guarantee the same results on another device. Search text is applied immediately while typing, but is only stored later with actions such as filtering or changing tabs. Staged, not-yet-applied selections are separate from this.

If the display is not correct: first check the visible selection, search text, and tab. Do not filter repeatedly in quick succession: the list query cancels its previous request, but the additional filter and count queries are not jointly protected. Delayed responses can affect counters or intermediate data. If loading fails, reopen the view, check the restored filters, and tell administration the last action and the desired period.

Read the table, sort it, and open a project

The table shows, among other things, Start Date, End Date, Name & Description, Location, Status, No. of Shifts, Invitations, Applications, and Days. The Client column is hidden for client users. For multiple locations, the location cell shows Multiple locations; the tooltip contains the names. Invitation and application counts as well as status bars are overviews, not proof of delivery and not time or payroll approval.

Scroll down to load more projects. There are no page buttons in this overview. Also scroll horizontally if there are many columns. Local automatic drafts can influence the displayed row counter; a list that stays still is therefore not definite proof that all server projects were loaded.

Click a column header with a sort icon to sort; clicking again can reverse the direction. Sorting reloads the list and starts from the beginning. Initially it is sorted by start date ascending, and by Past Projects descending. Location and the status bar do not have their own sort button. After searching, filtering, or changing tabs, check the order again: these actions can query again by start date even though another column was previously selected. If the order matters, choose the desired sorting again and check the results.

To open, click Name & Description, a date, or a linked count. These links lead to the Self-Service project information; they do not save or send anything. The empty area of a table row has no separate open action here. The status bar and the bell for pending follow-up assignment requests are separate links to staffing assignment, however. They currently use the general project path rather than the same Self-Service information path. If access is missing or the destination view is unexpected, return to the overview and open the project by its name; do not try any other identifier. The bell appears only in the Open Projects tab and only when the row contains the corresponding note.

Live View above the list on the right opens the separate overview for assignment and time checks, not the selected project. Opening a project, the assignment, or the Live View is not yet saving, inviting, publishing, or validating. Check the project and permission again in the destination view. The complete editing, planning, publishing, and assignment workflows are separate from these entry points.

Change flags and archive projects

Warning: The following table fields save immediately. There is no shared Save button and no additional confirmation for them. Only change them if you have the business instruction and authorization to do so; visible operability alone does not confirm write access.

Field or actionWhat you request with itWhat is not proven by it
Wages paidSets or removes the corresponding project flag.No payroll run, no payment, and no payroll export.
invoicedSets or removes the invoicing flag on the project.No invoice is created or sent.
Auto‑invite upon activationSaves whether the project can be considered for later automatic invitation when an employee is activated.The click itself does not send an immediate invitation. Later processing has its own prerequisites, such as open future staffing requirements and matching filters; there is no guarantee of delivery.
Archive project (archive icon)Sets the archive flag for the saved project row you clicked and reloads the list. The icon is based on the row’s status as a past project, not only on the selected tab.No deletion, cancellation, revocation of invitations, or automatic cancellation of assignments.

A changed checkbox or switch already appears locally before the save is confirmed. If errors occur, the visible value here is not automatically and reliably reset. Back or switching tabs does not undo a value that has already been saved. After loading is complete, check by reopening the overview whether the value persists. If there is an error message, no response, or rapid successive changes, do not toggle repeatedly: competing requests can arrive in a different order. Tell administration the project, field, and desired final state.

When archiving, note in particular: There is no yes/no dialog here. The current tab logic can continue to show a past project under Past Projects even though the archive flag is set, and exclude it from Archived Projects. So clicking does not guarantee a visible tab change. Do not archive again just because the row remains visible; have the saved state checked. There is no restore action integrated into this table.

Do not use these server-side flags on rows that are marked only as an automatically saved local draft. Those rows still lack the saved project ID; a visible switch can nevertheless trigger a failed request. For such rows, use the separate process Discard this project instead.

Discard the automatic local draft

Under Open Projects, self-service drafts saved automatically in the same browser can appear in addition to saved projects. They are identified by the note This project was saved automatically and the trash can Discard this project. This is not the same as the Draft Projects tab with saved project drafts. Unlike the server list, the local entries are not restricted by all search and date filters; date values can be placeholders. Check names and context carefully, especially after changing account or customer in the same browser. A local save is not a promise of permanent or cross-device storage.

  1. Check the marked draft row and click its trash can Discard this project.
  2. As long as you do not confirm, the draft remains. No discards nothing.
  3. Yes removes this automatic draft immediately from the local browser storage and the visible list. No deletion request is sent for a saved server project. There is no subsequent save here and no built-in undo action.

Another browser window already open may still show an older state. After an error or conflicting displays, first check the current state instead of deleting repeatedly. For a saved project without this local draft notice, this overview does not provide a normal delete or copy button. Archiving is the separate process above; it does not replace project deletion.

New project and template: getting started without premature saving

If the creation right is available, you will find Add new project and Load from template at the top. If these entry points are missing, have the right to create self-service projects checked; list view and edit permission do not automatically suffice for this. The rights check can also fail, in which case the buttons remain hidden. Opening a template dialog through another menu entry is also not proof of a creation right.

Add new project opens the self-service project information for creation. Clicking the link alone does not yet create a saved or published project.

For a template:

  1. Click Load from template. The template name dialog offers the loaded project templates. Customer users get their customer’s templates; for authorized agency users, templates from multiple customers may appear with the customer name prefixed.
  2. Search in the dialog for the template name. This search filters the already loaded options locally and is not case-sensitive. It does not search all template contents and does not create a new server request. Clear the search field if an expected entry is missing. An empty list can also mean that the templates have not yet been loaded; if the problem persists, have the customer context and template availability checked.
  3. Click the appropriate list entry. This opens the self-service creation with that template and closes the dialog. Missing or unreadable template content can prevent the switch; in that case do not select it repeatedly, but report the template name and customer context.
  4. If you do not want to use a template after all, close the dialog using the x at the top. This is neither deletion nor saving. After reopening, check the search; the display may still reflect the previous local selection.

The selection is navigation, not a finished copy and not publication. In the opened form, first check customer, name, dates, and the transferred details. Which values are transferred, how the creation is saved, and which steps require planning, publication, or staffing assignment are separate processes. In particular, this template access is not a complete guide to editing or saving templates. Chat and report buttons are currently not actively integrated into this project table; an existing project link does not replace those functions.

Open project master data in customer self-service

This section applies to customer users in Self Service, not to order creation and not to the normal agency project. It covers the first part of the master data and the save limits. Location search, map, calendar, and recurrence pattern as well as the subsequent role, shift, and staffing planning are separate processes; the mandatory prerequisites named below do not replace those instructions.

  1. Open Self Service → Project overview → Add new project. For changes, open an existing project there via its name.
  2. Wait until the data has loaded. If you are using a template or a local draft, check the transferred values instead of assuming an empty form. A delayed loading response can overwrite entries you have already made.
  3. For a customer user, your own customer is preset. There is no customer picker here and no reachable dialog for creating or editing a customer. Client Buyer, parent project, the agency project manager, HR Manager, and the separate customer contact picker are also not part of this customer form. Instead, the customer contact is selected as Project Manager.

In a truly empty new creation, name, description, project type, project lead, numbers, cost center, and department are initially empty; locations and assignment days have also not yet been created. The customer is taken from your user context. Loaded templates and local drafts can replace these starting values.

Creation and editing have separate self-service rights. A visible entry point and a loaded form guarantee neither saving nor the creation of new master data. Administration may need to check creation rights and edit rights separately for your own projects and for all self-service projects. For customer users, buyer assignment is decisive for their own projects; department and visibility rights remain additionally relevant. When a customer user creates a new project, their buyer assignment is set during server-side saving. Project manager and buyer are not the same person assignment.

An agency user can open the same self-service view with different fields: in particular, the customer is not generally hidden there. Therefore do not transfer either that customer creation or the agency rule “Project Manager or HR Manager” to your customer process. If the customer context is missing or there is an error message, do not use a different customer ID; instead have the account and permission checked.

Enter project name and description

Select the language tab German or the desired other language. In project name, enter a name in at least one of the four languages German, English, French, or Italian; a maximum of 100 characters is provided per name field. Not all four names are mandatory. The visible project title may still show the previous status until the next save step.

Project description is optional. The text editor limits the entered text to 500 characters; if this is exceeded, the edit path reverts to the last accepted content for this language, possibly to empty. Therefore shorten long texts before pasting and then check the visible content. Changing languages is not a translation. The separate translation action and detailed link editing are not part of this section.

Check multilingual values after saving: For the main name and main description, the save process first takes the language with an existing name in the order German, English, French, Italian. For customer users, the server also writes these main values into the language stored in the user account. This can differ from the tab you currently have open. As a result, an earlier different translation there may be replaced. After saving, check all required language tabs again; do not assume that every language version remains unchanged.

When leaving the name or description field in a new project not yet created on the server, a local save is attempted. This is not the saving of an existing server project. The general save limits below also apply here.

Choose or add project type and customer project manager

Select a project type and a project manager. Both are mandatory. For existing entries, click the matching result and then click another field; Enter and Tab are not consistently pure selection keys here. In customer self-service, the project manager is a contact person of your customer, not an agency contact. Without customer context, these two selection lists cannot be selected normally. Selecting an existing entry first changes the assignment in the form; for a new item, the local draft save is triggered.

New project type: First search for an existing entry. If a genuinely new type is needed, type the full name again, check that no existing entry matches, and press Tab once. Enter is also bound as a creation trigger, but when a result is marked it can conflict with the selection; do not use it to confirm existing types. Warning: this requests creation of the type immediately, without a separate type dialog and without waiting for any later continuation. An exactly matching name in the loaded list is not created again; the server additionally checks whether the name is already in use in the respective customer or agency area. If successful, the new type is selected. If there is an error or no response, first check the list and permission, and do not press Enter repeatedly. The right to create a project does not automatically include creating a new type.

New project lead via contact details:

  1. Only for a truly new contact: Type the name again in the Project Manager field and press Tab once. The CONTACT DETAILS dialog opens. Enter is also a dialog trigger, even if an existing result is selected at the same time. An unexpectedly opened dialog is not an instruction to save the existing contact again. If there are exactly two words separated by a space, the entered name is automatically split into first and last name; check the split and all prefilled fields.
  2. Fill in First Name, Last Name, and email. Both names have a maximum of 24 characters. The email must match the form format; this does not check whether the address can actually be reached. Mobile no. is optional and limited to 16 characters.
  3. Click Save once and wait. The contact is saved independently under the customer, then added to the list and selected as project manager. The project itself is not created yet. In this process, creating the contact does not send a user invitation and does not grant the contact person portal access.
  4. Cancel or the close icon before submitting closes the dialog and discards its input. After submission has already been sent, closing is not a cancellation of the ongoing request; a late response can still create and select the contact. A later back action from the project does not delete this contact.

If there is an error, the contact creation remains unconfirmed. Before trying again, check whether the contact already exists. The Save button shows a loading state, but here it does not reliably prevent a second click. Edit rights for your own self-service projects alone may be insufficient for this separate contact creation; administration should check the specific process. You do not edit an already selected contact here via the hidden agency customer contact picker.

Assign numbers, cost center, and department correctly

Project no. and Order number are optional internal details with up to 99 characters each. The project number can be checked against existing numbers. In the notice about an existing project number, No means: clear the number in the form. Yes keeps it; the close icon only closes the notice. None of these actions saves the entire project. The check runs asynchronously and does not reliably hold further actions until its response. Therefore do not rely on guaranteed uniqueness or on the notice preventing every duplicate creation.

Cost center: Type a value or select a suggestion. The suggestions are filtered by your text. Closing the list does not save an existing server project. If Multiple cost centers in use. is shown, the shared input field is replaced by this notice; check the differing values in role planning. During later overall saving, roles without a cost center can be carried along; if all existing non-empty role values correspond to the old project cost center, they can also switch to the new project value. This is not merely a display label.

Department: Select one of the departments loaded for your customer user. The normal list is based on your department assignments; an empty list can also result from a loading error. An offered entry no department if present is not the same as a normal department and is not reliably treated as an empty assignment in the immediate change path. If such an error message appears, involve administration. When multiple departments in use is shown, the shared picker is replaced by the notice; the roles must be checked separately.

  • New, not yet saved projects: The department selection initially belongs to the form or local draft.
  • Already saved projects: Selecting or clearing the picker sends a separate change request immediately, without Continue and without additional confirmation. In doing so, roles with the previous non-empty project department can also be changed. This is separate from overall saving, which can additionally take over roles without a department. Other deliberately deviating role departments are not automatically treated as identical.
  • New department: Only if an additional department is truly needed, enter the full name again and press Enter once. Enter requests a customer department immediately, even if a result is already marked; therefore do not use it to select an existing department. This is neither an informal search nor a separate confirmation dialog. Afterwards, the new department is selected and, for existing projects, its change is also requested. The new creation can additionally extend the department assignments of customer users who were previously assigned to all existing departments; so it affects more than this project. The selection list returned after this creation can contain more departments than before; this does not automatically create additional edit rights.

Self-service edit rights alone do not guarantee that the separate department change will be accepted: this path uses a different rights check. If there is an error, the local value may still appear changed. Do not toggle repeatedly and quickly; responses and write requests here are not jointly protected against overtaking. After completion, check the saved project and role state by reopening it. Back is not an undo for these immediate changes either.

Distinguish Continue, local save, and Back

Before Continue, check at least one valid project name, project type, the specified customer, and the customer project manager. In addition, at least one location must exist and every added location must have assignment days. For a project with a date range instead of individual days, both range boundaries must be present. If employee cancellations are enabled, the basic-data check requires a deadline of at least two days. Empty location rows can prevent Continue, even if another location is complete.

Templates and drafts: When using a project template, among other things the name, contact, type, cost center, and department are copied; the normal assignment-day lists are cleared. Select the required days again and check all transferred values. A locally reopened draft, on the other hand, is not a fresh template. The full template transfer as well as location, calendar, and recurrence handling are not declared complete here.

ActionStorage limit
Leave a field or change a selectionAutoSave only saves a new item that has not yet been created on the server, and only in the same browser, provided no submit is currently running. Not every field has its own such trigger. An existing project is not saved on the server through this general AutoSave path.
ContinueValidates the form and submits the entire project state. After reported success, the matching local draft is removed and step 2, the Self Service project planning, is opened. This is not a publication, invitation, or confirmed staffing assignment.
BackTakes you to the project overview, not to a discard confirmation. When leaving, a local save of the new item may still be initiated. Changes to an existing project are not generally saved this way; already separately saved master data or departments are not rolled back either.
Step number 2, 3, or 4 for a saved projectThe transition is started before the subsequent save attempt. A follow-up page that opens on this path therefore does not prove a successful save. Step 3 additionally depends on the edit flag. Use Continue for a controlled finish and check its result.

For a customer user in Self Service, the agency warning that another customer can no longer be selected later does not apply. If newly added past days are included, a separate yes/no prompt follows instead: No ends this save attempt, Yes continues it. Past days that were already saved when loading alone do not trigger this second warning. Rejecting it does not delete any contacts, types, or departments created independently beforehand.

No shared undo boundary: A local draft is neither a server-side project nor a permanent or cross-device backup. It may still exist after switching accounts in the same browser; check the context. The individual master-data requests, department change, and the overall save do not form a guaranteed atomic operation. During the overall save, project/role changes may already have happened before a later step fails. An error message therefore does not prove that nothing was saved.

If a save error occurs, first stay on the error message and check the current state in the overview before creating the item again. Tell administration the project name, customer account, action, and error message. If edit permission is missing, Continue can only lead to planning without saving. Simultaneous editing in multiple windows as well as late loading or write responses can lead to outdated values; a dirty warning or automatic conflict resolution is not guaranteed here.

Treat the image and subsequent settings separately

An image upload is not proof that the project has already been saved. If your account is allowed to perform the upload, an unsaved item is first given a file with a temporary record; only the later project save path transfers the image reference. For an existing project, a successful upload can change the image reference immediately. This upload check is not the same as the Self Service creation permission. A preview image or a visual lock alone does not confirm successful saving or a complete access lock.

The exact upload/delete controls, visibility switches, automatic invite/booking/cancellation functions, time-tracking managers including the invitation dialog, project deletion, and cancellation are not part of this limited basic-data guide. Likewise, location/map/calendar and the subsequent roles, wages, expenses, and criteria remain separate steps. Do not use their visible actions as a substitute for Continue or for merely cancelling. A button on a subsequent page means neither that the basic data is saved nor that an order was published or a message delivered.

Select locations in the project basic data

As a customer user, open Self Service → Project overview → Add new project or an existing project via its name. The following steps supplement the basic-data guide above; they are not instructions for creating an order. Wait for the project data to load. A template can bring locations with it, even though its normal assignment days were cleared.

  1. Search in the location field for the saved name, a Google place name, or coordinates. If the list is empty, Select location opens the selection. Pressing Enter on an empty field does not create anything.
  2. Select an existing database match. It is added to the form, not created again as a master record. The newly added location is marked for calendar editing, and the previously marked locations are deselected. An identical name already present in the form is not added again.
  3. Check the address beneath the name; No address is not a geocoding confirmation. The name field in the project row is read-only. Expanding shows the individual days, and the number beside it counts the days in that row.
  4. Repeat the selection for additional locations. Tick exactly the locations on the left whose days you want to edit together. Opening a row alone does not change this selection; clicking its map pin, however, can additionally select the location.

Search and map load asynchronously. An older search result may arrive after a newer input; compare the selected name and address before continuing. A missing map or missing results do not prove that there is no location. A location added without days can later block Continue. Selecting an existing location is not yet a server-side save of the project assignment.

Create a new location — do not rename an existing one

Create a free name: Type a new name into the location field and press Enter. If Enter has just selected a marked result, that result is applied first; the goal is not to open a second dialog at the same time. The location dialog shows Database name as a required field and a read-only second field with the Google place name. No German translation is stored for its key, so no fixed German label is assumed here. An empty Google entry is not a required-field error.

Google result: A location that has not yet been saved is usually shown on the map first. Check the point and click Create location in the map window. Only then does the name dialog open. If the map view is not yet available, the dialog can appear immediately. If location resolution fails, a preview may be missing; it is not a saved location.

Coordinates: Enter 47.37688, 8.54169, for example. Check the preview and open the same dialog from there. For a coordinate point, the database name must first be entered manually. Even without a found address, the coordinate path can open the dialog. By contrast, a freely clicked map point without a resolvable address is cancelled with a notice. The selected coordinates are not intentionally replaced by the center of the found street address.

Click Save only once and wait: this immediately requests a separate location master record, before Continue on the project. The customer user creates it for their own customer. If successful, the location is added to the form and the dialog closes. An already existing name in the same area results in a notice instead of a second creation. The project assignment and days still require saving the project.

Cancel or the close icon before submitting closes the dialog and removes the provisional map point; it is not a delete request. After submission, closing does not stop the request. A delayed response can close a dialog that has since been reopened or add a location later. The loading indicator does not prevent a second submission here. In case of transport errors it may remain stuck; in the event of a business error response, the dialog still closes. First check the location list instead of blindly creating it again. Even a success message phrased awkwardly does not replace this check.

Edit an existing name or address: Not in the read-only project row and not by creating the same name again. The separate location management has its own edit path and different save consequences. A general master-data edit dialog is not mounted here as a project action; Change location means something else, see below.

Use the map and add missing coordinates

A pin for an already assigned location opens or marks its project row. Pale available locations can be added by clicking them; they appear only in the matching map section and with sufficient zoom. Their availability depends on the loaded location list, not on a guaranteed global search. A map display alone does not save either days or the project.

Under Locations not shown on the map, you can find locations without usable coordinates. If Place on map is offered:

  1. Click the action for the correct location. An automatically suggested point is only a suggestion.
  2. Click the desired map point and move the provisional pin if needed. Check the name in the map window.
  3. Click Save location and read the confirmation: the coordinates are saved on the existing location and can make the distance warning when clocking in effective even for existing projects with this location. This is not merely a local project draft and not proven GPS/warning delivery.
  4. Only confirmation sends the coordinate change. No does not send it; Cancel ends placement without a new write. After submission, undo is not guaranteed here either.

This path adds missing coordinates; it is not a general move mode for locations that are already fully geolocated. If coordinates appear in the meantime, the server may report a conflict instead of a change; the view then ends placement mode without taking over the success. Recheck in case of errors or parallel editing. While a confirmation is open, do not change the location, cancel, or move the pin again: the confirmation is not fully protected against such local changes. Map/geocoding services may fail. Archive/maintenance status blocks individual actions; a visual form overlay alone is not a reliable permission check.

Edit individual days, multiple selection, and date ranges

For normal projects, open Date range. At least one location must be ticked on the left, otherwise the calendar is not active. With multiple marked locations, it shows their common set of days — a mark does not mean that this day already exists at every location.

  • Add day: Click a calendar day that is not yet marked. It is added to the selected locations. Check the expanded day lists per location.
  • Add consecutive days: Drag in the calendar from the first to the last day. Both boundaries are included, even when dragging in reverse. Existing days are retained; dragging is not a replacement and not a removal.
  • Remove a day from the calendar selection: Click a marked day again. The selected locations are affected, not automatically all project locations.
  • Remove a day from only one row: Expand that location row and click the remove icon next to the date. This is not removing the entire location.

For a day that has already been saved, a request is sent to check existing employee assignments before local removal. This check does not yet delete the day on the server. If rejected or if an error occurs, the day remains or is restored in the calendar. Only Continue transmits the changed day lists; assigned employees are checked again at that point. A locally disappeared day is therefore not final proof of deletion. After removing individual days, do not reorder/remove rows or start additional deletions at the same time: delayed responses can act on list positions that have already moved.

Date-range projects: If the loaded project is managed as a date-range/pay-per-call project, a from-to calendar is active instead of multiple selection; this basic-data view does not offer a separate switch for this project type. Select a location, then start and end. Only one location is selected at a time for the date-range change. The range is applied only when both boundaries are set; clicking only a new start can still leave the previous complete range in place. Therefore check the displayed boundaries of each row. The recurrence tabs are not offered in this mode.

Continue checks all rows, including those not ticked: normal locations need at least one day, date-range locations need both boundaries. The check does not verify every conceivable date order. Past newly added days can first trigger a notice and then, when saving, a separate yes/no prompt; No ends this save attempt without rolling back earlier master-data writes. Check the calendar and day list again after a failed save attempt. Browser time zones and the conversion of dates already present as text may differ; there is no guarantee here of a time-zone-independent transfer. A local draft is not a server-side date backup.

Generate recurring assignment dates and remove exceptions

For a normal project, first tick the desired locations and open Recurring pattern. Without a selected location, or when archive/maintenance status applies, the pattern cannot be applied. This is a helper for generating concrete assignment days, not an indefinitely continuing series and not automatic staffing planning.

  1. Set From and To. When opened for the first time, From is prefilled with today’s local date; To remains to be completed. An empty, invalid, or reversed range does not generate preview days. Both valid boundaries are included.
  2. Choose Weekly and under Repeat on select the desired weekdays. You can use every week, every second, third, or fourth week. Counting starts with the Monday-to-Sunday week in which From falls — not only with the first selected weekday.
  3. Alternatively, choose Monthly, then the first, second, third, fourth, or last desired weekday of the month. “Last” is not automatically “fourth.” There is no selection for a fifth occurrence and no separate public-holiday/vacation calendar here.
  4. Check Preview, day count, and date list. For longer results, only the first seven days and the number of additional days are shown initially. Changes to the pattern fields only recalculate the preview.
  5. Click Apply pattern. You return to the date range. The concrete days are added to the currently selected locations; already existing days and their assignments are retained. Check each location, especially if multiple different day lists were marked. The message count is not the sum of all newly created location-day combinations.

Exceptions: Remove a single day via its location list or a targeted calendar selection. Applying the same pattern again can add this day back: no permanent series exception is saved. Changing the preview does not remove previously applied days either.

Remove matching days removes only the days matching the current pattern from the currently selected locations. Unsaved days are removed locally right away; saved days are checked for assignments first. Days that cannot be removed remain. The summary warning refers to employee assignments, but it can also aggregate failed check requests this way. Do not change the selection or days any further in the meantime: the response uses the location selection current at that point. Only Continue saves the resulting lists. Apply pattern and Remove matching days are not a publication, not a recurring series rule, and not a shared undo boundary.

Change location, remove location, and check save consequences

Change Location moves project days — it does not edit the master-data address. For normal projects with more than one location, click Change Location on the source row, then Add here at the destination. Before the second click, you can choose Cancel on the source row without moving any days. When applied, the days are merged at the destination, duplicate days are avoided, and the source row is removed from the form. There is no additional yes/no prompt and initially no server write.

Caution with existing projects: If you then continue, this change can move existing project appointments and roles to the target location. For affected current/future confirmed or self-booked assignments, the status can be reset to assigned and a change notification triggered. This is neither a guaranteed delivery nor a new personal acceptance. Afterwards, check roles, shifts, and assignments; simply moving the day list is not a complete planning check. Do not save carelessly when locations have the same name or have been corrected in the meantime: parts of the save path resolve locations by name, not solely by the visible ID.

Remove the entire location from the project: Click the remove icon on the location row and confirm the prompt. No does not remove anything. If the row was added only locally, Yes removes it only from the form. If a project-location assignment has already been saved, however, Yes sends an immediate separate deletion request, without waiting for Continue. Existing employee assignments or missing permission can block it; the separate deletion path does not simply require the same Self-Service permission as Continue. If successful, associated roles, shifts, staffing requirements, and other planning data can also be removed. This is not a deletion of the general location master record. Do not remove multiple rows in parallel: a late response uses the earlier list position.

ActionWhat is saved?
Select an existing location, change days/period, apply patternFirst form state; Continue is required for the project assignment or day lists. Not every one of these actions triggers its own local save.
New location: save in the name dialogSeparate master data record created immediately; returning to the project does not delete it.
Missing coordinates: save location and confirmSeparate change to the saved location immediately, not only after Continue.
Remove a single saved dayFirst assignment check and local change, only Continue saves the day list.
Saved location row: confirm removalSeparate immediate project-location deletion path, not merely local removal.
Change location → Add hereLocal merge plus noted change; effect on roles/appointments when the project is saved later.

After Continue, reopen the locations and date lists to check them. An error message does not mean that all earlier partial changes were rolled back; a successful assignment check does not reserve the state against other editors. If anything is unclear, provide the administration with the project, location name, specific date, action, and message instead of blindly creating or deleting again. The subsequent role/shift planning, wages, expenses, criteria, automation, publication, and overall project deletion remain separate processes that are not fully checked here.

Saving a project template: the correct starting point

In the project master data (step 1) there is currently no active entry point for saving a template. Do not look there for a template name dialog. Load from template in the project overview is a different process: it opens a new project from an existing project template; it does not update that template.

For the available save path:

  1. Check the master data and save it with Continue. Wait for the confirmed result; merely opening the next page does not prove that all changes have been saved.
  2. Wait in Project planning (step 2) until the correct project has been loaded with its customer and ongoing changes are finished. Check the required roles and shifts. The following instructions cover only the project template action, not the entire planning process.
  3. Click Save as project template above the planning. The dialog is called Save as template and contains Template name.

The visual lock on the entry point depends on whether the project can be edited; it is not proof of template write permission. Server-side saving or overwriting requires the permission to edit templates or the permission to edit all Self Service projects. Having only the permission to edit your own Self Service projects is not automatically sufficient for this template path. If you lack permission, involve the administration; do not use another customer account.

Naming and saving a new project template

Before saving: A project template is a separate saved record for later reuse. It is neither the local draft save nor a substitute for saving your project changes. In particular, check the project, customer account, and desired template name.

  1. Enter a clear, non-empty name in Template name. This is the template name, not renaming the project. An empty field leads to Name is required; do not use only spaces either.
  2. In this dialog there is no type selection, no customer picker, no visibility switch, and no list of existing templates. The type is project template; in Self Service the customer area is passed through from the loaded project and bound server-side to the permitted customer context. The visibility of the customer name for employees is something different from this template scope.
  3. Click Save once. Pressing Enter in the name field triggers the same save attempt. The dialog closes immediately, before the response arrives — even with an empty name. Closing alone is therefore not proof of success.
  4. If the name is new, a new project template is requested. Wait for the message and then check via Load from template in the Self-Service project overview whether the desired name is offered. Opening the list alone does not create a project; only an intentional selection starts creation from the template.

The name check takes into account the template type, agency, and customer area. The same name in another template family is not automatically the same template. A new name does not create a new version with a guaranteed history; use a distinct name for a deliberately separate template.

Overwrite an existing project template or choose No

If a project template with this name already exists in the same area, the confirmation A project template with the name … already exists. Update this template? appears. There is no additional selection of another template here. The entered name determines the found entry; the template loaded earlier when creating it is not automatically overwritten just because of that origin.

Caution before Yes: You replace the content of the found template for later use. Check the name and project once again. The new content is assembled only when you confirm, from the then current project state; therefore, while the confirmation is open, do not switch projects or continue editing.

  • No does not request an overwrite. The previous name check has therefore not become a new template record. Open the name dialog again if needed and use a different name.
  • Yes sends a separate update of the found project template. Wait for Project template updated successfully. and check the desired content the next time it is used. A message alone does not replace content verification in the event of errors or parallel editing.
  • The checked project template update path replaces the template content, not automatically the projects already created from it. These are not treated as continuously synchronized copies. Already open forms can still contain the old state; reopening later can load the new state.

The confirmation offers no versioning or undo function. If an update was made by mistake, do not save blindly again: clarify the template name, customer, and desired state with the administration.

What is copied when loading a project template

After Load from template in the project overview, a new project is opened. Check the values before Continue instead of expecting a complete, unchanged copy:

AreaBehavior in the master data
Name and descriptionMain values and existing language versions are copied.
Customer, project management, and project typeSaved assignments are copied; the selection lists are reloaded for the template customer. Do not proceed if the customer context is not appropriate.
Numbers, cost center, and departmentProject number, order number, cost center, and department assignment are copied. A copied project number may already be in use.
Locations and assignment daysLocation objects remain, but normal assignment day lists and their saved day identifiers are cleared. The days must be selected again. If the location list is missing in an older template, this part starts empty. This does not guarantee that every other location field or a period is also reset.
Other saved master dataAmong other things, image reference, parent project, status/archive flags, period type, buyer, timekeeping managers, and automation/employee visibility values can be copied. Some fields are not directly visible in the customer form. Check unusual states before saving; the respective settings control is not enabled here.

For older templates without the relevant visibility values, the customer is visible to employees by default, but the project management and timekeeping managers are not. Missing automatic invitation is copied as switched off. A copied setting alone is not an invitation, booking, publication, or confirmed personnel assignment.

The new project identifier is not copied from the template in this master-data loading path. Continue saves the new project. When subsequently moving to planning, the template can be loaded again and embedded roles can be created separately; this is not just displaying again and is not a guaranteed atomic overall process. Therefore, do not change or overwrite the template in parallel with an ongoing creation. Full role/shift transfer and personnel planning remain separate processes.

Wait for loading to finish before changing values: a delayed template response can replace entries you have entered in the meantime. If a template is unreadable or language data is faulty, do not select it repeatedly; provide the template and the message to the administration.

Distinguish Cancel, errors, and independent saving

Cancel or the close icon in the name dialog before sending closes it without a template request. An already submitted request is not withdrawn by doing this. The name is not explicitly cleared when closing; check it the next time you open it.

ActionLimit
Local AutoSave in the master dataSaves only a new record not yet created on the server in the same browser; does not update a project template.
Continue in the master dataSaves the project, not automatically its source template.
Save or Enter in the project template name dialogSeparate template request; no shared save process for all open project changes.
Yes when overwritingSeparate update of the template record.
Back, Cancel, or NoDoes not undo a previously successful independent save.

When creating the template content, project details are merged with saved roles and shifts. Missing certain master data is supplemented from the saved project; if the location list is missing or empty, it can also be reloaded. Therefore, first finish the desired project changes: a preview or still-open role editing does not guarantee that exactly this visible intermediate state will end up in the template.

If there is an error, no message, or an unexpected confirmation, first check the existing template state. The dialog does not have reliable double-click protection. Transport errors are not separately caught in the save handler; a missing response proves neither success nor a safe non-write state. A delayed success message can close a name dialog that has been reopened in the meantime; a delayed name-conflict response can open a confirmation only after that dialog has been closed. Do not press Enter or Save repeatedly and do not choose Yes too quickly. Give the administration the project, customer account, template name, last action, and message.

Do not confuse project templates with role templates

Save as project template applies to the project together with embedded role information. A separate role template is a different template family: when saving a role template separately, cost center and department references are removed from the template content. The project template uses a separate structure: its embedded roles contain cost center references. The transfer of the department in the project master data is separate from this; this does not mean that role-based department assignments are copied unchanged. Do not transfer the rules between the two families.

The name dialog described here changes neither the template type nor the customer assignment of an existing template. To create a new project, you choose a project template via the project overview; the separate role template picker and the template management have different processes. Successful template saving is not permission to perform all role, wage, expense, criteria, publication, or assignment actions.

Detailed template management remains separate. Likewise, this section does not cover inviting people responsible for time tracking, using the visibility/automation switches, media/translation editing, or deleting and cancelling entire projects. These actions are not a substitute for cancelling a template dialog.

Select existing people responsible for time tracking

The following sections supplement the master-data instructions for customer users in Self Service. The field in question is Person responsible for time tracking, not the customer project manager and not the general employee invitation to register.

  1. Open the new or existing Self-Service project in step 1 and wait for the loaded master data.
  2. Click in select or invite person(s) responsible for time tracking. Search by name. The search filters the loaded names locally, without case sensitivity; it is not an email search and not a new server fetch.
  3. Click an existing result to select it. Multiple people are possible; the list remains open after a selection. Remove an unneeded selection via its remove icon; this does not delete a user account and does not revoke an invitation already sent.
  4. Check the selected names and save the project assignment with Continue. A selection alone does not send an invitation. In a newly created project that has not yet been saved, the selection can trigger local draft saving; in an existing project, it does not replace the later project save.

Enter is not a safe confirmation of a result here: In the open selection field, Enter opens the invitation dialog, even when the search text is empty or an existing result is highlighted. Therefore, click the result to select it. Close an accidentally opened dialog with Cancel, not with Save.

For normally loaded Self-Service data, the suggestions come from the user assignments belonging to the customer whose customer role has the permission for responsibility for time tracking. A matching additional agency/customer assignment of an existing account can also be considered. Not all employees or customer contacts are simply offered. After a new invitation, however, the list returned immediately can also contain agency users; the list restriction is not identical on these two response paths. If unexpected people appear, do not select blindly, but have the customer context checked and reopen the project.

An empty list can mean missing matching users, missing read permission, or a loading error. Archived or still pending order statuses block the picker; missing project edit permission and form overlay are separate from that. A visual block or an accessible dialog does not prove server-side permission. If the control cannot be used, involve administration; do not bypass the block.

Open the invitation dialog for a new person and check the fields

First check whether the person is already selectable as an existing user. The dialog is not a re-invitation of an existing account and not merely the creation of a contact person.

  1. Type the new name into the Person responsible for time tracking field and press Enter. The Invite person responsible for time tracking dialog opens; its role list is loaded separately. Opening it alone does not send anything yet.
  2. Check First Name and Last Name. The search text is taken over in full as the first name and is not automatically split into two names. The last name must be filled in separately.
  3. Enter the correct email. It is both the recipient address and the address of the new user account to be created. Check the spelling and recipient before sending; the form does not confirm deliverability.
  4. Select role and language. The language list offers English, German, French, and Italian. The role comes from the time-tracking roles enabled for the agency, not from a fixed, always identical role list. Retrieving the role additionally requires the corresponding time-tracking permission of the acting user. Agency roles may also be offered; for a customer user, clarify the intended customer role with administration. Selecting a role is not merely a label for this project.
  5. Before every submission, check all five fields again. On first opening, last name, email, role, and language are empty. When reopening, old entries and old role options may remain; only the first name is set again from the search text. A delayed role response can replace the list.

All five fields must be filled in. If values are missing, Please fill in all mandatory fields before saving. appears. The validation is not a reliable check for spaces only, a valid email address, or the current membership of the selected role in the loaded list. Do not use names consisting only of spaces. The dialog offers no phone number, no department selection, and no editable message preview. In particular, the department selection from the separate Client Buyer dialog must not be transferred to this dialog.

Saving in the invitation dialog sends its own request immediately

Warning: saving in this dialog does not wait for Continue in the project. It immediately requests a new user account and an invitation. This works as a separate process even before the first project save. Submit only if you intend to create the account and send the invitation.

  1. Check the email, names, role, and language; also check the project name that is copied into the invitation. If name changes have not yet been saved, this may differ from the language field currently visible.
  2. Click Save once. There is no additional Yes/No send confirmation. The loading indicator is not a reliable block against a second click.
  3. If the request is answered successfully, Invitation sent successfully. appears, the dialog closes, and the returned user ID is added to the local project selection.
  4. Then check the selection and save the project assignment separately with Continue. The invitation request does not send any request to save this project assignment. Even the success response does not itself trigger the local draft save here.

The account creation saves a user account that is initially unconfirmed and an invitation entry. For customer roles, a downstream department assignment is also triggered. This is not a single project save that can be undone. A technical limitation can prevent the new account from being assigned to the customer; therefore, a success message does not prove that the person will be available in the correct customer picker after reloading or that they can already access it. If the person is missing, have the account, customer, role, and department assignment checked instead of creating a second account.

If the email is already assigned to a user account that has not been deleted, this creation path rejects it as already existing. It then sends no new invitation and does not automatically link the existing account to the project. This also applies if the person does not appear in your list. A different spelling or a new address is not a suitable way to bypass this conflict; have the existing access and assignment clarified.

Distinguish cancel, errors, and actual sending

Cancel and the close icon at the top close the dialog. Before sending, this creates neither an account nor an invitation; however, old entries are not explicitly cleared. After clicking Save, closing the dialog is not a cancellation of the request already in progress. Going back from the project, removing the local selection, or discarding a local project draft also does not undo the standalone account creation or a send that has already taken place.

A late success response can still add the selection and even close a dialog that has since been reopened. While loading, do not change the recipient address and do not send again: the already submitted request keeps its old address. Multiple sends are not reliably prevented; the same ID can also be added locally multiple times by multiple responses. Simultaneous loading responses can temporarily replace the suggestion list.

In the event of a transport error, the loading indicator ends, but a response with a different business status may leave it running. An error message or missing response does not prove that no account or invitation entry has been saved yet. Before trying again, have the existing user and invitation status checked. Tell administration the project, intended recipient, action, and error message; do not forward access credentials.

The intended email route addresses the entered email and uses you@job.rocks as the sender together with the platform brand name. In German, the subject is Einladung als Verantwortlicher Zeiterfassung. The message contains the project name and temporary access credentials; it is not the general employee registration invitation and not an invitation message for an employee shift.

Request accepted ≠ sent ≠ delivered ≠ login or invitation accepted. The email route may fail to send, for example because of a blocked address, sending environment, or mail error, while account creation still returns a success response. The message Invitation sent successfully. is therefore not a reliable confirmation of sending or delivery. First check the account creation, then the sending status, and if necessary the spam folder with the intended person. A successfully created account alone confirms neither a login nor a completed project assignment.

Separate visibility for employees and time-tracking permissions

Next to Person responsible for time tracking there is the visible to employees switch. It controls whether the selected people responsible for time tracking are passed on as contacts in the corresponding employee assignment data. First name, last name, and email may become visible; no phone number of the user account is delivered through this contact path. Activate it only if these contact details should be visible.

The switch first changes the project form and here has no separate immediate save or send action. Save with Continue and check the status after reopening. In a newly created empty project, this visibility is off; loaded templates or drafts can bring a different value. Switching it on or off does not invite anyone, does not change any user role, and is not the approval of working hours. Switching it off also does not remove the person from the responsible-person selection and does not revoke access.

The saved responsible-person selection is used for the associated project list for people responsible for time tracking; additional prerequisites apply there, such as matching shifts and time/assignment data that are still relevant. An assignment therefore guarantees neither a visible task nor an unrestricted review or edit right. Role permissions and the respective time actions are checked separately. Full time-tracking and expense validation, other visibility switches, project deletion, and automation functions are not covered by this guide.

Visibility and automations: open and save deliberately

As a client user, open Self Service → Projects, select the relevant project, and open step 1 (basic data). For a new project, start via the project creation path already described. Wait until the project data has loaded. The automations are located below the fields for number, cost center, and department; the visibility switches are directly beside the respective responsible persons.

  1. First check that you are editing the correct project and the correct template. The automations mentioned below are switched off in a fresh project without a template; the cancellation period is empty. A loaded template or an existing project can have different values.
  2. Change the desired switches and, if necessary, the cancellation period. Switching them initially only changes the form. It neither sends an invitation immediately nor triggers its own save request for the switch. Unlike the flags in the project overview, this is not an immediately saved table action.
  3. Also check the remaining basic data and click next. This saves the entire project form, not just the last changed switch. Wait for a successful response. Then reopen the basic data and check the values and affected shifts. For subsequently turning on auto-close, the special immediate consequence below applies.

The switches themselves do not trigger a local autosave action. In a new project, a later field action or leaving the view can locally save the current overall draft in the browser; when the cancellation period is exited, this path is explicitly called. That is not server-side saving. For existing projects, there is no local draft save beyond that. Back is therefore neither save nor a reliable discard. There is no shared reset button for these settings here. A rejection prompt before saving does not start this project save process, but it does not reset the switches either.

Do not change anything when archived, when the order status is pending, or when edit permission is missing. The main form is then visually overlaid; the individual switches are not all technically blocked in the same way. An input that still responds is not authorization. For a new project, the Self Service creation right applies; for existing projects, the appropriate all/own edit right together with responsibility and client/agency area applies. Visibility for employees does not grant any of these rights.

Do not perform any further switch tests while loading or saving. A delayed loading response can replace local changes; an old successful save response can be forwarded despite newer local changes. Error messages do not reliably reset the local switches to the saved state. If the response is unclear, reopen and check first, do not save blindly again. Switching off after a successful save is a new change and does not undo invitations, closures, or messages that have already been created.

Templates and missing values: Templates carry over self booking, cancellation, deadline, republishing, and auto-close. If one of these values is missing in an old template, it is not reliably supplemented by a new form default; check the display before saving. When saving, missing automation values are treated as off. If project manager visibility is missing in a template, it is treated as off; if the client name switch is missing, it is treated as visible. An explicitly saved off value is not the same as a missing value. For existing projects, the loaded project state is retained; the default values of a new project do not replace it. The separate visibility of the persons responsible for time tracking remains as described above.

Project manager visible to employees: known limitation

Next to Project Manager there is visible to employees. First select the intended project manager, set the switch, and save with next. This switch does not grant portal rights, invite anyone, or automatically notify the project manager. It is also not the visibility switch for Responsible for Time Tracking explained above.

Important in Self Service: The project manager is selected here from the client contacts. However, in the tested state, the contact display for employees reads the agency project manager, not this selected client contact. Therefore, switching it on is not a reliable way to show the selected Self Service project manager in the employee app. If an agency contact has been adopted, that one may appear instead. Check the contact that is actually displayed and have administration clarify the assignment if it differs. Do not rely on this switch alone for required assignment information.

The separate switch for the client name is hidden in this client view. Agency users may have a different view on the same Self Service path; this does not create any additional client-side operation path. For new projects, the client name is generally preselected as visible. A template or a saved project can hide it. This is separate from contact display, the client's access to the project, and time tracking rights. Invite Client Buyer is also not a dialog reachable here through this visibility switch.

Automatic invitation upon activation

Activate auto-invite upon activation and save with next if newly activated employees should be considered for suitable assignments in the future. This refers to activating an employee assignment to the agency, not opening, saving, or activating this project. Creating an already active employee assignment for the first time can also trigger the background process. Switching it on alone does not retroactively invite all already active people.

At processing time, the background process considers projects of the same agency with the status open or ongoing and the flag switched on. For a role, there must be a saved employee filter and open requirements from today's date onward with a positive target quantity including overbooking. Invitations are only created if the activated person matches the role filter. Existing entries for the same person and the same requirement are not created again, even if their status is no longer open. This is not a promise for every employee in the client pool or for every project.

Distinguish notification and acceptance: This activation path creates pending invitations and a related automatic publication entry; it does not include any separate email or push delivery to the employee. An invitation or history entry is therefore not proof of sending or delivery. The person is also not yet assigned and has not accepted. Check the actual invitations and communicate required assignment information through the intended channel. Background queue, processing, and visible final state are separate; if there are delays, do not try to help by repeatedly deactivating and reactivating.

Switching it off and saving does not prevent already created invitations from remaining in place. A background process already running can continue processing the state it read earlier; there is no cancel button for this run.

Self booking instead of mere application

Activate self booking in the basic data and save with next if employees should be able to book an offered assignment themselves. Switching it on alone does not accept an existing application and does not automatically assign anyone. Only the corresponding action by the employee on an invitation starts the self-booking path; without self booking, the application path remains separate.

A self booking first sets the relevant invitations to accepted and then tries to assign them into free slots. For this, it searches today's and future requirements with a free assignment slot, a matching accepted application, and no detected shift overlap. It can still fail to create a slot, for example if none is free anymore by then. The checked assignment run validates the project and can also take further matching accepted invitations of the same person in this project into account; do not infer the scope solely from the last clicked offer. Check the actual shift assignments, not just an accepted invitation or success message.

The notification email for self booking can be triggered before this assignment attempt. Recipients are the non-empty client list for this event, otherwise the agency list; without either, there are no recipients for it. Such an email proves neither a filled slot nor delivery. If a self booking actually occurs, membership in the employee pool of the project agency is also ensured; any problem there is handled separately. Switching it off does not retract existing self bookings or pool memberships. Self booking does not replace any general access, assignment, or time tracking rights.

Auto-close: existing shifts can be affected immediately

Before switching it on for an existing project, check the open shifts and applications. Set auto-close and save with next. When switching from off to on, already sufficiently staffed open shifts in the project are checked and closed during this save operation. This is not just a rule for later shifts; existing data can also be affected. There is no separate closing confirmation for this. When creating a new project or saving again with an already enabled flag, this special retrospective check is not started again in the same way.

Confirmed assignments and self-bookings count as staffed, not merely assigned but unconfirmed places and not just accepted applications. If this number reaches the staffing requirement, the closing path can take effect. The overbooking amount is not added to the number required for this; staffing requirements without a positive total are not closed in the closing path. Later corresponding assignment/confirmation actions can also trigger the check.

Closing is more than a flag: pending and automatically accepted invitations are removed in the closing path. Accepted applications are closed; for applicants without an already assigned or confirmed shift of the same role, a push notification shift filled can be triggered. Self-bookings are not treated the same for this notification exception: a person who booked themselves can also receive such a message. Existing assignments are not generally cancelled by this; if a notification conflicts, check the actual shift status. A suppressed or failed push notification is not proof that closing did not happen.

Turning it off and saving does not automatically reopen already closed shifts or restore removed invitations. If an assignment is later removed, a closed shift can fall below the staffing requirement and be reopened while the flag remains switched on. Reopening alone is not a new invitation and not a delivery confirmation; the separate republishing is relevant for that.

Auto-republish when an assignment becomes available again

Set auto-republish when an assignment becomes available again and save with next. This is a rule for later supported cancellation/release processes, not an immediate publish button. Not every decrease in staffing triggers the same path: employee cancellation uses it directly; the general removal path additionally requires a recorded cancellation and a previously confirmed assignment or self-booking.

The affected shift must exist, be open, and not be before today's date. Its role needs a saved filter with suitable people. A shift that is still closed is skipped; the automatic reopening explained above can therefore be crucial for the interaction. The cancelling employee is omitted from this repeated invitation.

Warning: In the tested version, automatic republishing can clear the stored application deadlines for all roles in this project — not just the deadline for the shift that has become free again. This happens before the later selection of individual recipients and can therefore also occur if all initially found people are excluded afterwards. After such a process, check the application deadlines for all roles in the project with the responsible planner. Turning it off does not restore application deadlines that have already been cleared. The cancellation deadline in days is separate from this.

For suitable active people, the process tries to create missing invitations. If the staffing requirement is 0, the invitation helper can skip the new creation; a push notification alone therefore does not prove that an invitation was created here either. Check the actual staffing quantities and invitation list. Already pending invitations can receive a push notification again; other existing response statuses are not simply reset. The automatic publication entry and notification entries are not delivery confirmation. Repeated similar notifications are suppressed within a short time window; this does not guarantee one message per shift nor does it reliably protect against any parallel duplicate processing. This republishing path uses push jobs, not a separate email broadcast to employees.

Turning it off does not reverse invitations, publication entries, or requested push notifications that have already been created. If nothing new appears after a cancellation, check the saved switch, open status, date, role filter, and existing invitation statuses. Do not test by cancelling again and do not start repeated publication as a repair measure.

Employee cancellation and setting the cancellation deadline

Activate employee cancellation. This makes the field cancellation deadline (days) appear. Enter at least 2 days, leave the field, and save with next. Blank, 0, negative values, or values below 2 prevent the form from being released when cancellation is enabled. Use whole days; the form does not contain reliable additional integer/max-value validation. When turning it off, the deadline field is hidden, but its previous value is not deleted. Therefore check the deadline again when turning it back on.

The employee app compares the distance to the start of each assigned shift in minutes with the configured number of days times 24 hours. At the exact boundary, the cancellation action is still visible. This is not about the end date of the overall project and not just about calendar days. This display check is not a guarantee of a comprehensive server-side deadline lock. If there are deviations or the action is unavailable, contact the responsible planner; do not try other ways to bypass it.

The switch itself does not cancel an assignment and does not send a message. Only a cancellation carried out and confirmed by the employee can remove the assignment, trigger the reopening/republishing rules, and initiate a cancellation email to configured recipients. Here too, a non-empty customer recipient list is used before the agency list. An email can be blocked or fail without this implying a reversal of the cancellation. Check the assignment status separately. Changing deadlines and turning the feature off do not undo cancellations that have already been processed.

Do not confuse this: In this customer master data form, there is no additional accessible NOH or general "auto-accept" switch. The rules for reorders, publication, and time tracking are separate processes. Do not use self-booking or the cancellation deadline as a substitute for this.

Buyer invitation in the customer form

As a customer user, you will not find an accessible Invite Client Buyer dialog in these self-service master data: the associated selection and opening area is hidden for customer users. The separate dialog Select or invite a time-tracking supervisor is a different process. Do not transfer its instructions or role selection to the Client Buyer.

An agency user can open the same self-service address with a different view. That does not make their buyer invitation a customer function. If responsibility is wrong, have the stored buyer assignment checked by the responsible administration; merely seeing a dialog name in another view is not proof of your authorization.

Distinguish Back, confirmation, and destructive actions

Check before confirming: Back, delete project, and cancel project are three different processes. Deletion and cancellation are requested immediately after Yes; next is not required for that. There is no guaranteed reversal, refund, or shared all-or-nothing processing here.

  • Back returns to the self-service project overview without a deletion or cancellation request. When leaving, an unsaved project draft can be automatically saved locally. Back is therefore not a safe discard.
  • delete project and cancel project appear when a project name exists and the permission delete & cancel self service project is present. The normal agency right to cancel a job does not replace this self-service right. Archived projects and pending or rejected drafts are additionally overlaid in this view. A greyed-out area is not a promise about all technical blocks.
  • For a saved self-service process, the special delete/cancel right and the appropriate customer/agency area are checked again. This is not automatically limited to projects where you yourself are the buyer; view or edit own/all projects are different permissions.
  • In the confirmation prompt, No does not perform either of these two mutations. It also does not save any remaining form entries or reverse individual actions already carried out earlier.

Before Yes, check the project, existing assignments, and the intended action. Do not confirm again while a request is still running; there is no documented separate double-click protection here. If the response is unclear, first check the overview and the project again instead of blindly repeating the action.

Delete project: stored data and local draft

Warning: Deleting a saved project removes more than just the visible master data. It also affects associated roles, shifts, staffing requirements, free assignment slots, applications/invitations, publications, and other project-related data. This is not archiving.

  1. Check that you really want to delete the entire project, and choose delete project.
  2. The prompt reads Are you sure you want to delete this project? With No, this deletion request does not proceed. Only Yes starts it.
  3. If an assignment record with an employee ID greater than 0 is still linked via a project role, this deletion path is rejected — not only for confirmed assignments. Clarify the existing assignments with the administration; cancelling is not a harmless substitute to bypass this message.
  4. Only a successful deletion response returns the view to the self-service project overview. In the case of a business error message, it remains open. After a technical or unclear response, have the actual status checked; partial changes are not guaranteed to be automatically rolled back.

The deletion scope also includes associated time/cancellation and rating data, payroll/expense and clothing data, messages, role-based notification records, validation and other project links. Messages already delivered are not recalled by this. Subprojects are not deleted with it: their link to the deleted parent project is cleared. Saved project templates are not deleted in this process. For the project image, before removing the file it is checked whether it is still referenced by an agency, customer, other project, or a template; this is not a blanket deletion of shared logos. Removing project-related billing/credit records does not imply any promised financial refund. This deletion path does not contain a separate employee dispatch job.

Draft not yet saved on the server: Without a project ID, after Yes the same button only tries to remove the matching local autosave entry and return to the overview; it does not send a project deletion to the server. In the tested version, however, the subsequent automatic saving when leaving can recreate the draft. Do not rely on permanent discarding here; check the draft list again. Contacts, departments, or locations already created separately are not undone by this local draft action.

Cancel project: release assignments instead of deleting shifts

Warning: Cancelling releases existing employee assignments and can trigger notifications. Check the affected schedule before Yes. It is neither merely closing the view nor a draft step that can be reliably reversed.

Choose cancel project for the saved project. The German confirmation prompt can be translated as The project will be deleted, all assignments will be cancelled and the corresponding employees will be notified. Continue?. This wording is not an exact description of the saved effects: the tested process keeps the project, sets its type to cancelled, and prefixes the saved name with C/. Roles, shifts, and staffing requirements are not deleted. For existing assignments, the employee assignment is cleared and the assignment status is set to unassigned. Invitation/request records linked via project publications are permanently removed. A saved template is not changed by this.

No does not send a cancellation request. Yes starts the request regardless of the general next. The process is not limited to future assignments. Notifications are triggered before the subsequent changes: selected are people with requests linked to publications in the status assigned or completed. This is not a promise that every actually assigned person will be captured. This path uses a secured push job, not a separate email job. A successful response does not prove delivery; a failed push does not automatically prevent the subsequent cancellation.

After the response, this master data view remains without automatic refresh. The local success display does not reliably check the business response status. Therefore reopen the overview and the project and check the cancelled type, assignments, and requests; a visible translated project name does not have to show the new name prefix. Confirming again is not a safe retry method and can add the prefix again. For a local-only draft without a project ID, cancellation is not a usable discard button: it still attempts a server request and does not remove the local draft. In the case of errors or an unclear response, do not assume a complete rollback, restored invitations, or notifications sent.

Error dialog while loading and OK for past data

If the dialog Error! appears while loading the master data, read the message before closing it. The x closes this dialog and then takes you to the start page, not automatically back to the project overview. This loading error disables the local automatic draft saving when leaving; closing is not a deletion, cancellation, or save confirmation. A missing edit permission may instead only block editing without opening this dialog. Not every technical issue is shown in exactly this dialog. If the error repeats, have the project and access checked instead of concluding from the error that planning was deleted.

The OK notice after selecting a past date is separate from this. It informs you that some functions do not support historical data. OK only confirms the notice: it does not save a project, remove a date, or trigger employee notification. The separate Yes/No question when saving newly added past data remains a different step; see locations and assignment data. Shared Yes/No buttons always carry out the question currently shown, not a general "save project" action.

Select project image and check upload

The image field is at the top of the project master data. Click in the upload area and choose an image file, or drag it in. The upload starts automatically after the file is accepted, not only with next. Upload files one after another and wait for feedback each time. The selection accepts the browser-reported type image/*, at most one file accepted at a time, and up to 50 MiB. This is a selection check, not a promise that every image format can be processed server-side. The processing also tries to correct the image orientation.

Before selecting, distinguish:

SituationEffect of the upload
New project without a saved project IDThe file is uploaded already, but is initially stored only provisionally. Only successful project creation assigns the image path to the project.
Reopened existing project with IDA successful upload immediately replaces the stored image path. Back does not reverse this image change; no further general save step is required for this upload.

The image actions also use the permission edit own projects. The self-service edit permissions alone therefore do not explain every rejection. If the project is archived, if there is a pending order, or if editing is unavailable, the image area is blocked for pointer interaction. This is not general proof of a server-side status lock. A separate keyboard opener for the upload area is not documented here.

After a successful response, the image is displayed and the individual upload preview is removed from the queue. This disappearance is not image deletion. A preview alone proves neither the complete project save state nor a successful creation. If there is an error message, check file type, size, and permission; if the result is unclear, reopen a saved project before uploading again. Late responses can replace a display that has since changed; there is no reliable protection here against parallel image changes.

Temporary files are not a permanent draft store: a cleanup job takes files into account whose temporary entry is older than one day. This does not give you a guaranteed deletion time. Images still referenced by the agency, customer, project, or project template are protected during the tested cleanup. Therefore fully save any needed new project; local draft saving does not replace image assignment.

Remove and enlarge project image

For a displayed image that is your own or not marked as an agency logo, Delete and Enlarge appear. A replacement image displayed as an agency logo does not have these two actions.

Delete is a separate request, not a pending form change:

  1. Check the project and the image currently displayed. Click the trash icon Delete.
  2. In Confirmation, “Do you really want to delete this?” appears. No closes without a removal request. Yes starts the removal immediately; do not click again preemptively.
  3. If there is a saved image reference, a found project is switched to the agency logo. If there is no such match, a temporary image that is not referenced elsewhere is released for removal. Other references may prevent the physical file from being deleted. This is neither deleting the project nor deleting all copies of the image.
  4. Check especially carefully when images are shared: The removal path searches via the image path, not uniquely via the open project. With multiple projects using the same image, another project reference may therefore be affected. Have administration review an unclear case instead of trying to correct it with more clicks.

If an agency logo returns, the display changes, but the previously local project image path is not reliably replaced in this response branch. Reopen a saved project after the removal and check the image before saving any other changes with Next. Otherwise, the old path may be sent again. Save or back up any required text changes before removing the image, not only between removal and reopening. An error response or missing update is not proof that the file remained unchanged; there is no guaranteed shared rollback of file and form.

View only: Click Enlarge to open the image in the large view. Clicking the image or its content area keeps the view open. Clicking the outer background or the close icon closes it. Opening and closing do not change either the image path or the project save state. No separate Escape close path is documented for this simple image view; it is not the same component as the other confirmation dialogs.

Open the desired language tab and edit Project description. The tabs are called English, Deutsch, Français, and Italiano; switching between them alone does not save or translate anything. The following clarification supplements the 500-character limit described above: the plain text is counted without exactly the editor’s last line break, not the length of the saved HTML. Internal line breaks count; some characters such as emoji require more than one unit.

If the visible editor is changed, content that is too long is reset to the last accepted HTML content for that language, if necessary to empty. After a complete clear, the last accepted state can still be older text. This check is skipped for hidden language tabs. The limit is therefore not a general server-side guarantee for loaded or automatically translated texts. Check each required language visibly, shorten long texts before pasting, and then verify the actual content.

Set or change a link:

  1. Select the text to be linked. Click the chain icon HyperLink; alternatively, Ctrl+K or the corresponding command key is provided in the editor. Without selected text, this insertion path does not open a new link dialog.
  2. Enter the target address in the small link window and confirm its apply action or press Enter. Escape closes this link window without applying the newly entered target value. This does not yet save the whole project.
  3. For an existing link, place the cursor in the link. The link window offers target preview, editing, and removal of the link. The target preview can open the external address in a new tab; check it before opening. Removing a link does not remove the text.

When plain text is pasted, recognized addresses are linked with http://, https://, or www.. Typed addresses are linked afterward when leaving the editor; existing links remain intact. www. receives http:// as a prefix. Check the target address, especially when punctuation appears directly after an address. Protected spaces from pasted text are normalized.

The visible toolbar here contains only the link button, no image/video upload buttons and no full formatting palette. This does not mean “plain text only”: inserted formatting and the editor keyboard shortcuts for bold, italic, and underline are not excluded by this narrow toolbar alone. The description is stored as HTML.

A grayed-out editor is not reliable proof of a technical writing lock: the editor version used here does not implement the disabled set here as its own write-protection function; in addition, the form’s pointer overlay is active. Edit only projects that have been explicitly released. When leaving the editor, the local draft save for suitable new entries runs, not an automatic general server save process. For permanent saving, the rules for Next described above still apply.

Translate name and description selectively

Before translating: The service sends the selected source text to the configured DeepL translation service. This is not a purely local browser function. Enter only content that is approved for this external translation path. This instruction does not promise a specific operating location, retention period, or error-free operation of the external service.

  1. Open the target tab, for example Deutsch. If a name or description exists in another language, the magic-wand icon appears with the matching hint, such as Translate into German. While the translation is in progress, this button is disabled.
  2. Check the source before clicking: the first other populated language in the order English, German, French, Italian is used automatically. A name or a description is already sufficient. The same source language is chosen for both fields, not the best available language for each one. Example: target German, English name available, description only in French — then the English name is used; the French description is not additionally used.
  3. Click the magic wand once. A non-empty source field is translated and replaces the corresponding target field even if text is already present there. A truly empty source field does not start a request and leaves the target field as it is. This is not a “fill in missing translations only” button and not a translation of all tabs at the same time. Even HTML content that appears empty can count as populated.
  4. Wait and check name and description separately in the target tab. They may be processed by two requests. The button returning after an error is not proof that both results are complete and correct. One part may already have been replaced while the other remains unchanged or arrives later.
  5. Check name length, visible description, links, and meaning. Then save via the normal project path and verify the language versions after reopening.

Do not correct the target text in the meantime and do not blindly translate again: A delayed response can overwrite target text entered in the meantime. Switching tabs does not cancel the original request. The local error path removes the loading lock, but does not provide its own reliable field error message or restore the previous text. A repeated request can overlap with the other field request that is still running. If there is an error or the content remains unchanged, first check which fields have already been changed.

The translation request does not save any project changes. Its source-language selection is also not the priority used for later project saving: there, German still takes precedence over English, French, and Italian for the first existing name. For customer users, the main values can then be written into the account language. Preserve any required own translations before they are overwritten and check them after saving.

Project type: click an existing match instead of Enter or Tab

The three selection lists Project type, Project Manager, and department each accept exactly one entry. The search filters the loaded names; it is not a promise that a missing match does not yet exist. Upper/lower case and accents are handled differently in the search than in the exact name check for a new project type.

For an existing Project type, click the match and then click the next field. Tab does not select a match that is only highlighted: it closes the list, but also triggers the type creation with the last accepted search text. That text may still be stored temporarily even after clicking or clearing. Therefore, do not continue with Tab from a just-filtered type selection if you do not want to create a new one.

Enter first accepts the highlighted match in the open picker and clears the search. When released, this empty search value is accepted first, then the creation handler runs into a technical error. In this event sequence, no additional type is requested; the already selected assignment remains. Do not rely either on a guaranteed harmless confirmation or on reliable creation of a new item with Enter when matches already exist. For an intended new creation, type the full name again, check the match, and use Tab once. If there is no response, do not repeat it: multiple requests are not blocked and a delayed response can replace a newer selection.

The × removes only the assignment in the form, not the type master record. For a new project, local draft saving is triggered; for a saved project, the type assignment is only changed permanently when the project is saved later. The separate type creation is distinct from this and may already have been saved beforehand.

Project Manager: Enter and Tab can unexpectedly open KONTAKTDATEN

Enter can also open the dialog CONTACT DETAILS after selecting an existing contact. Tab opens it even when the search is empty; a highlighted match is not selected by Tab. Opening the dialog alone does not create a contact yet. For existing project managers, click the match and then click another field. Close an unwanted dialog with Cancel, not by confirming with Save.

After Enter on a highlighted match, the dialog opens with the first name cleared because selection happens first and the cleared search is then applied. With Tab, however, the dialog adopts the last cached search text. No check is made as to whether an existing contact has already been selected. After selecting or clearing, the visible search may be empty even though an earlier search text is still cached. Check first name, last name, email, and mobile number completely: the opener does not reliably clear the old contact fields. Automatic splitting affects only exactly two words separated by a space; other inputs can leave an old last name in place.

For a truly new contact, enter the name again, press Tab once, and check all dialog fields. Only saving requests the separate contact creation. Late responses can still replace a selection that has since changed; closing after submitting does not revoke the request. The × in the picker removes only the project assignment, deletes no contact, and sends nothing. The Project Manager remains a required field; after clearing, click a suitable existing contact again.

Department: Enter is a creation action, not just a selection

Enter can trigger both selection and department creation: First the highlighted match is selected; for a saved project, this requests the department change. After that, the additional keyboard handler requests the last accepted search name as a new department. The later acceptance of the cleared search does not prevent this request. Unlike with project type, there is no check for an already existing entry with the same name before creation. A search prefix or text cached after selection/clearing can also become an unwanted new department. Do not press Enter multiple times.

For an existing department, click the match and then click another field. Tab closes the list without selecting the highlighted match and without creating a department of its own. For a truly new department, type the full name again, check existing entries, and use Enter once. If Multiple departments in use replaces the picker, that combined selection does not happen here.

For a saved project, selection alone already triggers its own change. If a successful creation response also arrives, its department is selected and a project change is requested again. These are separate processes, not an atomic action; the order of responses and write processing is not guaranteed. A failed second change does not roll back a department that has already been created. For new projects, the project assignment initially remains local, but the new department master record may still already have been saved.

The × and Backspace with an empty search can clear the assignment, but they do not delete a department master record. For a saved project, a change request follows immediately after that as well. After error messages or rapid changes, reopen and check the saved project and role state again. Archived or waiting projects disable these pickers; a mere editing overlay, by contrast, is not reliable keyboard or server-side rights protection.

Project planning: open locations and roles

After saving the base data, you go to step 2 for project planning. For an existing project, you can also switch from the base data to step 2. The planning shows the locations and days saved for the project; you add a role within the desired location. Creating, selecting, or changing a location is done in step 1, not via a new location dialog in this planning view. Use Back for that and the location controls described above; note the separate saving and change sequences there.

Click the location name to expand or collapse its area. The arrow next to a role expands or collapses its shifts. Expand all and Collapse all apply to locations and roles together. This changes the display, not the saved roles. Expanding or collapsing an individual item does not reliably update the state of the master toggle.

For customer users, the role list may be restricted by the assigned departments. Roles without a department appear only with the appropriate access. A visible location without roles is therefore not proof that no role has been saved there yet. Check missing roles with your administration before creating them again. Access to Self Service is not the same as editing rights for every project. A grayed-out area is also not a reliable statement about keyboard operation or all server-side rights. If editing is blocked or unclear, do not continue changing things through other routes.

Create a new role at the correct location

  1. Expand the desired location and select Add new role there.
  2. Enter a name under role name. A name is required; spaces alone are not enough. When creating a new one, the name of the current language is used first, then English, German, French, or Italian. Tabs are available for additional language versions. The Role Description is not an additional required field for creation.
  3. Check cost center and department. A manually created new role starts with these values from the project base data. They are not required values for this name check.
  4. Click Save once and, if applicable, note the follow-up questions described below.

Name error after Yes: If, when creating a new item, you confirm the offered transfer of cost center or department to the project with Yes, those project changes are requested before the name check. If the name used consists only of spaces, no role creation is requested and the dialog remains open. The name error message therefore does not mean that the project base data remained unchanged. First check the saved state of cost center and department in the project base data, or have it checked, instead of blindly repeating Save and Yes. The initiated requests alone do not prove successful saving.

Creation is requested immediately, not only with Next and not via the local base-data autosave. In the loaded location, the interface prevents an existing name spelled exactly the same way. This is not a general duplicate check: differences in uppercase/lowercase, spaces, hidden roles, or two creations still running can bypass this check.

The new role also comes with a first shift from 08:00 to 16:00; the break is determined server-side from the matching settings. The new role starts without a set employee filter. Then check shifts, staffing requirements, and other role details separately: creating the role is neither finished planning nor publication nor staff assignment.

The dialog closes after creation has been started, before a successful response is required. Its disappearance is not a saving confirmation. If there is an error or the response is unclear, first reopen the saved state or have it checked instead of saving again. Late responses can still affect a role that has since been opened differently, including its local additional details.

Edit role name and discard changes

Use Edit on the desired role; the hint for it reads Change role name. In the dialog that opens, check the language tabs and the role values. Save requests the change immediately. When editing, the German name takes precedence, then English, French, and Italian — unlike when creating a new one. The display may still show the version in your current language. Therefore, do not check only the name that is currently visible.

Cancel or the close icon does not itself trigger a role save request. However, that is not a complete reset: cost center and department are changed on the role object already shown when editing; such local values can remain after closing. Any department creations or other requests already started are not undone by this. If in doubt, reopen the saved project state.

Even when saving, the dialog closes before the response arrives. An error response does not reliably reset values that have already been changed locally. The role description is sent along in the language data, while the separate description field is not reset in the same way during this edit. Therefore, do not rely only on the local display as proof of every later description display.

Cost center and department: selection and follow-up questions

For cost center, you can enter text or click an offered entry. The suggestions are filtered based on the entered text. The selection changes the cost center text here; it does not automatically reset the internal reference to another saved cost center. Check the assignment after saving if you switch between saved cost centers.

Select an existing department preferably by mouse click. This role list loads the project customer's departments and is not the same restricted list as in the project master data. A selection can therefore, after reloading, cause the role to no longer be visible for your user. Clearing it initially removes only the role assignment, not a department master record.

Enter is not a harmless selection confirmation here: In addition to the selection component, a department creation is linked to a cached search text. This can request a separate master record even before the role is saved; if the response is successful, the new department is assigned to the currently open role object. Avoid Enter to confirm existing matches. If an unintended creation occurs or a response arrives late, check the state instead of confirming repeatedly. A reliable keyboard-based new creation is not assumed for this dialog here.

When saving, the follow-up questions differ:

  • New creation without already loaded roles or editing of the only loaded role: If cost center or department differs from the project, the transfer to the project is offered. Yes first requests the corresponding project changes and then continues saving the role, without waiting for the project responses. No also continues saving the role, but without these explicitly offered project requests; during new creation, the name is still checked.
  • Additional new creation or editing with multiple loaded roles: Before values differ for the first time, another warning can appear. This also applies to an additional role when exactly one role is already loaded. Yes continues the role creation/change; No does not start a role request in this confirmation branch. Already changed local values are not reverted by this.

Partial change despite an open role dialog: When the offered project transfer is accepted, Yes starts the requests for a changed project cost center and then for a changed project department before the name check of the new role. If the name consists only of spaces, no role creation is requested; the dialog remains open. In that case, first check the project master data instead of blindly repeating Save and Yes. Neither the name error message nor the open dialog proves that the master data is untouched; conversely, requests already started are not confirmation of successful saving.

The number refers to the loaded roles; a list restricted by departments may hide other roles. A No response also does not mean that the project values remain unchanged permanently: when the role is saved server-side, the project department can be carried over automatically or cleared. The same applies to the cost center text when roles are changed. Empty cost centers and missing departments are omitted when determining common values. After that, check both roles and master data; there is no guaranteed shared transaction or rollback of all partial changes here.

Load a role template

If load from template is available at the location, the list of role templates opens there. First select the correct location. Search for the template name in the dialog; the search filters the loaded list case-insensitively. Clicking a list entry already starts creation – there is no additional apply button beforehand and no separate confirmation. Closing without selecting does not start this creation.

In Self-Service, the list is focused on the project customer's role templates; the switch to other customer templates is not shown here. An empty list after a load error does not prove that no templates exist. Late list responses can replace a newer search or list.

A single loaded role template does not transfer either cost center or department, not even as a fallback from the project master data. Check and add this information afterwards on the new role. Template creation does not use the local same-name check of manual new creation; repeated clicks can request additional creations.

Role and shifts are requested first. Wages, expenses, clothing requirements, and, if applicable, a tariff group are transferred in further requests. Closing the dialog does not prove the success of all these transfers; in particular, not all partial responses are awaited together, and even a tariff group error can close the dialog. Check the result and do not simply repeat the entire import if the status is unclear. The detailed operation of these follow-up screens is not part of this basic role guide.

Do not confuse project template and role template

When starting from a project template, the included roles are created individually when switching to planning. This is an additional step after saving the project master data, not just a display of the template. After the role sequence, planning is reloaded. Until then, intermediate states may be visible; do not reload again too early or apply the same template a second time.

For these embedded roles, different default values apply than for a single role template: cost center references can come from the embedded role content, or alternatively from the new project. If the cost center has been explicitly changed for the transfer, these new values are used. The role department, by contrast, comes from the current project department, not from an unchanged role-specific copied template department. The previously described transfer of the project master data remains separate from this. This process also does not wait for every additional wage/expense/clothing request; it guarantees neither a complete shared transfer nor protection against repeated application.

Back, step changes, and continue in planning

Back and the numbered steps are navigation, not undoing already saved roles. This planning has no additional local master-data autosave when leaving. Wait while requests are running and then check the saved state.

Continue does not publish the project yet. If editing is available, role data is requested again first and missing data is checked. A confirmation can allow the transition to step 3; No in the warning dialog does not continue in this branch. Which missing wage/expense details are reported also depends on whether you are allowed to edit them. Without the edit availability reported by the planning call, Continue instead goes directly to staff assignment. The numbered links do not perform the same checks as Continue.

This guide covers entry, location sections, manual role master data, and the template sequences described. Editing shifts and staffing requirements, copying/deleting roles, wages, expenses, criteria, documents, automatic translation, and publication are separate screens; their full operation is not assumed here.

Department in the role dialog: selection and Enter

Select an existing department if possible by clicking the matching list entry. The cross in the selection field initially removes only the assignment in the open role object; the role change is only requested via Save. For an existing role, this local change can remain visible even after Cancel.

Enter is not just a selection confirmation here. If you have entered search text, Enter can additionally create a new customer department immediately – even if an existing department is selected at the same time. Avoid Enter if you only want to select an existing entry. Even after selecting with the mouse or clearing the field, Enter can still use the last search text entered by keyboard for creation. Tab does not start a department creation in this field.

For a new department, enter a unique name and press Enter only once. Creation is requested immediately, without any further prompt and regardless of later saving the role. After a successful response, the new department is selected in the currently open role object. Cancel or closing the role dialog does not undo an already created customer department. The cost center/department follow-up questions when saving the role are a different process.

Do not use empty names or names consisting only of spaces, and use no more than 255 characters. The input itself does not prevent all invalid names. If no response arrives or the expected selection does not appear, first check the department list or the saved state instead of repeating Enter. There is no reliable protection here against multiple requests or identical names. Do not switch to another role during creation: a late response can change the selection in the role dialog that is open in the meantime.

Edit role description and language register

Open the desired role via Edit and select the language tab English, Deutsch, Français or Italiano. When opening, the tab follows your saved interface language; still check the active tab, especially after a previous dialog. Changing the tab does not save anything and does not translate texts automatically.

Enter the name and description for each language. The description is optional. The link tool is available for links; inserted web addresses can also become links when pasted or when you leave the editor. In the link window, Enter confirms the link and Escape discards this link edit – neither is saving the role.

Keep the description short: the visible editor checks at most 500 text characters, not the length of formatting. Some characters, such as emojis, count multiple times. If the limit is exceeded, the text can revert to the last accepted content; without such content, it can become empty. Check the result after inserting, deleting, and translating. The check is not a reliable safeguard for texts in inactive registers or automatically transferred translations. After a previous dialog, even an earlier accepted text can reappear; do not rely on a reset description still belonging to the current role.

For a new role, the general label and description come from the same language: first from your interface language if a name exists there, otherwise from English, German, French, or Italian. A description alone does not determine this selection. For an existing role, the general label is taken when saving first from German, then English, French, or Italian. The changed descriptions are passed along as language texts; the separate general description is not updated again from the edited language register when saving. After saving, check the needed language views instead of only a single display.

Finish with Save and observe the cost center/department follow-up questions described earlier. Cancel discards the unsaved language texts in the dialog, but it is not a complete reset of the displayed role object: simply opening it can already switch its general label and description to the matching language. Even a closed window or a locally changed display does not yet confirm successful saving.

Translate name and description into a language register

First choose the target register and then the button with the magic wand. It appears when a name or description exists in another language. The translation applies only to the name and description of this role in the selected target language – not to cost center, department, shifts, other roles, or all languages at once. For this purpose, the text is sent to a translation service; before triggering it, check which content you want to translate.

The source language is chosen jointly for both fields: the first other language with content in the order English, German, French, Italian. This does not necessarily have to be your interface language or the last edited tab. For example, if only the English name is filled in, a French description is not additionally searched for as a second source. A field that is empty in the source language leaves the corresponding target field unchanged.

Existing target texts can be overwritten without prompting. Back up any wording you need before clicking. Wait for both results and check the name and description separately. One field can be translated successfully while the other fails. A button that can be clicked again does not prove that all responses have arrived.

Do not edit target texts in the meantime, do not restart immediately, and if possible do not open another role. Late responses can overwrite your own changes or texts in a role dialog that has since been opened. Changing tabs, Cancel, or closing does not reliably stop ongoing translations. After an error, check the current content; there is no shared rollback for both fields.

Translating alone does not save the role. Also check text length and links, and save the role only after your review. The additions here apply only to this role dialog; other planning functions and other editors are not fully described by this.

Copy a role to one or more locations

Open the desired project in Self-Service and the planning step. Expand the location and the relevant role. On the right in the role row is the copy icon with the hint copy role. The location selection appears only when the premium feature is enabled and the planning is not treated as archived or locked. The greyed-out editing area is not reliable proof of a complete keyboard or permission lock; if you lack editing rights, have the project managers perform the action.

  1. Open copy role and tick one or more of the offered project locations. The original location is also a valid target: this duplicates the role at the same place. You do not create a new location here.
  2. Check the boxes and click apply once. This immediately starts a separate copy for each target location, without an additional yes/no prompt and without later shared project saving. The selection is then cleared and closed.
  3. Wait for the new roles and check each copy. At the same location, the name suffix starts with copy; if there are name conflicts, copy 1, copy 2, and so on follow. At another location, the name initially remains unchanged. Existing language labels are checked separately for conflicts; the visible language name and the general name can therefore receive different suffixes.

Setting only checkmarks saves nothing yet. Closing without apply does not copy, but it keeps the checkmarks for reopening. Therefore, explicitly remove targets you no longer want. An empty selection with apply does not create a copy in this single role action.

Do not click repeatedly if a copy does not appear. Names are checked only against the target roles already loaded; ongoing copies do not reserve a name. Parallel calls can therefore create identical names. Multiple targets do not form a shared all-or-nothing action. On errors, part of it may already have been created without this action showing its own helpful error message. After the pending responses have finished, reopen planning and check the target locations before starting another attempt.

Copy all loaded roles from a location

On the right in the location row, not in the role row, copy all roles opens the target selection. In this Self-Service planning, at least one loaded role at the source location is sufficient. You do not need two roles. Premium activation, planning status, and the editing area apply as with copying a single role.

  1. Open the location action and tick one or more other project locations. The source location is not offered here. If there is no other location, there is no copy target.
  2. First check which roles are actually loaded at the source location. Depending on their department assignment, customer users may only see part of the project roles. All here means these loaded roles, not necessarily all roles in the project. The checkmarks from Edit multiple roles do not limit this action.
  3. Click apply once in the selection window. This label remains in English here. A separate copy request is started for each combination of loaded source role and selected target; there is no additional confirmation.

Before apply, select at least one target. Unlike the single-role action, this bulk path does not reliably treat an untouched selection as an empty list. After apply, the window and its checkboxes are also not explicitly reset as they are in the single copy. Close it yourself afterwards and check the targets; apply again may request further copies. The same applies here: no shared undo for all copies, no reservation of names, and if the result is unclear, reload first instead of copying repeatedly.

What happens to shifts and staffing requirements when you copy a role

A role copy is not a complete copy of the staffing. Before continuing with planning, check in particular:

  • Shifts and breaks: The existing shift times, break duration, split breaks, as well as shift names and language texts, are created as new shifts. The copy is a new role with new shift records, not a move of the original role. The associated days are based on the project dates and the target location; no new project days are created here.
  • Staffing requirement and people: Newly created staffing requirement starts at 0, not with the quantity of the source role. Days without a matching date at the target location are not active. Personal assignments and invitations are not transferred to the copy. Therefore check the quantities and plan the staffing of the new role separately. The process reconciles staffing requirement and assignment slots across the whole project. If there are excess assignment slots, this reconciliation can also remove existing assignments and related deployment, time, and billing data from other roles. Not every copy leads to such deletions. Therefore clarify any unexplained discrepancies in quantities or staffing with the project owners before copying.
  • Role content: Cost center text and cost center reference, as well as document references, are copied over. Existing salary details, expenses, and clothing regulations are transferred through separate copy steps; check these after loading instead of treating the copy as already fully verified. The documents are the same references, not a new upload.
  • Fields not fully transferred: Employee filter, role department, and pay group are not transferred by this copy action as existing settings. The general role description is also not sent along, but its language texts are. The copy shown immediately may still display the source role's filter, pay group, or general description. Do not rely on that: reopen the planning after the responses and check these settings explicitly. A copy without a department can disappear from the visible role list for a customer user when reloading; in that case, have an authorized person check the department assignment instead of copying again blindly.

The project department can also be derived anew from the existing role departments when the copy is created. Empty role departments do not count as their own department. Therefore also check the project's basic data if departments are relevant to your planning. A later error does not guarantee that the already created role or shifts will be undone; always check the actual status before trying again.

Copied clothing images use the same stored image reference. The copy is not an independent image backup. If a role involved is deleted later, a deletion attempt is made for an image file. However, upload and display use different storage paths from the deletion routine; it is not proven whether this causes the displayed image of the other role to disappear. This also does not guarantee safety for all older storage states. Secure any needed images before deletion and then check the remaining role.

Delete a role with its shifts

Open Self-Service → Projects → desired project → Planning, expand the location, and look for the Delete icon on the right in the relevant role row. This deletes the entire role, not just a single shift entry and not merely a reduction in staffing requirement.

  1. Beforehand, check all shifts, staffing requirements, requests, and people already assigned to this role. If there are ongoing assignments, clarify the procedure with the project owners first.
  2. Click Delete. The confirmation prompt reads Are you sure you want to delete this role? With no, no role deletion is started. With yes, the deletion request begins immediately; later saving the project is not necessary.
  3. Wait for the response. Only then does the interface remove the role from its list. Afterwards, reopen the planning to check whether the role and related data were actually removed as expected.

The confirmation covers more than the role name. The deletion path removes the role's shifts, their staffing requirements, assignments and related requests, as well as role notifications, salary details, expenses, and clothing regulations. It does not replace a cancellation agreed with employees; deletion does not imply confirmed delivery of a notification.

A request with internal status completed on a shift blocks deletion with the English message Cannot delete, you have a contract with at least one employee to work on this role! This does not mean that every other already assigned or accepted request is automatically protected. The check is done shift by shift: if the blocking request is only found on a later shift, data from earlier shifts may already have been removed. An error therefore does not reliably mean "nothing changed." If there is a block or the outcome is unclear, do not delete again; instead reload and check the actual status with the project owners.

If exactly one loaded role remains in the project after a successful response, the interface copies its cost center into the project basic data and separately requests that it be saved, without any further prompt. Other roles may still exist because of department filters; this separate saving can also fail due to missing permissions even though the role has already been deleted. Therefore check the project cost center after reloading. The role deletion itself has no separate error callback here, and repeated confirmation or parallel changes to the role list are not reliably intercepted. Wait for completion and avoid further role actions in the meantime.

For previously copied clothing images, the remaining role copy is not an independent image backup: it uses the same stored image reference. The role deletion triggers a deletion attempt for an image file. However, upload and display use different storage paths from the deletion routine; an effect on the displayed image of the other role is therefore not proven. A general harmlessness for older storage states is also not proven. Secure such images beforehand and then check the remaining role.

Create a shift in Self-Service planning

In Self-Service, open the project and step 2 – Planning. Expand the appropriate location and role. Under the role, you will find Add New Shift. The shift belongs to this role; the date columns come from the project locations and dates. You do not select a single date when creating it. The visible roles may be limited by your customer departments.

  1. Beforehand, check the role, location, and project data. Click once on Add New Shift. This creates the shift immediately, without any additional save or cancel dialog. Continue is not required for this.
  2. Wait until the new row appears. For the first loaded shift of the role, 08:00–16:00 is preset. If shifts already exist, the start and end are initially set to the end of the last loaded shift. Matching times are therefore not yet a fully planned assignment.
  3. Check the times, break time, and every required date column. Newly created staffing requirement fields start at 0; existing staffing quantities in the project are not generally reset. Only dates that belong to this location are intended as active staffing fields. A new shift does not assign a person yet and does not send an invitation through this action.

The initial break time is determined from the shift duration: in Self-Service, a matching customer break rule takes precedence. If no customer rule matches this duration, the agency rules apply; without a matching calculation, 0 may result. Do not assume a fixed standard break.

Clarify any unexplained quantity/staffing discrepancies in the project before creating it: this action also reconciles assignment slots across the whole project. If there are excess slots, assignments as well as deployment, time, and billing data from other roles can be removed. This does not necessarily happen with every creation, but it is not solely a local change to the new row.

If there is no response or the response is unclear, do not click multiple times. Ongoing creations are not blocked against each other and can create additional shifts. Wait for the response, reload the planning, and check location, role, and shift inventory before acting again. If you lack edit permissions or the planning is locked, have the project owners make the change; greyed-out areas alone do not prove a complete keyboard lockout.

Change times and simple break time

Open Self-Service → Project → 2 – Planning, expand the location and role, and find the shift row. On the left, start and end are shown in the format HH:MM, next to break time in minutes. These times belong to the shift and therefore apply to its staffing needs across multiple project days, not just to a single date column.

  1. Enter a complete time from 00:00 to 23:59. The full entry is checked, but it does not save on its own yet. When leaving the time field or pressing Enter, the break is recalculated and the shift is then saved. Enter can trigger this without leaving the time field; both actions can also save with unchanged valid values. Repeated Enter presses and then leaving the field can start additional calculations and saves.
  2. An incomplete or invalid entry, such as 10:__ or 24:00, is rejected with "Invalid time. Please enter a time in the format HH:MM (00:00 - 23:59)." The field is reset to the value it had when you entered it. If another save was already open at that time, this reset is not proof of the last saved server value.
  3. For a night shift, you can use 22:00–06:00, for example; an earlier end is treated as ending after midnight. When changing it, such a span is rejected if it exceeds 23 hours. Identical start and end times are treated as a duration of 0 for break calculation, not automatically as 24 hours. Check the desired period yourself.
  4. For a simple break without split breaks, enter the minutes in the break time field and leave the field. This starts saving immediately, without a shared save button. The field allows up to three characters, but it does not provide reliable validation of whole, non-negative minutes or a duration suitable for the shift. Use sensible whole minutes and check after reloading. If split breaks are stored, this simple field is disabled; their separate operation is not described here.

Time changes recalculate the break again. A break entered manually beforehand can therefore be replaced. Do not change start, end, and break in quick succession: calculations and save responses are not protected against delayed responses. An older break calculation can be saved together with the times that have since been entered. If the result is unclear, wait for all responses first, then reload and check the three values together.

For certain assignments that are already in progress or being edited, the server rejects a time change. This includes existing clock-ins and assignments with validated, in-progress, or completed time editing; for confirmed or self-booked assignments, an additional date/time-based pre-start lock applies. The message is "The times for this shift cannot be changed because at least one of the assignments for this shift has already started." Start, end, and break are then reset to the values returned. This lock is checked when times are changed; it is not an equivalent promise for a pure break change. Clarify such corrections with the project owners instead of trying to bypass the lock.

When saving the break directly, "Shift could not be changed. Please try again!" may appear; the local input is not automatically reset. Even if there is no response after a time change, do not assume the save was successful. Reload first and check the actual status. A successful time change is also not proof that all affected people were notified. Coordinate relevant changes separately.

Enter the staffing requirement per shift and date

Go to Self-Service → Project → 2 – Planning, expand the location and role, and find the appropriate date column to the right of the desired shift. The number field is the regular staffing requirement; a separately displayed overbooking next to it is not part of the visible field value. Dates that are not active at the location are disabled. Therefore first check the shift, date, and location.

Each entry starts its own save immediately, not only when leaving the field or by using Next. There is no cancel dialog here and no shared final save. Even temporary clearing while replacing a number is transmitted as regular staffing requirement 0. Therefore replace quantities deliberately and wait for the response before changing anything else.

Enter a sensible whole, non-negative number of people. The number field and the bound save path do not guarantee full validation of whole numbers and sensible upper limits. Do not use negative or decimal entries as a supported type of staffing requirement. The saved total value includes regular staffing requirement plus existing overbooking; this is not a personal commitment or automatic staffing. The separate overbooking control is not described here.

If you reduce the staffing requirement below the already assigned slots, the application can keep the total staffing requirement and show the difference as overbooking. Example with previously 5 regular slots, no overbooking, and 4 assigned slots: a new regular staffing requirement of 1 can come back as 1 regular + 3 overbooked. Therefore always check both displays and the staffing. 0 in the regular field does not necessarily mean total staffing requirement 0 when there is existing overbooking or assignment.

If the total staffing requirement actually reaches 0, open invitations with status pending are quietly removed in the corresponding save branch. This is neither a personal cancellation notification nor the same action as closing an assignment. A later increase does not automatically restore the removed invitations; check the invitation list afterwards.

Clarify any unresolved assignments and time/billing data before changing quantities. The subsequent slot reconciliation affects the whole project. If there are excess assignment slots, it can also remove assignments and assignment, time, and billing data from other roles. The overbooking adjustment described here is therefore not a general guarantee that all data will remain unchanged.

With "The number of employees could not be changed. Please try again!", the local entry may remain visible. Even rapid successive changes are not reliably confirmed by the last visible response: an older response can overwrite the new display; numeric zero values from a response are not always adopted. Wait for open responses, reload, and check regular staffing requirement, overbooking, and people together before entering anything again. If values conflict, involve the project owners.

Remove a single shift

Open Self-Service → Project → 2 – Planning, expand the location and role, and look for the delete icon with the label Delete on the right in the shift row. Do not confuse it with the delete icon for the entire role. Here you remove the shift with its staffing requirements across the associated project days, not just a single staffing requirement on one date.

  1. Beforehand, check the affected dates, invitations, assignments, and already recorded times. Coordinate any necessary cancellations separately.
  2. Click the shift delete icon. The prompt reads "Are you sure you want to delete this shift?". No does not trigger deletion; Yes requests deletion immediately. Later shared project saving is not necessary.
  3. Wait for the response and, after reloading, check the correct role. If successful, the shift, its staffing requirements, and assignments are removed; related requests are deleted. This does not imply confirmed notification of the affected people or guaranteed complete cleanup of all dependent time/billing data.

The message "A shift with invitations cannot be deleted!" is worded more broadly than the checked lock: this single action blocks on related requests with status completed or auto-accepted, not generally on every existing invitation. Therefore, a missing lock does not mean the shift is unstaffed or can be deleted without consequences. If deletion is refused, do not first remove invitations just to bypass the lock; clarify the assignment with the project owners.

Do not click Yes multiple times and do not change the affected shift list while the response is open. After a successful response, the display removes a previously remembered row position; if the list has since been reordered, the wrong row may be removed temporarily. If there is an error, an unclear response, or an unexpected display, reload first and check what actually exists. The action is not intended when planning is locked and requires appropriate Self-Service edit rights at the shift endpoint; this is not a general security approval for all planning actions.

Edit overbookings for a shift and a day

  1. Open Self-Service → Project → Step 2 (Planning) and expand the relevant location and role. Find the shift row and the date column. Next to the regular staffing requirement there is +, and for positive overbooking its number. The label is Add overbooking or Edit overbooking. The entry point appears only for the matching active staffing requirement once its loading process is complete.
  2. Click this symbol and change Number of overbookings. This means additional places on top of the regular requirement, not a new regular staffing requirement number. Example: with 5 regular places and 2 overbookings, a total of 7 places are planned. Changing to 3 overbookings results in a total of 8 places if the regular requirement stays the same.
  3. Click Save to send the change immediately. The dialog closes before the response arrives. A later Next or shared project save is not required for this. Afterward, check both the regular requirement and the overbooking, as well as the assigned people for exactly this shift and this day.

Typing is not yet saving: Entering a value and leaving the number field first only changes the dialog value. Enter in the number field is not a save command here; use Save. Cancel or the close symbol at the top closes without saving a new overbooking. When reopened, the then current value of the staffing requirement cell is taken over. Escape and clicking outside do not replace the close symbol in this dialog. Cancel does not undo a saving that has already been sent.

Enter valid quantities deliberately: Use a non-negative whole number; 0 removes the additional overbooking, not the regular requirement automatically. This is an operating recommendation, not a guaranteed quantity check. An emptied field is not treated as “keep the old number”: saving sends an empty overbooking value, while the total amount is recalculated. Negative numbers or decimal values are also not reliably caught in the save handler. Do not save such values. If the total amount is unexpected, reload first and check both quantities; already loaded values and responses are not consistently converted to numbers.

People already assigned can prevent a reduction: If you reduce the overbooking and the new total would be smaller than the number of assignments with a status other than “unassigned”, this branch does not take over the new quantities, but returns the previous ones. Example: 5 regular places plus 2 overbookings, already 6 assigned → setting overbooking to 0 would result in 5 in total; this reduction branch therefore keeps the previous 7/2. It still performs the project-wide quantity reconciliation. The dialog may be closed without a special rejection message; that alone does not confirm the new quantity. The behavior differs from a reduction in the regular requirement field, which can absorb assigned places by increasing the overbooking.

Check project-wide effects in advance: This save also reconciles assignment places across the entire project, not just in the opened cell. If the requirement and assignment quantities conflict, other roles may also be affected. Depending on the branch, excess assignments and related time, expense, and billing data may be removed; there is no general promise of retention or undo here. Clarify such discrepancies with the responsible person before changing quantities. The overbooking number alone is neither a personal assignment nor a confirmed commitment.

If, in the normal save branch, a total amount of 0 with overbooking 0 is actually saved, then pending invitations with status “pending” for this requirement are removed afterward and project counters are recalculated. Simply setting the overbooking to 0 is not enough if the regular requirement remains positive. This is not a guaranteed personal cancellation notice and not a general closing of the shift. A later increase does not automatically restore the removed invitations.

In case of errors or rapid follow-up changes: The message The number of employees could not be changed. Please try again! does not reset the local quantities and does not reopen the dialog. Repeated saving can trigger additional operations, even without changing the value. An older response can overwrite a newer display; a numeric zero in the response is also handled differently from the string “0”. This describes possible response constellations, not the proven data type of your system. While the dialog is open, responses can also change the underlying requirement; saving then recalculates from this now current requirement and the dialog value. Wait for feedback, reload in a controlled way if the result is unclear, and check quantities and people before changing anything again.

Observe archiving and permissions: A locked planning is not an approved editing path. The quantity field in the dialog is disabled for archived projects; however, this does not imply a general lock guarantee for every button, keyboard action, or server request. Do not try to bypass a lock; instead clarify the editing authorization. This guide concerns overbookings only; split breaks as well as shift names and languages are not validated here.

Split breaks: open the dialog and edit time ranges

Open your project and its planning in Self-Service. At the relevant location, find the desired role and shift. Next to the break duration field, click the small break button. The dialog is called "Split shift - break(s)". It first loads the existing breaks for this shift. The shift belongs to the role, not just to a single day cell: therefore also check the affected assignment days. Depending on customer access and department filter, you may only see part of the roles.

Add creates an empty row. Enter the break start on the left and the break end on the right in HH:MM format, for example 12:00 – 12:30. This means the break between work segments, not an additional work block. Use the remove button on the right to take a row out of the dialog. Adding, entering, and removing do not send a save request on their own yet. The Add button is disabled when four rows already exist and for archived projects; this is not a general server-side limitation or security assurance.

Enter in the break time field does not save. Complete entries and leaving a time field trigger its time validation; Enter also calls this check, without necessarily moving the focus on. Invalid or incomplete times may be cleared. Check both fields again before saving. This is a different process from directly editing the shift start and shift end time outside this dialog.

Cancel and the dialog’s own close button at the top do not save the current dialog changes. When reopened, the breaks are loaded again. However, they do not undo a save that has already been started. Escape is not a reliable way to close the dialog: in the time field it can reset the entry there; the dialog itself is not set up to close via Escape or clicking outside. Use the visible buttons.

Saving split breaks: time frame, night, and total break

All breaks need a start and an end and must lie within the shift. A break’s end must be later than its start. Breaks must not overlap; directly adjacent time ranges are not rejected as overlaps. For a shift that crosses midnight, times after midnight are assigned to the following day, for example a break 23:30 – 00:30 within a 22:00 – 06:00 shift. The dialog check treats identical start and end times for the entire shift as a day change, not as an empty time span. Do not use this special case as a substitute for a substantive check of your shift duration.

Click Save only after checking. The breaks list is sent immediately for the shift; Next or saving the entire project later is not required for this. Missing times, an unsuitable time frame, or overlaps prevent the request in the checked dialog flow. The hints may appear in English, for example „Split shifts must not overlap.“. Correct the affected rows and only then save again. The input form and these checks are not complete server-side validation and not an approval under labor law.

After the response to the breaks list, the entire shift is additionally saved with a calculated total break. The dialog closes and reports „Split shift saved!“ without waiting for the response to this second save. The message therefore does not confirm that both steps completed successfully. After reloading in a controlled way, open the shift again and check both the break times and the total break duration.

Important for night breaks and when removing all rows: The subsequent summation only takes into account breaks whose end time is later than their start time. A break that runs past midnight can pass the time-frame check, but be missing from this sum. If the calculated sum is zero or the list is empty, the previous total break duration is retained instead of being automatically set to zero. In a mixed case, only the same-day part can become part of the total break. Do not rely solely on the checkmark or the success message here. If there are discrepancies, clarify them with your responsible planner before further mission or time processing.

As long as the loaded shift contains break rows, the simple break-duration field next to it is disabled. After all rows have been removed and saved, it becomes available again; check and correct the remaining total break separately if needed. The tooltip when hovering over the break button shows the resulting work segments, not simply the list of break times. It uses the local state and is not a fresh fetch or a reliable proof of the correct night order.

Split breaks: errors, parallel changes, and follow-up data

Do not save an unexpectedly empty list right away. Even after a loading error, the dialog may appear empty. Saving an empty list removes the previous break entries for this shift. Close the dialog, reload in a controlled way, and check the previous state before confirming changes. When saving, the transmitted list is reconciled: missing previous rows are removed. In case of errors, no reliable joint rollback of the breaks list and the subsequent shift save is documented.

Edit only one break dialog at a time if possible and wait for ongoing requests to finish. Repeated saving is not prevented as a duplicate request. If you open another shift before a response arrives, an older loading response can overwrite that dialog’s list. An older save response can locally change the shift that is now selected, trigger another shift save for it, and close the newer dialog. Cancel also does not stop older requests. If the display is delayed or contradictory, do not click Save repeatedly; instead reload in a controlled way after completion and check all shifts that were edited in the meantime.

If the dialog remains open after saving or an error message appears, check the state before trying again. The dialog does not always show loading and saving errors itself; a general error message may also appear. Even a closed dialog is not complete proof of success. The follow-up save sends the entire local shift, not just its break duration. Therefore be especially careful if shift times or other shift data were changed in the meantime.

Break planning does not replace correction of already recorded working times, wages, or expenses. No automatic complete follow-up of such data is evidenced from this save path. For assignments already carried out, check the time and billing data separately with the responsible office. The permission check of the subsequent shift save must also not be understood as a guarantee of protection for the preceding break fetch or break write. Use only the project access intended for you; greyed-out interfaces are not a comprehensive security clearance.

This guide concerns only the Self-Service planning’s own break dialog. Shift names, language editing, and other planning dialogs are not covered by this.