---
title: Introduction
slug: GRYg-introduction
docTags: 
createdAt: 2025-07-24T03:49:27.540Z
---

This guide provides the initial setup instructions for the **Activate Identity & Access Manager – Create User** task.

This task enables automated user onboarding either through a business-user-driven web form or automatically via an HRIS connector.

By the end of this guide, you’ll have created your first user via Activate.

# Overview

The **Create User** task automates the provisioning of new users across on-premises and cloud environments. It can integrate with HR systems, enforce naming conventions, and apply role-based access automatically.

# Features

The Create User task performs the following actions:

- Creates a new user object in **Active Directory** and optionally in **Azure AD** 
- Sets a **one-time password** for secure initial access 
- Assigns a **manager** in AD for future approval workflows 
- Provisions an **on-premises or Exchange Online mailbox** 
- Configures a **home drive and profile folder** 
- Adds the user to **Activate roles**, which may include default AD and Microsoft Entra ID group memberships 

# Prerequisites

Before configuring the Activate Identity & Access Manager, several prerequisites must be met to ensure a smooth and compliant implementation. The following sections outline the key preparation tasks and permissions required.

## Platform Preparation

### Understand Your Environment

Determine the overall environment architecture and directory setup:

- **Architecture Type:** On-Premises Only, Hybrid, or Cloud Only 
- **Directory Structure:** Identify key organisational units (OUs) and naming hierarchies 

### Identify the Source of User Data

Define where new user information will originate:

- **Manual Entry:** Data entered directly via Activate web forms 
- **HRIS Integration:** Data sourced automatically from an HR system (e.g., Workday, SAP SuccessFactors) 

### Gather Key Configuration Data

Before setup, confirm and document the following:

- Mailbox naming convention (e.g., firstname.lastname\@domain.com) 
- Email alias format and supported domain names 
- Naming standards for SAMAccountName and logins 
- Department and Location structure for entitlement assignment 
- Source system readiness — ensure directories, HR systems, and service accounts are accessible 
- Password policy and complexity rules 

## Permissions and Access Requirements

The required permissions vary depending on the selected architecture (On-Premises, Hybrid, or Cloud).

Refer to the **Active Directory Permissions** and **Required Permissions Reference** documents for detailed guidance on permission assignments.