Caregiver Access and Permission Models: What Actually Happens When You Add a Nanny or Grandparent to Your Baby App

Bottom line up front: Before inviting a paid nanny or an unpaid grandparent into any family coordination app, the question that actually matters isn't "does it support multiple caregivers" — nearly every app in this category claims that. It's three narrower questions almost none of them answer clearly in their marketing: does the caregiver need their own login credentials or just a temporary invite code, can that access be cleanly revoked if the arrangement ends, and does adding a second or third caregiver require upgrading to a paid tier. On top of that, a genuinely confusing naming collision exists in this exact product category right now — Cradle, Cradlo, Cradly, and Cradlet are four separate, real, currently active apps with overlapping names and different feature sets, and searching for one while meaning another is an easy, real mistake to make while sleep-deprived.

Related in this series: This guide extends the caregiver-login limitation flagged in our full Huckleberry review — Huckleberry uses shared account credentials across caregivers rather than the invite-code or per-caregiver-permission models covered here. For the full household budget, see our cost hub. For a related but distinct fragmentation problem — two kids on two different daycare platforms rather than two caregivers on one app — see our daycare app comparison.

First, a Practical Warning: These Four App Names Are Not the Same Product

Before comparing features, it's worth pausing on something that will genuinely trip up a tired parent typing into an app store search bar. As of 2026, there are at least four separately developed, currently active baby-tracking apps with confusingly similar names:

• Cradle — built around SweetSpot-style sleep predictions, an AI sleep coach feature, lock-screen live activity widgets, and multi-caregiver sync with no double-logging.
• Cradlo — positioned specifically around shared caregiver identities and real-time sync for partners, nannies, grandparents, and daycare.
• Cradly — a distinct product with its own published terms of service governing household billing and caregiver access removal (detailed below).
• Cradlet — combines baby tracking with an AI assistant for overnight questions and a built-in white-noise/lullaby sound-machine feature, blending two categories this cluster otherwise treats separately (see our Hatch vs. Yoto and Tonies comparison for the ambient-sound side of that overlap).

None of these four is a typo or a rebrand of another — they're independently developed products competing in the same crowded space with names close enough to cause real confusion. If you download one expecting a specific reviewed feature and it's not there, checking whether you actually installed a different one of these four is a reasonable first troubleshooting step before assuming a review was inaccurate or a feature was removed.

Baby-Specific Trackers vs. General Household Apps: Two Different Permission Philosophies

The caregiver-access landscape splits into two structurally different categories, and which one fits depends on what you're actually trying to coordinate.

Baby-Specific Trackers

General Household Coordination Apps

A separate category — not baby-specific, but often pulled into service by families managing a nanny or grandparent alongside general household logistics — handles caregiver permissions with meaningfully different philosophies:

• FamilyWall adds a nanny or grandparent through a standard member invitation, granting the same member-level access as any other family member joining the household.
• Cozi can add anyone to the family account, but — worth flagging directly — every person added receives full access to all of the household's data with no granular restriction available; there's no way to give a nanny visibility into the kids' schedule while withholding, say, financial or unrelated family information stored in the same account.
• Nines offers genuinely granular staff and vendor permissions, but only on its Standard tier or higher — the free or entry tier does not include this distinction.

The practical takeaway: if the goal is strictly baby-care coordination (feeds, naps, diapers, handover notes), a purpose-built baby tracker like Pebbi or Baby Connect is the more precise tool, since permissions are scoped to child-care data by design. If the household is also using a general coordination app for broader family logistics (school schedules, meal planning, household tasks) and considering adding a caregiver to that same app for convenience, Cozi's all-or-nothing access model is worth weighing carefully against Nines' more granular (but paywalled) permission structure before assuming "adding them to the family app" is a low-stakes decision.

What Happens When the Arrangement Ends: The Access-Revocation Question Most Apps Don't Answer

This is the single most practically important question a family should ask before onboarding a paid caregiver into any shared app, and it's the one most marketing pages simply don't address. Cradly's own published terms of service are unusually direct about this, stating plainly: if a caregiver is removed from a household, their access ends immediately, while historical data they logged remains part of the household's permanent record. This is a sensible, clearly stated policy — access to ongoing data stops the moment the relationship ends, but the family doesn't lose the actual care history that caregiver contributed while employed.

Most competing apps in this category don't publish an equivalently explicit statement about what happens on removal, which doesn't necessarily mean they handle it poorly — it more likely reflects that this level of terms-of-service detail simply isn't something most consumer app companies write down clearly, leaving the family to test it themselves or contact support with the question. Before onboarding a nanny into any shared app, it's worth explicitly checking: can the account owner remove a specific caregiver's access unilaterally, does removal happen immediately or after a delay, and does removed access retroactively hide data that caregiver already logged (which could create a gap in your child's care record) or simply stop future access (Cradly's model, which preserves the historical record). For a nanny relationship that could end on short notice — a real, common scenario — knowing the answer before you need it matters considerably more than after.

Matching the Access Model to the Actual Relationship

Not every caregiving relationship needs the same permission structure, and treating a grandparent who visits twice a week the same as a full-time nanny with daily access is a common mismatch:

• A grandparent with occasional access: A simple invite-code model (Pebbi, Cradlo) that doesn't require creating and remembering a separate login is the lower-friction choice — a grandparent who logs in once a week doesn't want to manage another password.
• A full-time paid nanny: Baby Connect's dedicated Professional tier, built specifically for this relationship type, may justify its cost through features scoped to a professional caregiving context rather than a family member's casual use — worth checking what that tier specifically adds beyond the standard Family plan before assuming it's simply a rebranded version of the same access.
• A daycare provider: Several apps in this category, including Baby Connect, specifically market daycare-compatible access, though the daycare's own systems (many facilities use their own reporting apps, like Tadpoles or Brightwheel) may make a parent-side app redundant for that specific relationship rather than complementary to it — check whether your daycare already provides its own daily report system before assuming you need to add them to your personal tracker as well.
• A co-parent or ex-partner sharing custody: Full, equal access via account-based sync (Baby Connect's model, or Huckleberry's shared credentials) may be more appropriate than a revocable invite-code model designed around temporary or professional relationships, since a co-parenting relationship isn't one either party expects to "remove" the other from.

Practical Recommendations by Situation

• Adding a nanny for the first time and want the cleanest access-control story: Explicitly ask (via support, if it's not in the published terms) what happens to their access and logged data if the relationship ends before committing to onboarding them into any shared app.
• Managing a grandparent's occasional help alongside a full-time nanny's daily access: Consider whether an app supporting differentiated permission tiers (rather than an all-or-nothing model like Cozi's) fits better than forcing both relationships into identical access levels.
• Confused about which "Cradle"-named app a recommendation is referring to: Check the developer name and exact app store listing before downloading — the naming overlap in this category is real and current, not a sign that one review or another made an error.
• Already using Huckleberry and frustrated by its shared-credential caregiver model: A dedicated caregiver-coordination layer like Pebbi's invite-code system can run alongside Huckleberry for the specific handoff/permission problem Huckleberry doesn't solve, rather than requiring a full platform switch.

Frequently Asked Questions

If I remove a nanny's access from an app like Pebbi or Cradly, do they get a notification that they've been removed? This varies by app and isn't consistently documented in public terms of service; if this specifically matters to your situation, checking directly with the app's support before relying on an assumption is the safer approach.

Can a grandparent use these apps without owning a smartphone, if they only have a tablet or share a family computer? Most of the apps discussed here, including Pebbi and Baby Connect, offer web-based access alongside their mobile apps, though the invite-code-based systems (built primarily around QR code scanning) may be smoother on a phone or tablet with a camera than on a desktop browser — check the specific app's web-access capability before assuming a phone is required.

Does Baby Connect's Professional tier for nannies cost the family or the nanny? This is a billing-structure detail that should be confirmed directly with Baby Connect before assuming either party is responsible, since app subscription billing conventions vary and aren't standardized across this category.

Is it safe to assume a "family plan" price like Baby Connect's $4.99/month covers unlimited caregivers, or does that cap apply too? Confirm the specific caregiver limit tied to any named plan directly with the current pricing page, since plan names like "Family" don't consistently imply unlimited access across different apps, and limits can change between the time a review is published and when you sign up.

If I'm already paying for Huckleberry Premium, is there value in also paying for Pebbi Premium for caregiver coordination? Potentially, if Huckleberry's shared-credential model genuinely isn't meeting your household's need for distinct caregiver identities or clean access revocation — but this means paying for two overlapping subscriptions, so weigh whether Pebbi's free tier (up to 2 caregivers) already solves your specific problem before upgrading either one.

Do any of these apps let me restrict a caregiver to seeing only one of my two children's data, rather than both? This capability isn't consistently available across the apps compared here and should be verified against the current version of whichever app you're considering — Huckleberry, as covered in our full review, does not offer this restriction, since its sharing model is account-wide rather than per-child.

Why would a family use a general household app like Cozi instead of a baby-specific tracker for caregiver coordination? Typically because the family is already using that general app for broader household logistics (calendars, task lists, meal planning) and wants to add the nanny or grandparent to one consolidated system rather than maintaining a separate baby-specific app alongside it — the tradeoff, as covered above, is Cozi's lack of granular data restriction compared to a purpose-built baby tracker.

Is Cradlet's built-in white-noise feature a substitute for a dedicated sound machine like Hatch or Yoto? It could serve a similar basic function for ambient sound, but it hasn't been evaluated in this cluster's decibel-safety research the way Hatch, Yoto, and Tonies have in our dedicated comparison — the same AAP volume-safety principles covered there apply regardless of which app or device is producing the sound, so testing your own setup's actual output remains necessary rather than assuming any built-in feature is automatically calibrated safely.

How often should I re-verify pricing and caregiver limits for these apps given how fast this space seems to be changing? Given the number of similarly positioned apps actively competing and updating in this category as of 2026, checking current pricing and features directly before signing up — rather than relying solely on any single review, including this one — is a reasonable practice, since tier limits and pricing in this space have shown a pattern of changing without much notice.

---

This guide addresses access control, permission structure, and cost comparison. It does not evaluate the clinical or developmental accuracy of any app's tracking or prediction features beyond what's covered in this cluster's dedicated reviews.