Skip to content
AscendCore
Back to Runbook Library
Provisioning Template: configurable per customer

Contractor Onboarding

Provision a time-boxed contractor account with scoped access and an automatic end-date deactivation, approval-gated and audited.

Integrates with

OktaM365

The problem

Contractor accounts are easy to create and easy to forget. When the engagement ends, the account often stays active because nobody owns the cleanup, leaving access open well past the contract.

What AscendCore does

A requester provides the contractor details and an end date. AscendCore proposes a scoped account that deactivates automatically on that date, routes it for approval, and schedules the deactivation. Creation and the scheduled end are recorded in the audit chain.

Status

Template. Access scope and approval routing are configurable per customer. Connect it to your Okta and Microsoft 365 tenant to enable.

Runbook source preview

Versioned, deterministic, auditable

Every runbook is defined as a versioned YAML manifest with explicit triggers, steps, and approval policies. The runbook itself is the audit-ready record of what AscendCore can and will do. Chat is just the interface that triggers it.

name: contractor-onboarding
trigger:
  channels: [slack, teams]
  intents: [contractor_onboard]
steps:
  - create_account_with_end_date
  - assign_scoped_access
  - admin_approval
  - schedule_auto_deactivate   # on engagement end date
approval:
  required: true
  approvers: [it-admins, hr-ops]
Want this runbook?

Configure contractor onboarding for your environment

Templates are configurable per customer environment. Talk to us about the specific systems and approval flow you need.