Skip to content

Choose a lifecycle guide

WC365 Lifecycle Reference

Choose the guide for the employee change you need. It explains what to enter, which approvals apply and what WorkCycle365 does next.

Lifecycle Use it when Key characteristic
Hire A person is joining the organization Uses staged identity and start enablement approvals.
Transfer An existing employee’s manager or organizational assignment is changing Applies the approved change at its effective time. For a revert, select Temporary Assignment and enter Assignment End. An end date without Temporary Assignment creates a Contract End request.
Leave An existing employee is beginning a leave Choose Departure, then select Leave. Enter Return Date to schedule a separate Return.
Return An employee is coming back from leave Re-enables configured access at the approved return time.
Extension A planned contract end needs to move Processes immediately without approval. Handles one eligible upcoming Departure; enter New End Date to schedule a replacement, or leave it blank when no replacement is required.
Departure and Immediate Access Removal Employment or access is ending Coordinates planned offboarding, resignation, contract end, leave, or urgent access removal.
  1. Request: The requester enters the person, lifecycle, and timing.
  2. Validate: WorkCycle365 checks the submitted details.
  3. Approve: An assigned person makes a decision when the lifecycle requires approval.
  4. Schedule: Future-dated work waits for its effective window.
  5. Act: WorkCycle365 performs the configured Microsoft 365 actions.
  6. Communicate: Applicable email, Microsoft Teams cards, and calendar events are produced.
  7. Record: Request status shows progress. Operational logs support troubleshooting when something goes wrong.

The steps differ by lifecycle. Hire has two approval stages; Extension processes without approval.

  • Confirm the correct person and request type.
  • Check the effective date and time.
  • Use the visible form to identify required fields; tenant configuration and lifecycle type influence what applies.
  • Submit one request and wait for the portal’s success or error message. The portal does not display a request reference in that message.
  • Use the view available to your role when you need to follow or change a request. Those views do not include every request, so do not submit again just because it is not listed.
  • The success message acknowledges submission. Approval, scheduling and lifecycle work happen separately; report an error or an overdue request through your normal support route.

See the requester quickstart for the complete submission checklist.

See timing and scheduling for time fields, business-hour defaults, time zones and when scheduled work begins.

Identity groups, licensing support, calendar destinations, Microsoft Teams channels, email templates, approvers, and scheduling conventions are configured per tenant. Check the relevant guide and ask your administrator which settings apply to your organization.