The situation
A departing employee owns important documents and has accounts outside central identity.
Joiner, Mover & Leaver Workflows
JML governs how access changes when someone joins, changes responsibility or leaves. The workflow must connect an approved trigger to action, verification and handling of exceptions.
- Agree the authoritative event
- Coordinate application actions
- Verify completion
Is this right for you?
When this is the right work.
Employee changes create repeated manual work or uncertainty over access removal, shared records and unused licenses.
The first conversation establishes the environment, the constraint and who will accept the result. We agree a bounded starting point before expanding the engagement.
Scope
What DotConn delivers.
- 01
Agree the authoritative event
Define who approves a start, role change or departure, and when the change takes effect.
- 02
Coordinate application actions
Scope provisioning, removal, ownership transfer and credential handling across supported tools.
- 03
Verify completion
Record completed actions, unsupported integrations and the person accountable for unresolved access.
Deliverables
What you receive.
Acceptance criteria identify the checks, records and handover needed for the agreed scope.
- Lifecycle policy and application action map
- Supported automation and exception workflow
- Verification and handover records
In practice
A practical example.
Our approach
We separate access cutoff from data-retention decisions and coordinate application-specific actions.
The useful result
The customer can see verified completion and the exceptions still requiring action.
Responsibility
Agree the responsibility.
DotConn
Assesses and delivers the technical work in the agreed scope, with reviewable changes and handover. Continuing operation requires a separately defined managed-service scope.
Your team
Provides authorized access, business priorities and accountable decision-makers; approves policy choices and accepts the agreed result.
Set this boundary early
Zero-touch behavior depends on reliable triggers and supported integrations. Account deletion and data retention require explicit customer decisions; automation must not guess them.
FAQ
Questions worth resolving.
Should the workflow delete accounts immediately?
Not by default. Access cutoff, data preservation, retention and eventual deletion are separate policy decisions.
Pricing, timing and how to prepare are covered in working with DotConn.
Connected work
Services that work alongside this.
Workplace Identity & Access Management
Workplace IAM manages employee and contractor access across organizational tools. It connects identity, SSO, MFA, roles and approval to the responsibilities people actually hold.
ExploreSaaS License & Renewal Optimization
SaaS optimization connects licenses and subscriptions to real ownership and usage. It makes renewal, seat changes and access decisions reviewable without assuming that every unused-looking account should be removed.
ExploreSecret Rotation & Credential Lifecycle
Secret rotation changes credentials and coordinates the systems that depend on them. A safe lifecycle includes ownership, distribution, expiration or revocation and validation that the intended service still works.
ExploreGoogle Workspace Management
Workspace management governs the organization’s collaboration environment: administration, access, sharing and the security settings supported by its subscription and operating needs.
Explore