> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lumos.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Some Create Account Tasks Require Manual Verification

This article aims to provide context for error tasks that may display in your Just-In-Time (JIT) provisioning workflows when working with invite-based apps.

## Overview

Some integrations create accounts using an invite-based provisioning model.

In these cases, Lumos successfully sends the account creation request, but the application:

* Returns a provisioning status of `PENDING`
* Does not return a permanent account ID
* Requires the end user to accept an invitation or activate their account

Until the user completes that step, the account is not fully created in the downstream application.

When this happens, Lumos creates a task to ensure the workflow in Lumos is not completed prematurely.

***

## Why This Happens

Certain applications do not immediately create an active account when a new user is provisioned. Instead, they:

1. Send the user an invitation email
2. Wait for the user to accept the invite or activate their account
3. Finalize account creation only after that action

Because the account does not yet exist in a fully provisioned state, the connector cannot return a stable account ID to Lumos.

As a result:

* Provisioning status is marked as **Pending**
* The workflow pauses
* A manual task is created for the application admin

This is **expected behavior**, not a provisioning failure.

***

## What To Do

If you receive a task related to pending account creation:

### Step 1: Confirm the Invite Was Sent

Check the application’s admin console to verify that:

* The user appears in an **Invited** or **Pending** state
* An invitation email was successfully sent

If needed, you may resend the invitation from the application.

### Step 2: Wait for the User to Accept

The user must:

* Click the invitation link in their email
* Activate or create their account
* Complete any required verification steps

Until this happens, provisioning cannot complete.

### Step 3: Verify the Account Exists

After the user accepts:

* Confirm the account now appears as **active** in the application
* Ensure the account is fully created (not still pending)

### Step 4: Run a Sync in Lumos

Once the account is active:

1. Trigger a sync for the application
2. Confirm the account is discovered in Lumos
3. Match the account to the correct identity (if needed)

### Step 5: Complete the Task

After the account is successfully synced and matched in Lumos:

* Mark the task as complete
* The workflow will resume automatically

***

## Affected Integrations

The following connectors use invite-based provisioning and may return a `PENDING` status until the user takes action:

* **Calendly**
* **Cloudflare**
* **GitHub**
* **GitLab**
* **GitLab (Token)**
* **GitLab (Multiauth)**
* **Postman**
* **SharePoint (Microsoft 365 Guest)**
* **Zoom**

All of these applications require the end user to accept an invitation or activate their account before provisioning is finalized.

***

## Frequently Asked Questions

### Is this an error?

No, it's not a true error. This is expected behavior for invite-based applications.

True errors (API failures, permission issues, token expiration, etc.) will generate a separate integration error message.

### Why doesn’t Lumos just wait automatically?

Because the application does not return a permanent account ID while the invitation is pending, Lumos cannot safely assume the account will be created. Admin verification ensures:

* The user actually accepted the invite
* The account exists
* The account is properly matched to the correct identity

### What happens if the user never accepts the invite?

The account will remain in a pending state within the application. Many applications:

* Expire invitations after a set period
* Allow admins to resend invitations

Provisioning will not complete until the user accepts.

### Can this be automated?

In invite-based models, finalization always depends on user action. However, once the account is active, syncing and matching in Lumos completes the process cleanly.