Request a Project

Video has been removed from this PDF. Visit the BrightWork 365 knowledge base to view.

The project management lifecycle will typically begin in the BrightWork 365 Requests area, where a Requestor submits a new project request along with details needed for an approval decision. Through workflows, notifications and reports, the request process affords users an efficient method for starting the project management process.
Note: The request process and forms are different for users with different security roles. To submit a project request, at a minimum the user will need the security roles Basic User and BrightWork Request Submitter.

The Request process begins with the Requestor filling in the Request form.

  1. Click into the Requests area, and + New.

  2. A preliminary short form displays where a project title is entered, and a template from which to create the project is chosen.
    Note: Project titles must be unique, have a maximum of 50 characters, and should not contain any special characters including < > : * ? |

    BrightWork ships with three templates out of the box: Project Standard, New Product Introduction, and Product Update. For template details see Templates Overview.

    The selected template defines:
    • The forms used in the request.
    • The number of approval stages in the request. See Request Approval Stages.
    • The Business Process Flow (BPF) to apply to the project. The BPF is the process map at the top of the form. 
    • The forms to apply to the project. The form is all the columns and tabs used to display information about the project.
    • The Content Template that will be used to create the project if one is specified in the chosen template. Content Templates include content (i.e. stages, deliverables, tasks, issues, risks) copied in from another project.
  3. A longer form related to the chosen template type will then display for additional details to be entered. The number of fields displayed will be determined by the requestor's BrightWork security role. The Requestor fills in the request fields (and adds documents if desired) in order to activate the request Submit switch.
  4. After the Requestor clicks the Submit switch, the value will change to Yes. Save and Close the request, and an email with request details will be sent to whomever has been set as the Request Receiver, thereby initiating the approval process. Additionally an MS Teams Activity will be created for the request recipient to provide an additional option for interacting with requests. The notification's From address will be set as the related Flow Owner.



  • The list of available users to choose from in the Request Receiver column is limited to those users given the BrightWork Request Receiver security role.
  • The list of available users to choose from in the Approvers column is limited to those users in the Senior Managers Dynamics Team.
  • A Requestor can only see their own requests unless they have elevated privileges.

Requests App

In addition to the full BrightWork 365 app, organizations have the option to also install and assign users to the Requests app. The Requests app provides users who have only been given a free BrightWork 365 license and assigned the BrightWork Request Submitter role a means with which to log requests outside of the full BrightWork 365 app. Users of this app will have access to much of the same request functionality as found in the Requests Area of the full BrightWork 365 app for paid users, but they will not see the other full app areas on the Site Map such as the sections Projects, and Portfolios. However, note that these users still have access to these other app areas by navigating to them through other routes such as by clicking on linked columns, e.g., the Program column in the Request form.

As with all other functionality in BrightWork 365, Requests App users will need one of the following licenses from Microsoft: Power Apps per user, Power Apps per app, or Power Apps pay-as-you-go.