An HR Portal in SharePoint: Policies, Onboarding and Requests in One Place, Personnel Files Kept Private

SharePoint HR solutions are what you get when the HR department's site in Microsoft 365 is built on purpose: one place for policies, benefits information, onboarding and employee requests, with a separate locked area for the files only HR may open. Lightray Solutions designs and builds that portal, remotely, inside the Microsoft 365 tenant you already pay for.

Begin with a free 30-minute strategy call with Edward Pinela, MBA. He asks which questions reach HR most often, which documents exist and who may see them, then tells you whether SharePoint is the right home for each. A build is quoted after that call; Lightray publishes no fixed price for SharePoint work because the scope varies too much between HR teams.

The portal is one piece of the wider Microsoft 365 consulting Lightray does, and it usually sits on a tenant structured along the lines described on the SharePoint implementation consultant page.

What does an HR team actually put in SharePoint?

Four things, in order of how much email they save: a policy and handbook library everyone can search, an onboarding area that walks a new hire through week one, request forms that replace HR's inbox, and a restricted space for HR's own working files. The table below shows how each one is built and who can open it.

Does Microsoft provide an HR site template?

Yes, two. The Human Resources communication site template ships with Home, Compensation, Career, Benefits and Culture pages. The New employee onboarding template adds Getting Started, an Onboarding Checklist page backed by a Microsoft List, leadership and priorities pages, Help and Support, and a news template for introducing new hires.

Templates are a fair starting point and a poor finish. They contain sample text and stock images, they say nothing about who may see what, and Microsoft notes that applying a template to an existing site does not merge your current content into it. Most of the work is replacing the placeholders with your real policies and deciding the permissions behind each page.

How do employees use the portal day to day?

Mostly through search and a few buttons on the home page. Someone wants the PTO policy, types 'vacation' and gets the current version, not an attachment from 2022. Someone needs an employment verification letter, opens a form, and the request lands in HR's queue with the details already filled in.

Requests run on Power Automate, Microsoft's workflow tool included with most Microsoft 365 plans. A submitted form creates an item in an HR list, routes it to the right person, and tells the employee when it is done. Approvals for things like tuition reimbursement follow the same pattern; our Power Automate consultants page goes deeper on how those flows are designed and maintained.

• Policy acknowledgements: a new handbook version sends each employee a request to confirm they have read it, and HR keeps the list of who has
• Onboarding tasks assigned to the hiring manager, IT and payroll, each with a due date relative to the start date
• Letters, address changes and equipment requests captured in one form instead of a chain of emails
• Org chart and contact pages drawn from Microsoft 365 profiles, so they stay current as people join and leave

How are personnel files kept private in SharePoint?

By keeping them out of the employee-facing site entirely. HR's working files live in a separate site or library whose membership is limited to the HR group, with permissions granted to groups rather than to individuals, so access changes when someone joins or leaves HR rather than file by file.

Microsoft Purview retention labels add a second control. According to Microsoft Learn's retention overview, a label can be applied by default to a whole library or folder, can keep a document for a set period and then delete it, and can mark an item as a record so it cannot be edited or deleted. Microsoft's own example is work visas. Your retention periods come from your HR policy and legal counsel, not from Lightray; the build applies them.

What should stay out of an HR SharePoint site?

SharePoint is a document and workflow platform, not a human resources information system (HRIS, the system of record for employee data, pay and benefits elections). Payroll, tax forms, benefits enrollment and medical or leave records with their own legal handling rules belong in the HRIS or payroll provider you already use.

The portal links out to those systems rather than copying their data. That keeps sensitive figures in one controlled place and means the SharePoint site never becomes a second, out-of-date copy of the employee record. If you are unsure where a file type belongs, that question is a good use of the first call.

How does a Lightray HR portal project run?

Discovery, structure, build, then handover. Discovery lists the documents, the recurring requests and the audiences. Structure sets the sites, libraries and groups, and agrees retention with whoever owns your records policy. The build fills the pages, creates the forms and flows, and migrates current policies. Handover trains HR's site owners on video and leaves written instructions.

New-hire training often becomes the next request once onboarding works. That is a separate design problem, covered on the SharePoint learning management system page, which explains where SharePoint can carry training and where it cannot. Teams still deciding where files should live at all may find the SharePoint vs OneDrive guide useful first.

You deal with Edward throughout: 20+ years of business systems work, 200+ projects delivered, a 4.9 rating on Google, and replies within 4 business hours.

Further reading: Microsoft Learn — Retention policies and retention labels.