Employee Onboarding Tool
Manual access provisioning delays new hire productivity
New employees start but can't do their jobs because access provisioning hasn't happened yet. IT manually adds people to systems one by one. Team leads field constant requests about permissions. HR has no way to track what's been set up and what's still pending.
About this tool
This platform automates access provisioning based on department. Select a new hire's department and the system triggers the appropriate workflow. Development gets GitHub repositories, AWS Console, and PostHog. Customer support gets Intercom. Team leads approve repository access via email. Employees provide credentials through forms.
Department-based workflow automation, GitHub repository provisioning with team lead approval, AWS Console setup, PostHog and Intercom access, Postmark email notifications, workflow progress tracking, and MongoDB storage.
Access setup happens in hours, not days. IT handles exceptions instead of routine provisioning. Team leads click approve in email without touching GitHub settings. HR tracks exactly who has access to what.
Prompts used to build this app
I want to build an employee onboarding application that on the homepage should have all the added employees and the button to add a new employee. When I click on the button, add a new employee, I should be able to choose a department: customer support, development and marketing, add new employee's name, company email for that user, team lead email and their personal email where they will get a notification once all the accesses have been given. Customer support users should get access to Intercom. Development users from development department should get access to AWS, GitHub, and PostHog. When you assign GitHub and PostHog, first send an email to the team lead to set repositories from this organization where the new employee will get access to, then the team lead should get a link to a page where we should list all the available repositories from the current organization. Make sure to use requestSecret MCP to ask me for all needed credentials during the backend implementation. Once they check all the repositories, they can click done and after that continue with the flow. Then the next thing is to send an email to the employee's personal email to request their GitHub username. Once they get an email, they should open up a specific page to enter their GitHub username. Once they enter and click done, then we should give them the access to all these repositories. Also make sure that on each employee's page, when I open it up, I want to see the entire workflow that is triggered and I want to see all the accesses that they have been given the access to. Once all the accesses have been given, send an email to the employee's personal email with the list of all the accesses that they have been given. Also when I choose the department, I want to see the flow that will be triggered and all the accesses that will be given for that specific department for that user, the employee.
Don’t Miss Out
