> For the complete documentation index, see [llms.txt](https://www.cakewalk.security/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.cakewalk.security/docs/human-access/how-to-guides/auto-provisioning/how-it-works/configuration-settings.md). # Configuration Settings Agent Cake configuration is app-specific: each app's metadata, permissions and setup steps live in its integration guide. Agent Cake configurations are different for each application. Each app may require different metadata, permissions or setup steps: such as enabling API access, creating a service account or granting admin rights. There is no centralized configuration panel. Instead, app-specific requirements and instructions are documented in the corresponding [integration guides](/docs/human-access/connections-and-integrations/integration-guides.md). #### **Configuration options** When configuring Agent Cake, you can control how access is managed throughout the user lifecycle: **When Access is Granted:** * **Permissions**: Configure which permissions are automatically assigned * **App-specific metadata**: Set up default permissions, team assignments, etc. **When Access is Removed:** * **Permissions**: Select which permissions should be removed during access removal * **Deprovisioning strategy**: Agent Cake uses a **full removal** strategy removing user access from all teams, projects and resources in the application * **Special scenarios**: * If a user is the app owner, deprovisioning will be blocked and requires ownership transfer first * For apps that prompt for data transfer during user deprovisioning, Agent Cake uses the default option provided by the application to ensure data loss prevention --- # 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://www.cakewalk.security/docs/human-access/how-to-guides/auto-provisioning/how-it-works/configuration-settings.md?ask=&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.