New Employee Onboarding with Approvals and Notifications — SharePoint Automation
IT Partner develops an automated new employee onboarding process in SharePoint Online that lets authorized users submit account requests through a form, route those requests for supervisor approval, and receive new user credentials by email after approval, without giving those users Microsoft 365 global administrator rights.
What this engagement is
This service sets up an automated process for requesting new employee user accounts. An authorized user fills out an account request form on a SharePoint Online site, specifies the supervisor who must approve the request, and submits it. The supervisor receives an email with the request details and approve/reject options. After approval, the requester receives an email with the login and password for the new account to provide to the new user.
Success criteria
What you receive
How the work unfolds
Confirm business goals, review the standard onboarding request scenario, identify the client point of contact, confirm required access, and agree on the expected approval and notification flow for the fixed-scope implementation.
Collect the standard account request parameters, approver list requirements, supervisor selection approach, SharePoint site location, email notification requirements, and any tenant-specific details needed to configure the form and approval process.
Configure the SharePoint Online request form elements with standard parameters, set permissions for authorized requesters and approvers, build the common supervisor approval workflow, and configure email notifications for approval requests and approved account credentials.
Test the end-to-end onboarding request process with client-provided sample data, verify that eligible supervisors can approve or reject requests, confirm notifications are delivered, and validate that credentials are sent after approval as scoped.
Review completed deliverables with the client, provide user instructions, confirm acceptance against the success criteria, document any agreed limitations or follow-up items, and begin the one-month post-implementation break/fix support period after project closure.
Prerequisites
Who does what
IT Partner
- Create and configure account request form elements with standard parameters
- Set up common approval process
- The common approval process is waiting for approval from the supervisor that is specified in the form and included in the list of users with approval permission
- Create instruction for users
- Post-implementation break/fix support for one month after project closure
Your team
- Coordinate Client resources and staff schedules
- Provide a dedicated point of contact responsible for working with IT Partner
- Provide all the necessary information to organize the process
- Review and approve engagement deliverables in a timely manner
What's not included
Limitations & technical notes
Frequently asked questions
What does IT Partner’s New Employee Onboarding with Approvals and Notifications service do?
IT Partner develops an automated new employee onboarding process in SharePoint Online. Authorized users submit new account requests through a form, the request is routed to a specified supervisor for approval, and after approval the requester receives the new user login and password by email.
Why use this onboarding process instead of giving managers Microsoft 365 admin rights?
This service lets authorized users request new accounts without giving them Microsoft 365 global administrator rights. The process uses a SharePoint Online form and supervisor approval workflow, while the required implementation access is handled through the project setup.
What is included in the service?
The service includes account request form elements with standard parameters, a common approval process, approval routing to the supervisor specified in the form, user instructions, and one month of post-implementation break/fix support after project closure. The supervisor must be included in the list of users with approval permission for the approval process to work as scoped.
What is not included in the standard scope?
Additional fields and extra process conditions are not included in the standard scope. They can be customized as additional cost items, and those changes should be discussed with IT Partner because the plan may vary depending on your needs.
What information is collected in the onboarding request form?
IT Partner creates account request form elements with standard parameters, but the exact field list is not specified in the service description. During the engagement, the client provides the necessary information to organize the process, and any additional fields should be confirmed with IT Partner.
How does the approval process work?
An authorized user submits an account request form and specifies the supervisor who must approve it. The supervisor receives an email with the request details and approve/reject options, and the process waits for approval from that supervisor if the supervisor is included in the approved list of approvers.
Who can approve new employee account requests?
Approvals are handled by the supervisor specified in the form, provided that person is included in the list of users with approval permission. This matters because the scoped workflow is designed to wait for approval only from an eligible supervisor.
What happens after a supervisor approves a request?
After approval, the requester receives an email containing the login and password for the new account. The requester can then provide those credentials to the new employee according to the organization’s internal onboarding process.
What happens if a supervisor rejects a request?
The service description states that the supervisor receives approve/reject options, but it does not define the exact rejection notification or follow-up process. If your organization needs specific rejection handling, escalation, or resubmission logic, confirm that requirement with IT Partner.
What Microsoft 365 prerequisites are required?
Your organization must have SharePoint Online and use Microsoft Entra ID. You must also have global admin level access to the Microsoft 365 tenant for the implementation.
Does the client need global admin level access?
Yes, global admin level access to the Microsoft 365 tenant is listed as a prerequisite. The exact access method for implementation should be coordinated with IT Partner. The resulting process is intended to let authorized users submit account requests without receiving global administrator rights.
What are IT Partner’s responsibilities during the engagement?
IT Partner is responsible for creating and configuring the standard account request form elements, setting up the common approval process, configuring supervisor-based approval for eligible approvers, creating user instructions, and providing one month of post-implementation break/fix support after project closure.
What are the client’s responsibilities during the engagement?
The client coordinates internal resources and staff schedules, provides a dedicated point of contact, supplies the information needed to organize the process, and reviews and approves deliverables in a timely manner. These responsibilities are important because the workflow depends on accurate organizational and approval information.
What are the implementation steps for this service?
The listed implementation milestones are kickoff meeting, gathering necessary information, creating the form and approval process, verification, and project closing. The source scope provides milestone names but not detailed milestone descriptions, so confirm the exact activities and schedule with IT Partner.
How long does the onboarding automation project take?
The listed duration for this service is 3 days. The plan may vary depending on your needs, so the exact schedule should be confirmed with IT Partner after the kickoff and information-gathering steps.
Will this project cause downtime for existing Microsoft 365 users?
The service description does not identify any required downtime. Because the work focuses on creating a SharePoint Online form and approval process, any business impact should be confirmed during planning based on your tenant configuration and requirements.
Can the request form or approval process be customized?
Yes, additional fields and process conditions can be customized, but they are additional cost items and are not included in the standard scope described for the service. If you need custom data fields, special routing rules, escalations, or extra conditions, discuss them with IT Partner before finalizing the engagement.
Does the service include training or documentation for users?
Yes, IT Partner creates user instructions as part of the deliverables. The scope does not specify live training sessions, so any training beyond written instructions should be confirmed separately.
What support is provided after the project is completed?
IT Partner provides post-implementation break/fix support for one month after project closure. This support is for issues with the implemented solution, while new enhancements or additional customizations should be confirmed separately.
How is pricing determined for this service?
The listed price for the standard service scope is $900. Additional fields and process conditions are listed as additional cost items, so pricing for customization should be confirmed with IT Partner.