Each household system — Crestron, the Lutron app, UniFi Access, and Alarm.com — has its own separate user-permission model, so giving a housekeeper, nanny, or driver "just enough" access means configuring each platform individually rather than assuming one login covers everything. The practical approach is to assign every staff member the lowest access tier each platform offers, scope door and alarm credentials to the hours and areas they actually work, and keep a single written list of every account tied to that person so nothing gets missed when they leave. Done this way, offboarding becomes a checklist you run through system by system rather than a guess about what someone might still be able to reach.
What access level should staff get on Crestron Home?
Crestron Home's control system supports distinct account types rather than one shared login. The system distinguishes Admin credentials (used to sign into the Crestron Home Setup app), Advanced User credentials that give homeowners limited access to setup and configuration screens, and User Interface Device credentials that let touch screens, remotes, and phones join the system at all — and Crestron's documentation notes that resetting any of these after a password reset event removes the Admin username and every other user from the system, requiring everyone to be re-added. On a 4-Series control system more broadly, Crestron's authentication model is group-based: accounts are added to local groups with a predefined access level — Administrator, Programmer, Operator, User, or Connection Only — and a user's effective rights are the combined rights of every group they belong to. According to Crestron's 4-Series authentication manual, the User access level only grants connection to the device's Web XPanel interface, with no administrator, programmer, or operator rights — which is the level that fits a driver or nanny who needs to tap scenes on a wall panel but should never reach system configuration. Removing someone is a single command (deleteuser) that also pulls them out of every group they belonged to, which is the piece that matters at offboarding: a departing staff member's control-system account can be deleted in one step rather than hunted down room by room.
How does the Lutron app handle shared household access?
Lutron's consumer app model is built around a single homeowner-level login rather than Crestron's tiered group structure. According to Residential Systems' coverage of Lutron's app redesign, the current Lutron app presents a room-organized dashboard of scenes and device status, and gives the homeowner access to their installer's contact information directly from the app. Because the Lutron ecosystem does not publish a separate staff-tier login in that interface, the practical move for a housekeeper or nanny who only needs to turn on a few rooms is a dedicated keypad or a limited scene assigned to their hours, rather than handing over the same app credentials the homeowner uses — that question is worth raising directly with your integrator, since the right answer depends on which Lutron platform (RadioRA 3, HomeWorks QSX) and app version is installed.
How should door credentials and alarm codes be scoped per person?
Alarm.com's system-user model is built for exactly this kind of per-person control. Alarm.com's knowledge base on creating a system user code describes assigning each person their own named access code, then toggling which devices — panel partitions, individual locks — that code can actually operate, so a driver's code can unlock a garage or gate lock without granting access to interior doors. Alarm.com also supports randomly generated user codes that can be shared by text or email directly from the app or customer website, with the share message including which devices the code reaches and the access timeframe — useful for a seasonal employee whose access should expire on a known date rather than requiring a manual follow-up.
The same per-person logic should extend to UniFi Access door schedules and to camera-viewing permissions: a house manager may need to see every camera, while a housekeeper or driver typically only needs the doors and areas tied to their job, not the family's private spaces. Ask your integrator how UniFi Access schedules and camera-group permissions are structured in your specific installation, since the exact options depend on hardware and firmware version.
Should staff devices share the family Wi-Fi network?
Separating a staff or guest network from the family's trusted devices and AV/control traffic is a standard practice in enterprise-grade home networking, where VLANs keep different device classes from reaching each other even on the same physical network. Putting staff phones and tablets on a separate network segment from the Crestron processors, NAS, and family devices limits what a compromised or lost staff device could reach, independent of any door or alarm permissions that device's owner also holds.
What belongs on a staff offboarding checklist?
A single offboarding checklist should pull together every system a departing staff member touched: delete or deactivate their Crestron user account (and confirm they are no longer in any group), remove or disable their Alarm.com user code and confirm the toggle for every device it reached, revoke their UniFi Access credential and move their Wi-Fi device off the staff VLAN, and change any shared keypad codes or Lutron scene assignments tied specifically to their schedule. Keeping that list in one place — rather than relying on memory across four separate apps — is what prevents an old code or stale credential from sitting active for months after someone leaves.
Cave Group designs residential systems around Crestron for control and Lutron for lighting and shades, and builds UniFi networks with the VLAN separation this kind of role-based access depends on; ask about staff access planning as part of your residential design, or review support options for ongoing account management after handoff.
Frequently asked questions
Can a housekeeper's Crestron account be limited to just a few rooms?
Crestron 4-Series accounts are assigned to local groups with a defined access level — the User level grants only Web XPanel connection rights, with no administrator or programmer access — so a staff account can be scoped well below the homeowner's Admin or Advanced User credentials.
Does the Lutron app support separate staff logins?
The current Lutron app is built around a homeowner-level dashboard with room-organized scene and device status rather than a published separate staff-tier login; ask your integrator whether a dedicated keypad or limited scene assignment fits your platform better than sharing app credentials.
Can a door or alarm code be set to expire automatically?
Alarm.com lets each user code be scoped to specific devices and shared with a defined access timeframe, which supports giving a seasonal or temporary staff member a code that aligns with their actual employment dates rather than requiring a manual revoke later.
What happens if staff and family devices share one Wi-Fi network?
Without network segmentation, a staff device sits on the same trusted network as family devices and control-system traffic; VLAN separation in an enterprise-grade home network keeps those device classes apart regardless of door or alarm permissions.
What is the fastest way to remove someone's access after they leave?
A written offboarding checklist that covers the Crestron account, the Alarm.com user code and its device toggles, the UniFi Access credential and Wi-Fi VLAN assignment, and any shared keypad or scene codes in one pass is more reliable than removing access system by system from memory.