Onboard new project members

I need the new project members added to the Alpha Launch team and given the right access. Add Priya Shah, Marcos Diaz, and Lila Chen to the Alpha Launch project, assign them the role of Contributor, add them to the 'Creative Tasks' and 'Weekly Standups' sections, and set their default notification to project updates only. Before inviting, check the task list for any confidential attachments and remove anything not cleared for new hires. Deadline Friday 5pm.

Before I invite Priya Shah, Marcos Diaz, and Lila Chen, make onboarding as frictionless as possible for reviewers. Put the three must-know items at the top: who to contact for access issues, the first-week deliverable, and the sprint cadence. Show where their first task will appear, surface any blocked tasks they might inherit, and flag any tasks with confidential attachments that need manager sign-off.

I added Priya Shah, Marcos Diaz, and Lila Chen to the Alpha Launch project and set them as Contributors, but when I checked they have no tasks in My Tasks and no auto-notifications. I’m worried they’ll miss the Monday kickoff and lose trust in the onboarding. I don’t know whether I missed a project setting or if the tasks were created under a different section. What is the most likely cause and the quickest fix to ensure they see their first-week tasks before Monday?

New team members repeatedly arrive and don’t see or act on their first-week tasks, which costs hours chasing them and damages our credibility with stakeholders. I suspect we forget to assign tasks directly, rely on default notifications, or clutter the project with irrelevant tasks. Which single habit change would stop this slipping — and what three practical steps should I enforce on every new member onboarding to make it reliable?