> For the complete documentation index, see [llms.txt](https://docs.lithnet.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lithnet.io/okta-ma/configuration/global-settings.md).

# Global settings

The Global Parameters page, which controls group import and user lifecycle behavior.

![The Global Parameters page.](https://2206708376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F0u5rDWCokdBire3bUPyS%2Fuploads%2Fgit-blob-17707e3eb3ac8502c0e0ad30f1cd546fd4e63440%2Fmim-global-parameters.png?alt=media)

## Include built-in groups

Imports groups of the Okta type `BUILT_IN`. They are read-only.

## Include app groups

Imports groups of the Okta type `APP_GROUP`, which are created and owned by application and directory integrations. They are read-only.

`OKTA_GROUP` groups are always imported when the `group` object type is selected, and they are the only groups the management agent can create, update, delete, or change the membership of.

Run a Full Import and Full Synchronization after changing either setting, because both change what an import returns.

## User deprovisioning action

This setting applies when MIM exports a delete for a user. It changes what an import returns as well, so decide on it before you design your deprovisioning rules.

### Deactivate

This is the default. A staged delete deactivates the user in Okta but leaves it in place, where it can be reactivated or removed manually later.

Deactivated users are not presented to MIM at all, so a delta import confirms the delete.

### Delete

A staged delete deactivates the user and then permanently deletes it. A deleted user cannot be recovered.

Because deactivated users can be a normal, permanent state under this setting, they are imported like any other user. Only a full import can confirm the permanent delete, since Okta cannot return an object that no longer exists.

{% hint style="warning" %}
The management agent cannot reactivate a deactivated user. Under **Deactivate**, the object leaves the connector space, so a later reprovision is exported as a create, and Okta rejects it because the login is still in use. Reactivate the user in Okta first.
{% endhint %}

## Activate new users

Activates a user immediately after the export creates it. If you leave this off, new users stay in the `STAGED` state.

## Send activation email to new users

Instructs Okta to send its activation email to the new user. This only applies when **Activate new users** is selected.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.lithnet.io/okta-ma/configuration/global-settings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.