Help the first day feel ready—and changes stay controlled.

Identity and access: define the entitlement before the trigger.

Dragon offers identity and access capabilities, including supported single sign-on and app provisioning. Begin with the applications and access patterns your IT team needs to manage. A job title alone may not explain which permissions someone should receive.

Define role-based expectations, exception approval and the systems that remain outside the selected connection. Confirm whether each application supports the actions you need, such as creating an account or changing access. An integration name does not establish every capability, and an automated task should not widen access beyond an approved purpose.

Devices: match the controls to the equipment.

Device-management capabilities can support selected equipment, operating systems and policy controls. Inventory the devices your people actually use before evaluating a configuration. Review ownership, remote-work patterns and how IT will support exceptions.

Agree on appropriate policies and employee communications before rollout. Define who can apply controls, how a problem is investigated and what happens when a device cannot complete the expected process. Device management is one part of an IT program, not a universal guarantee of security or compatibility.

Inventory: account for the physical handoff.

Inventory and device logistics capabilities can help coordinate equipment across the employee lifecycle. Confirm the available services, supported geographies and operational terms before assuming procurement, storage, shipping or recovery are included.

A useful equipment record identifies ownership and status, but the real-world handoff still needs a process. Establish who confirms receipt, reports a problem and follows up on a return. Explain the employee’s next step so a missing package or unclear instruction does not become a first-day surprise.

An illustrative joiner, mover and leaver sequence.

For a new hire, HR confirms an approved start and relevant role information; IT reviews the access and equipment plan; assigned tasks track what is ready and what needs attention. The employee receives clear instructions about the tools and support channels they will use.

For a role change, review whether access should be added, removed or retained rather than only adding the new permissions. For a departure, coordinate the approved timing of access changes and equipment handling with the appropriate owners. These are design examples; actual automation and timing depend on selected capabilities and policy.

Connect Microsoft 365 and Google Workspace to the employee lifecycle.

Software access and paid licenses should be part of the same joiner, mover and leaver conversation. Through Dragon, connect supported Microsoft 365 and Google Workspace account and group administration with employee context. Reseller purchasing and billing are a different arrangement from integration-only access management; adding an integration does not mean subscriptions are purchased through Rippling or Dragon.

During onboarding, agree on the account, access and license someone needs. At a role change, review whether that combination still fits. At departure, check both access and the paid seat: Microsoft offboarding policies may be configured to remove licenses, while suspending a Google Workspace account does not itself remove its license. The described Google flow leaves license removal to an administrator in Google Admin Console.

Coordinate this work with finance’s subscription and renewal review. Existing subscriptions, transfer timing and commercial eligibility can require separate handling; not every subscription transfers automatically. We can help frame the operating questions, while authorized resale scope, supported plans and support responsibilities must be confirmed for the arrangement you choose.

Keep what works in your existing IT environment.

Your organization may already have an identity provider, device-management platform or asset process that works well. Evaluate which capability is missing and whether a supported integration or a targeted addition addresses it. Do not create two competing owners for the same control without a clear reason.

Bring your IT team into the discussion early. HR can provide lifecycle context; IT should validate application coverage, operating-system support, permissions and operational safeguards. The decision should reflect the actual environment rather than a generic product diagram.

• Which applications and device types are in scope?
• Which system is authoritative for identity and each control?
• Who approves access exceptions and reviews accumulated permissions?
• What happens if an employee event or integration fails?
• How do employees get help during onboarding or equipment changes?