> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/arm/arm-features/ncino/feature-ci-jobs/running-a-ci-job/exclude-the-ownerid-from-automapping-in-ncino-ci-jobs.md).

# Exclude the OwnerID from Automapping in nCino CI jobs

## **Exclude the OwnerID from Automapping in nCino CI jobs**

To ensure user permissions differences between different environments will not affect the RBC deployments, users are provisioned to disable the auto assignment of users as they trigger the RBC deployments.

<figure><img src="/files/ETqWOMKpjyge12zXnzxy" alt=""><figcaption></figcaption></figure>

By default, the option is disabled, which signifies that the user permissions will be auto-assigned if another user continues to trigger a job that was initiated by a different user in another environment.

While triggering the RBC configuration deployment, you must explicitly disable the option to make sure that the users will not be auto-mapped.


---

# 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://knowledgebase.autorabit.com/product-guides/arm/arm-features/ncino/feature-ci-jobs/running-a-ci-job/exclude-the-ownerid-from-automapping-in-ncino-ci-jobs.md?ask=<question>&goal=<endgoal>
```

`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.