> For the complete documentation index, see [llms.txt](https://help.sdocs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sdocs.com/sdocs/maintenance-and-troubleshooting/legacy-workflows/s-doc-jobs-legacy/s-docs-jobs-testing/testing-as-another-user.md).

# Testing as Another User

We often come across instances where the SDjob or flow is being run as another user. Fortunately, we can minimize in-depth testing to focus on the document generation.

Enable **Let admins debug flows as other users**

This option will enable the user the ability debug flows as other users.

1. Navigate to Setup
2. Type ‘Process Automation Settings’ in the quick find.
3. In Process Automation Settings, enable the option: **Let admins debug flows as other users**

{% hint style="info" %}
You may want to ask clients before proceeding for confirmation the option can be enabled.
{% endhint %}

## Create a simple flow

This portion is dependent on how the user is leveraging our product. If the user is creating SDjob records, leverage the flow to create an SDJob record.

## Debug the flow

If the organization wide setting is checked, System admins will have the option Run flow as another user. This can be done directly in the flow itself.

1. Open the simple flow.
2. Click the Debug button
3. Check the box **Run flow as another user**
4. Run the flow.

{% hint style="info" %}
If the flow is kicked off as the other user, the SDJob will be created as the other user, also.\
This also works on users that are part of the experience cloud.
{% endhint %}


---

# 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://help.sdocs.com/sdocs/maintenance-and-troubleshooting/legacy-workflows/s-doc-jobs-legacy/s-docs-jobs-testing/testing-as-another-user.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.