decídalo
Documentation
Ask AI
Search Results for

    Show/Hide Table of Contents

    Workflows

    This article explains the concept of booking workflows in the resource management process. It shows how to manage and configure booking workflows in decídalo and defines the involved roles and approvals.

    Bookings and Booking Statuses

    A booking in decídalo is used to allocate capacity or time of a person (resource) to a project, customer or activity. Bookings are created when a resource is staffed to a project or a resource request, which is a resource demand in general.

    Decídalo distinguishes three statuses for bookings:

    • Soft: provisional booking that does not affect availability. This is typically used when the demand is not confirmed, i.e. for opportunities. If your company lets the booking workflow start on soft bookings, a soft booking triggers the approval workflow instead of a reserved one (see Workflow start status).

    • Reserved: a temporary status that is set when waiting for the booking to be confirmed. This status impacts availability. It triggers an approval workflow, if configured.

    • Confirmed: the final status after the booking was approved.

    • Rejected: the approval request for a booking was rejected. This is largely equivalent to removing the booking, except that the rejected booking is kept for auditing and analysis purposes. It does not affect availability and is hidden on the user frontend.

    Since bookings can impact availability and define what the person will be working on, booking someone requires specific permissions. In decídalo booking permissions can be configured by booking status. Everyone may be allowed to soft-book or reserve candidates, but not to create confirmed bookings.

    In larger organizations the user having the resource demand, often someone in the sales organization, typically does not have the permission to create confirmed bookings for resources. They need to request candidates (typically from the delivery organization) by reserving them (creating a reserved booking) or via a resource request.

    On a resource request, a candidate can carry both a suggestion status (suggested, approved or rejected) and a booking. To make conflicting situations easy to spot, the Candidates tab shows a warning icon in the Suggestion column whenever the two no longer match. Hover the icon to see the explanation. The warning appears when:

    • the suggestion was rejected but the candidate still has a confirmed booking, or
    • the suggestion is not rejected while its booking has been rejected.

    Note: The warning is only an indicator that highlights the inconsistency; it does not change the suggestion or the booking. Resolve it by updating whichever of the two no longer reflects the intended decision.

    Position Status

    Besides its booking status, a booking can carry a position status. It says whether the position the booking is for is already won (Confirmed) or still an opportunity (Unconfirmed). This lets you book candidates early for an opportunity without blocking their capacity before the deal is closed.

    The position status is only used while the Position status data field of bookings is active. It is inactive by default, and an administrator activates it with the Active toggle under Administration > Data fields > Booking (see Customizing data fields). While the field is inactive, it is hidden in the application and none of the rules below apply.

    While the field is active:

    • New bookings start on an unconfirmed position. The booking dialogs preselect the position status the booking will get: Unconfirmed for a new booking or a new position, the position's own status when you staff an open position, the status of the position a team booking was staffed from when you distribute it to its members (Unconfirmed for a team booking added directly), and for a resource request the status of its open position or of the booking that is copied. If you may create neither soft nor rejected bookings, the dialogs that book a person preselect Confirmed instead.
    • A booking of a person on an unconfirmed position can only be soft or rejected, so each of the two fields only offers what fits the other. On an unconfirmed position the booking status offers soft and rejected, and next to a reserved or confirmed booking the position status only offers Confirmed. To reserve a booking on an unconfirmed position, confirm the position first; to unconfirm the position of a reserved booking, make it soft first.
      • In the dialogs that book a person, the position status only offers Unconfirmed if you may create soft or rejected bookings.
    • Open positions are exempt and can stay reserved on an unconfirmed position, because they block nobody's capacity, so both fields offer every value. A team booking ignores the position status: it shows none, and the team booking workflow does not wait for it. The restriction applies as soon as a person is assigned, including when a team booking is distributed to its members, where you choose the position status of their bookings.
    • A booking that is already reserved or confirmed on an unconfirmed position can still move between reserved and confirmed. This only happens when the field was deactivated and activated again, and such a booking's position status has lost its meaning.
    • Approving a booking in a booking workflow is not affected. If the workflow starts on soft bookings, the approval waits until the position is confirmed (see Approval while the position is unconfirmed).
    • Setting the position status of a booking back to Unconfirmed removes the approvals given for it so far. Its approvers are asked again once the booking is back in the workflow: as soon as the position is confirmed again if the workflow starts on soft bookings, or once the booking is reserved again if it starts on reserved bookings.
    • The project status automation confirms the positions of a project's bookings when the project becomes Planned, Active or Completed.

    The position status can be changed in the booking side drawer, on the booking page, in the resource plan and in the project plan, except on a team booking. The project's Team members tab shows it but does not edit it.

    Bookings and Schedules

    Every booking comes with a schedule. The booking defines the start, end and total effort in person days or capacity of a person’s assignment. The schedule defines how the effort is distributed on the timeline. In a simple example the booking could be for five person days (with 8h per person day) over a duration of two weeks. The schedule could be 4 hours every working day, or 3 days the first week and 2 in the second, or any other distribution.

    Schedules and bookings are relevant for different use cases. The booking defines the commitment of the resource’s time for a given duration. It typically involves an approval process. In the example above, the resource’s team manager has committed the resource to the project for five days. The detailed planning on how the days are delivered is done by the project manager.

    Here the project manager can change the schedule but not the committed times on the booking. The permissions for bookings and schedules are different.

    Booking and Schedule Permissions

    decídalo distinguishes resource-based and project-based permissions.

    Resource based permissions are directly tied to users through their permission profile. The user’s permission profile is set on the Account tab on their profile. The permissions a user gets from this are defined on the Permissions menu item under the Administration menu section. This menu item is only visible to Administrators.

    Resource based permissions define which features a user can access and which permissions he has on employee data like profiles and CVs. These permissions are static and defined by the users role within the organization. Typical permission profiles are employee, team manager or administrator.

    Project-based permissions extend the resource-based permissions in a project context. For example, an employee may not be allowed to edit any bookings by default, but if he is assigned to a project as a project manager, he can be allowed to edit the bookings for that project. In this case he does not have resource-based booking permissions but project-based permissions for specific projects.

    Resource-based permissions

    In the booking context the following permissions are relevant:

    Projects section

    Project editing. The default permissions for editing projects. The user can either edit the project he added himself (Own data) or all projects (All data). On this level we can only define general project permissions and not permissions for specific projects. Note that there is no “none” option since it must always be possible that users add projects to their project history on their profile.

    Create and edit project positions and bookings: Defines for which projects the user can add or edit bookings by default. The options are also Own or All. Even if a user is in general allowed to create or edit bookings he cannot automatically add or edit bookings on any project. Booking permissions and project permissions are separated. If a booking is added to a project, this affects the project’s costs and modifies the project. Therefore, separate permissions are required to do this. Note, that in decídalo bookings can be created without a project.

    Allowed to grant project permissions: This is the permission to set the project manager, resource manager, sales responsible or substitute project manager on a project. These roles get project-based permissions. To prevent that users extend their own or someone else’s permissions by setting these roles, this requires an explicit permission. This capability can also be granted per project and contact type instead of globally (see “Grant project permissions” under Project-based permissions below).

    Bookings and schedules section

    Create and set soft / reserved / confirmed bookings: These are three separate permissions for the different booking statuses. They define for which group of persons the user can create bookings in the respective status or set that status on an existing booking. The options are:

    • None: this option is only available for the status confirmed. If this is set, the user cannot create a confirmed booking for anyone, including himself. Soft and reserved bookings the user can at least create for himself.

    • Own data: the user can create bookings in this status only for himself or set the status only on his own bookings (where he is booked).

    • Team data: in addition to his own data, the user can do this for the team or teams he is managing. This option only makes sense for permission profiles that can manage teams (permission “Allow to lead team” set to yes).

    • Resource Group - In addition to his own data, the user can do this for the resource groups he is managing. This option only makes sense for permission profiles that can manage resource groups (permission “Allowed as resource group manager” set to yes).

    • Team & Resource Group: this option is relevant for users that lead teams and resource groups. It combines the two previous options.

    • All data: the user can create or set bookings in these status for everybody.

    Edit bookings: This permission specifies which bookings the user can edit. Editing includes all properties of the booking, like start / end date, person days, but also the status. With edit permission the user can set any status on the booking, regardless of the create and set bookings permission described above. Edit permissions only apply to existing bookings. Permission the user gets from this setting overwrites any restrictions he may have from other permissions, including the “Create and edit project positions and bookings” or any project-based bookings. That’s the reason why this permission is introduced. For example, a team manager may not have permission to book anyone from his team on a project. The project manager is responsible for the project and must approve this. But for everyone on his team the team manager is typically allowed to edit their bookings because he is responsible for his team’s utilization.

    The options are the same as above with one addition:

    • Self created data: these are bookings created by the user for himself. If someone else created the booking for the user, this would be “own data” but not self-created. This option is introduced to allow users managing adding and editing their own bookings, but preventing them from editing bookings that were created for them through an approval workflow.

    In general users can always edit bookings they created as long as they are in the same status that they created them in. This is a global default permission that does not need to be configured and cannot be disabled. It prevents that users cannot correct bookings directly after creating them.

    View bookings and schedules: Permissions to view bookings and schedules. They should at least be the same level as the editing permissions. The definition of the options is the same as for editing.

    Edit booking schedules: As explained in the previous paragraph, permissions to edit schedules must be distinguished from permissions for bookings. This setting configures permissions to edit the schedule belonging to a booking, independent of the permissions on the booking.

    Resource based permissions for projects and bookings, with values per permission profile

    Project-based permissions

    Project-based permissions are configured under the “Project based” tab on the Permissions page.

    They are used to extend the permission for defined project contact persons within the scope of a project. The following contact persons can be set on the project and can get project-based permissions:

    • Project manager
    • Substitute project manager
    • Sales responsible
    • Resource manager

    These project contact types are mapped to the permission profiles defined on the “Resource based” tab. The mapping defines which users can be set for which contact type. For example if all user can be set as the project manager on a project, we need to map all permission profiles to the project manager contact type. If only resource managers can be set as the resource manager on a project, the mapping is one-to-one in this case.

    The mappings are defined by clicking on the icon in the contact type column. This opens a side drawer where the related permission profiles can be selected.

    Project based permissions with a side drawer selecting the permission profiles eligible as project manager

    Besides the four built-in contact types (project manager, resource manager, sales responsible and project assistant), an administrator can add contact types of their own, for example a delivery lead or a quality manager. Click Create on the “Project based” tab and enter the name of the new type in your own language. The screen languages you leave empty are translated automatically; you can adjust the translations on the data fields page. The new type appears as its own column and starts with the same permissions as the project assistant, with every permission profile mapped to it, so review both before you assign anyone. It is then available on every project as its own contact section, in the project list and its filters, for contact groups, and as a recipient of email notifications, where it is switched off until you enable it.

    To delete a contact type you added, open its side drawer and click Delete. The built-in types cannot be deleted. While users are still assigned to the type on a project, the button is disabled and names the reason on hover. Deleting a type also deletes its contact groups.

    To rename a contact type or switch it off, use the data fields for Projects (Administration menu → Data fields → Project), see Customizing data fields. A switched-off type grants no project-based permissions.

    The following booking-related permissions can be configured by contact type:

    Create and set soft / reserved / confirmed bookings: If set to yes, the contact person can create bookings in the respective status (soft, reserved, or confirmed) for all profiles for which he has view permissions. It only takes effect on the “Team members” tab of the project. With this permission the user can create bookings via the “Add member” functionality (under the Add button). Ensure that the (resource-based) permission profiles mapped to the (project-based) contact type have “Profile view” permission higher than “Own data”. Otherwise the user can just book themselves.

    Edit bookings for project: If “Yes” the contact person can edit all existing bookings on this project, regardless of his resource-based permissions. This includes changing the booking data (dates, person days, etc.) and the status. He can change the status to any value, except for people he reaches only through a completed or withdrawn project (see below).

    Edit booking schedules: If “Yes” the contact person can edit all schedules belonging to bookings for this project, regardless of his resource-based permissions.

    In addition to the booking-related permissions above, the following project-management permission can be configured by contact type:

    Grant project permissions: If “Yes”, the contact person can manage the contacts of this project: they can set or remove project contacts (project manager, substitute project manager, resource manager, sales responsible, and any contact type your administrator added) and attach or detach contact groups and resource groups, for the projects where they hold this contact type. This is the project-scoped counterpart of the resource-based “Allowed to grant project permissions” permission: it lets, for example, a project manager manage the contacts on their own projects without being able to do so on all projects. Substitutes (deputies) of such a contact inherit this permission.

    Project-based permissions only reach people while the project is open. View team members lets the contact person open the profiles of the project's team members and of the candidates on its resource requests, and see these people by name in search. View all schedules of team members shows the project's team members with all their schedules in the resource plan. The booking permissions above also let the contact person book the team members of any of their projects. A project without a status counts as open.

    Once the project is set to Completed or Withdrawn, this reach ends for the people who are reachable only through that project: the contact person can no longer open their profiles, sees them anonymized in search, no longer sees them in the resource plan, and can no longer book them or change the status of their bookings (including rejecting a booking), on other projects as well as on the closed project itself. The project stays accessible: the project, its team list, its bookings (on the project and on the bookings page) and its resource requests stay visible, and editing bookings (dates, hours), time recording, billing and comments work as configured.

    Booking Workflows

    The booking workflow defines the approval steps required to get from a reserved booking (or, if configured, a soft booking) to a confirmed booking. Booking workflows are used in larger organizations where different people are involved in the project staffing process. If in your organization resources are directly booked to projects without any approval steps, then booking workflows are not relevant for you.

    The required approvals depend on the organization and can be configured. A typical workflow for mid-sized organizations has a single approval step: The team lead (line manager) needs to approve the bookings of his employees.

    In large firms the workflow can involve multiple people, e.g. resource manager and team lead.

    Booking workflows require the booking to be linked to a project. The project provides the context for the booking, especially the involved roles and people.

    In decídalo the following user roles can be involved in the booking workflow:

    • Project Manager: The project manager set on the project. This is the same as the project manager contact type from the project-based permissions.

    • Team Lead: The Team Lead of the booked resource as shown on the person’s profile.

    • Candidate: The booked resource (person).

    • Resource Manager: The Resource Manager set on the project. This is the same as the resource manager contact type from the project-based permissions.

    • Requestor: The requestor is only relevant if the booking belongs to a resource request. In this case the requestor is the person shown in the “Requested by” field in the Responsibilities section of the request.

    Project details with the project manager and resource manager fields highlighted

    : project manager and resource manager are set on the project

    When a resource request is created for a project, the project manager and resource manager are automatically copied. The requestor is by default the user that created the resource request. These contact persons can be changed afterwards.

    Resource request overview with the requestor, project manager and resource manager highlighted

    If a reserved booking is created on a project (or a soft booking, if the workflow starts on soft bookings), the approver(s) (configured by the workflow) will get a task in decídalo which is noted under the 'My tasks' menu section. The tasks are sorted by due date per default, and it is also possible to navigate to the project (via the project name link) or the resource request (via the request name link).

    My tasks list of booking approval tasks with project, request, booking dates, status and due date

    Clicking on the booking id, the approver can get to the actual booking. At the top of the page, under the booking's general info, a banner is indicating the possibility to approve or reject this booking.

    Reserved booking page with a highlighted banner offering approve and reject buttons

    By clicking 'Approve', the current user gives one's consent to the requested booking. If 'Reject' is clicked, a pop-up with a select field for the rejection reason appears. Select a reason and click 'Confirm' to reject the booking. The Rejected by column in the bookings grid then shows who rejected it. Like the candidate, the rejecting user is shown anonymised if your permissions do not allow you to see their profile (see Anonymisation). It stays empty for a booking rejected directly through its status, and is cleared once the booking leaves the rejected status. Setting a rejected booking back to another status also clears the earlier approval decisions, so they no longer appear under Activities. If the new status is one the approval workflow handles, the approvers are asked again.

    Rejection dialog with a dropdown of rejection reasons

    Configuring booking workflows

    To configure workflows for booking approvals in decídalo, select the Administration menu item in the Administration menu section. Then expand the Resource management section and select Booking workflow.

    Booking workflow configuration with approval task and email rows per role, set to mandatory, optional, yes or no

    From top to bottom, the page holds the Booking workflow emails active option (see Notifications), the Workflow starts on field (see Workflow start status), the configuration table and the Team booking workflow table (see Team bookings). The first row in the configuration table (Approval tasks) is used to configure the required approvals. The other rows are used to configure email notifications related to approvals.

    Workflow start status

    The Workflow starts on field decides which booking status starts the approval workflow. It sits between the Booking workflow emails active option and the configuration table and offers two options, each shown with a short explanation:

    Option Effect
    Reserved booking (default) Reserved bookings get approval tasks and are confirmed once approved. Soft bookings are not part of the workflow.
    Soft booking Soft bookings get approval tasks, and the last required approval sets them directly to confirmed, without passing through reserved. Reserved bookings are not part of the workflow. This fits companies that do not use reserved bookings, for example because their consultants plan themselves and a reserved booking would distort the forecast.

    While Soft booking is selected, a note under Workflow starts on explains how the Position status data field holds the approval back (see Approval while the position is unconfirmed).

    Only one status starts the workflow at a time. The configuration (the approval levels and emails in the table, and the task deadlines) applies to whichever status is selected.

    Approving a task needs no booking permission. With the workflow starting on soft bookings, a project manager without the permission to create or set confirmed bookings can therefore still confirm the bookings a resource manager has soft-booked, and only those.

    Changing the field asks for confirmation first and takes effect at once:

    • Open approval tasks on bookings in the previous status disappear. Bookings in the new status get their tasks right away, without an approval email, unless their approval waits for the position (see Approval while the position is unconfirmed). Their deadlines count from the day the booking was created or its position was confirmed, so some may already be overdue.
    • Approvals already given stay valid, so a booking only needs the approvals that are still missing.
    • A booking in the previous status is no longer part of the workflow. Only someone with the permission to set confirmed bookings can confirm it.

    Note: When the workflow starts on soft bookings, check the project status automation. By default it moves soft bookings to reserved when a project becomes Active or Completed, which takes them out of the workflow before anyone has approved them. Set the soft booking transition of these project statuses to Soft, so that the approval confirms the booking.

    Approval tasks

    The booking approval workflow is triggered when a booking in the workflow's start status (reserved by default, see Workflow start status) is created under a project. If a booking is approved, the booking status is changed to confirmed. If the approval is rejected, the status is changed to rejected.

    Before configuring the workflow review the booking permissions described above. If, for example, you want project managers to be able to find resources for their project but require approval from the team manager, ensure that the project manager is permitted to view all profiles, permission to create reserved bookings (or soft bookings, if the workflow starts on soft bookings) but no permission to create or set confirmed bookings. The first permission is needed to find candidates, the second to trigger the approval workflow, the third to ensure the team manager must be involved to confirm the booking.

    Decídalo supports two types of approval configurations:

    1. Specific people must approve
    2. Any eligible person can approve

    To configure the first type, set the “Mandatory” option in the “Approval task” row for roles that must approve the booking. For example, if the Team Lead must approve, set Mandatory in the Team Lead column and set all other columns to No. If the Team Lead and the Resource Manager must approve, set both columns to Mandatory. The booking is set to status confirmed only after both roles approved it.

    For the second type of approvals set all roles that can approve the booking to “Optional”. For example, if the Team Lead or the Resource Manager can approve, set both optional. The booking is approved when either one of them approves it. Just one person needs to approve here.

    If mandatory and optional roles are configured, the optional ones are ignored. Make sure to have only “Mandatory” or only “Optional” set in the first row.

    In case a person who needs to approve a booking creates the booking, the creation is treated as an approval. You can’t approve bookings you created yourself.

    This is relevant in the context of Resource Requests. Let’s assume we configured the requestor to be a mandatory approver. If a resource manager creates a booking in status reserved for the resource request, the requestor must approve it. However, if the requestor himself created the booking, there is no need for him to approve it. If the requestor does not have permission to confirm the booking, you must ensure that an additional approver is configured, e.g. the resource manager.

    Approval while the position is unconfirmed

    This applies when the workflow starts on soft bookings and the Position status data field is active (see Position status).

    While the position of a soft booking is unconfirmed, the booking gets no approval task and no approval email. The position is still an opportunity, and the booking could not become confirmed yet anyway. The booking page shows no approval banner, and the approval history lists no open approvals.

    As soon as the position is confirmed, the approval tasks are created and the approval emails are sent. It does not matter how the position is confirmed: on the booking page, in the booking side drawer, in the resource plan or the project plan, when a candidate is assigned to a position, through the Import API, or by the project status automation when the project becomes Planned, Active or Completed. The deadline of such a task counts from the day the position was confirmed, not from the day the booking was created.

    The Positions confirmed email can tell the project contacts which positions on their project have been confirmed.

    Deactivating the Position status data field while the workflow starts on soft bookings creates all waiting approval tasks at once, without approval emails, and their deadlines count from the booking's creation. decídalo asks for confirmation before the field is deactivated under Administration > Data fields > Booking, and the Booking workflow page shows a note about it while the workflow starts on soft bookings.

    Notifications

    The rows below the “Approval task” row list the configurable email notifications for the approval workflow.

    To enable workflow emails in general set the “Booking workflow emails active” checkbox above the workflow configuration table. This checkbox is the same as the Workflows Email notification on the Email notifications configuration (click on “Show email notifications” to get there). Setting it on the workflow config automatically sets it in the email config section, and vice versa.

    The following Emails can be configured:

    Email for approval task: If set to Yes and the same column has an entry in the approval task row other than No, then an email is sent to the corresponding contact if an approval task is created for them. If the same column has No in the approval tasks row, a Yes in this email row will be ignored.

    Email when confirmed: If set to Yes, an email will be sent to the contact, once the status of the booking changes to confirmed, i.e. after the final approval. In contrast to the previous mail, this email can be set independent of the value in the approval task column. The mail can also be sent to contacts that don’t have to approve. For example, the candidate can be informed, even if he does not have to approve.

    Email when rejected: Same as above but sent when the booking status is set to rejected, i.e. when an approval is rejected.

    Note: The project status automation can trigger email notifications, if they are configured for the target booking status.

    Team bookings

    A team booking reserves capacity on a whole team instead of on one person, and the team lead decides later who does the work (see team bookings on the team timeline). The Team booking workflow table below the configuration table gives the team lead a task to confirm, distribute or reject such a booking. The table is marked as beta.

    To use the workflow, switch on Team bookings under Administration > Resource management > Booking workflow.

    Setting Description
    Team bookings Gives the team lead of the booked team an approval task whenever a team booking is created in or set to the status the workflow starts on (reserved by default, see Workflow start status). The team lead is the team's primary manager; its additional managers and the managers of parent teams get no task.
    Enforce distribution Shown while Team bookings is on. The task no longer offers Confirm, so the team lead must distribute or reject the team booking. Changing the booking status directly is not affected. Switching Team bookings off also switches this setting off.
    Team booking emails Shown while Team bookings is on. Sends the booking workflow emails for team bookings (see Emails for team bookings). Switching Team bookings off also switches this setting off.

    All three settings are off by default. The task adds no right to view the booking. As with an approval task for a person booking, the team lead needs a permission that lets them view the booking, for example View bookings and schedules with Team data or All data, to open the task under My tasks and the booking page with its banner. Without it, both show the permission-denied page. To change the status directly, they need the ordinary booking permissions described above.

    While Team bookings is on, the team lead finds the task under My tasks as Approve or distribute team booking for followed by the team's name (Distribute team booking for while Enforce distribution is on), and a banner on the booking page offers the same actions, in this order:

    • Confirm sets the team booking to confirmed. It is not offered while Enforce distribution is on.
    • Select team members opens the dialog that distributes the team booking's person days to members of the team. It is only offered if you may distribute the team booking. It stays disabled while the team booking has no valid period or no person days, or while you may set no booking status; hover over the button to see why. Distributing all person days removes the team booking, and the booking page then takes you to its project.
    • Reject asks for a rejection reason and sets the team booking to rejected.

    The task follows the rules of the approval tasks for person bookings:

    • The task is only open while the team booking is in the status the workflow starts on. Unlike an approval task for a person booking, it never waits for the position to be confirmed, because a team booking ignores the position status.
    • After a change of Workflow starts on, a team booking that is already in the new start status gets its task right away only if it was created in or set to a start status before. Any other team booking gets its task once it is set to the new start status.
    • Confirming or rejecting closes the task, and the booking's activities show who requested the booking and the team lead's decision. Setting a confirmed team booking back to the start status does not bring the task back. Setting a rejected team booking back to another status clears the decision, as it does for person bookings, so the task comes back once the team booking is in the start status.
    • A team lead who booked the team themselves gets no task.
    • A substitute of the team lead sees the task on the Substitute tasks tab and can confirm or reject it on the team lead's behalf. Selecting team members stays with the team lead.

    Note: The task and the banner are only shown to users with the Feature preview permission (see permissions).

    Emails for team bookings

    While Team booking emails is on, team bookings get the booking workflow emails, as person bookings do. Like those, they also depend on Booking workflow emails active and on each user's own email settings.

    • Approval task: the team lead gets an email whenever their task appears, regardless of the Email for approval task row, and so does a substitute of the team lead. Only users with the Feature preview permission receive it, because only they see the task. The email names the booked team and always links to the team booking.
    • Confirmed: sent when the team lead confirms the team booking through the task, to every contact with Email when confirmed set to Yes. Setting the status to confirmed directly sends no email, as for person bookings.
    • Fully distributed: sent when all person days of a team booking that went through the workflow are distributed to team members, to the same contacts as Email when confirmed. It shows the team booking's details and links to the project's team members, because the team booking no longer exists. Distributing only part of the person days sends no email.
    • Rejected: sent when the team booking is rejected, through the task or by changing its status directly, to every contact with Email when rejected set to Yes.

    For these emails, the Team Lead column means the booked team's primary manager. The Candidate column does not apply, because a team booking has no booked person. Substitutes of the recipients get the emails as they do for person bookings, and whoever made the change gets none. If a recipient's authorization role does not have the Bookings page enabled, the confirmed and rejected emails link to the project instead of the booking.

    In This Article
    Version history Back to top Copyright © data assessment solutions · decidalo.com