> For the complete documentation index, see [llms.txt](https://docs.yansalabs.com/okta-orchestrator/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yansalabs.com/okta-orchestrator/technical-docs/general-settings.md). # General Settings The following settings are available in the **General Settings** module to allow customization of application behavior. * **Okta user access entity**: A reserved [Access Entity](/okta-orchestrator/technical-docs/access-provisioning/access-entities.md) used for Okta user access. Typically, this should not be changed. * **Okta admin access entity**: A reserved [Access Entity](/okta-orchestrator/technical-docs/access-provisioning/access-entities.md) used for Okta admin access. Typically, this should not be changed. * **Default Okta admin role**: Default admin role that will be used when assigning Okta admin privileges to a user (May be overridden for specific requests). * **Logging level**: Level of logging verbosity for Okta Orchestrator within ServiceNow. * **Provisioning model**: Determines who is responsible for provisioning new user accounts within ServiceNow during a new user creation request. * **Okta provisions ServiceNow users**: Allow Okta to provision ServiceNow user accounts * **Okta does NOT provision ServiceNow users**: Do not allow Okta to provision ServiceNow users. Instead, ServiceNow will provision users locally as part of workflow. * **Okta active states**: The set of Okta states that are considered 'active' such that new [Access Entities](/okta-orchestrator/technical-docs/access-provisioning/access-entities.md) can be assigned and [Attestation](/okta-orchestrator/technical-docs/attestation-tracking.md) renewals can process. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.yansalabs.com/okta-orchestrator/technical-docs/general-settings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.