Nanny Agency JobsA nanny may need a shared calendar, a household shopping account or another work service. Begin with the task you need to perform and have the account owner arrange appropriate access. Receiving a password is not a complete setup: you also need to know which account to use, what you may change and whom to contact when access fails.
The workflow below is an original NAJ approach to discussing work access. Product settings and available permissions vary, so use the actual service's instructions with the owner's authorization.
List tasks before requesting accounts
Write down the work that requires access: read the children's calendar, add an agreed appointment, view a shopping list or submit a specific update. For each task, identify the service, its owner and whether you need to read, edit or administer anything.
Ask the owner to use an individual invitation or designated work login where the service supports it. Do not assume that a parent's main email account is the appropriate doorway to every household tool. If the service cannot provide the requested arrangement, ask the owner to choose another workable process.
Keep the list free of passwords, security codes and account-recovery answers. It should explain responsibility, not become a second credential store.
Establish the identity and device you will use
Agree which email address receives invitations and whether access belongs on an employer-provided device or an approved personal device. Check which account is already signed in before accepting an invitation. Similar profile icons can make a wrong-account mistake easy to miss.
Clarify who controls recovery settings for a household-owned account. Do not make your personal phone number the only recovery route without an explicit arrangement. Equally, do not let a work setup unintentionally give someone control over your personal account.
If a service asks for broader permissions than the task appears to need, stop and ask the owner to review the request. Do not approve it simply to get past the screen.
Agree how credentials will be handled
Google's account guidance recommends different passwords for important accounts and suggests a trusted password manager. Agree the setup with the owner.
Keep work credentials separate from personal credentials. Avoid putting a password in a daily report, calendar description or ordinary task list. Where a household uses a password manager, ask the owner to provide only the access needed for your agreed work through its supported process.
Discuss any additional sign-in checks before the first shift that depends on the account. Know whom to contact if a verification step cannot be completed. Do not borrow another person's identity, bypass a control or change account protections to make an immediate task easier.
Test one ordinary task with the owner
Open the intended service and confirm the account identity and visible information. Test a small agreed action with the owner, such as viewing a named calendar entry. If editing is required, use a clearly identified test entry that the owner has approved.
Check the outcome from the owner's side. Being able to click “save” does not tell you whether you edited the correct calendar or list. Remove any test material through the agreed process and record only that the task was successfully tested.
If access exposes unrelated private information, tell the owner and ask for a narrower arrangement. Do not explore it to understand how the account works.
Work through a calendar invitation
Fictional example: Nanny Priya needs to view the children's schedule and add appointments after parent approval. The parent initially offers a main account password. Priya asks whether the calendar can instead be shared to her designated work address.
The parent checks the service's available permissions and sends an invitation. Priya notices that her personal account is currently open, switches to the agreed work identity and accepts there. Together they test access with a clearly labeled practice event.
The parent remains responsible for calendar ownership and removing the invitation when the arrangement ends. Priya records the service, owner, work address and tested task in the access list, without recording a password.
Plan for loss, changes and the end of access
Agree an immediate reporting route for a lost device, unexpected sign-in prompt or suspected account problem. Report what happened and when; avoid experimenting with recovery or deletion tools on someone else's account. The owner can then follow the service's official response process.
At a role change or departure, review the access list together. Identify who removes invitations, recovers work devices and handles any authorized transfer of work material. Do not erase shared records or retain private household information as a personal archive. The aim is a completed handover with access deliberately reviewed, rather than a forgotten login that continues indefinitely.
Sources
Google's account guidance. Source checked October 27, 2026.