How do I set milestone and team assignment?

Milestones and tasks within the Operations Phase have extensive and stratified settings, so organizations can better manage the submission, reviewal, and approval of workflow stages. Within the Operations settings tab, org admins can designate responsibility to specific assignees (individuals or teams) over various milestones by workflow, and apply multiple levels of approval. Approval options include “Manual Approval”, “Single Approval”, and “Dual Approval”. “Manual Approval” allows an individual or team to both mark the milestone and associated tasks as approved. “Single Approval” uses a designated submitter and a designated approver to advance the workflow. Lastly, “Dual Approval” requires an additional designated reviewer, so the process flows from submitter, to reviewer, and then to approver.

See below for details on how to implement milestone and task assignment within the Operations settings and how to incorporate the different levels of approval.

Select the settings wheel in the top right of the EverBright platform.
Navigate to the Operations Phase tab in the left-hand menu.
Land on the “Assignment” tab.
See the top 3 dropdown tabs: “Default Milestone Submitter”, “Default Milestone Reviewer”, and “Default Milestone Approver”.

In this example, “Submitter”, “Reviewer”, and “Approver” all have designated assignees - this is a “Dual Approval” setup. These fields represent the fallback user assigned to any milestones and the specific role when there is not a specific individual assigned to a milestone.
As shown in the “Default Milestone Submitter” dropdown, there is a “None (Unassigned)” option for these milestone roles.

Note: by default, any users with access to Operations can complete tasks and milestones.
1. The process outlined above for selecting “Default Milestone” roles is a means for determining fallback responsibility across all workflows.
  1. Additionally, “Default” selections allow for further specified designation for specific milestones.
Note: as written above the “Sales Requirements” settings (in edit mode) shown to the right, any assignment done within specific milestones or tasks will supersede the designations made in the “Default Milestone Submitter” and “Default Milestone Approver” dropdown menus.
Again, shown to the right is the “Sales Requirements” milestone - select the blue “Edit” button to view in this manner.

The default “Submitting Team” and “Approving Team” will be all individuals with access to Operations.
The dropdown menu can be used to select other organizationally structured teams (for more on setting up teams, visit the following article: How do I manage users and set permissions?) to be responsible for either submission or approval.
The “Default Assignee” on a specific milestone must be a member of the “Submitting Team” - regardless of who is selected (or if it remains “Default Milestone Submitter”) anyone with Operations access can take action on the milestone - it is just the approval process that is controlled by the teams. That access level supersedes both the “Default Assignee” and “Default Milestone Submitter” roles - the “Default Assignee” selection is only designed to add further stratification of responsibility without restricting functional action.

The Milestone Restrictions section allows you to block specific users from seeing this milestone.

Select the “Blocked Users” dropdown to select users to remove visibility into this milestone.
You can select any numbers of users from the dropdown
Click Save.