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

# User Settings

User Settings is where you configure your personal credentials and defaults for how StepSecurity behaves when acting on your behalf. Settings here are scoped to you as an individual user, not to your organization or tenant.

### Opening User Settings

Click your avatar in the top right of the StepSecurity app and select User Settings.

<figure><img src="https://754495266-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FQJRZY4cfEeY3I7DXTOCp%2Fuploads%2FjTIQomXehuRhLe58z2BH%2FScreenshot%202026-05-25%20at%2013.31.52.png?alt=media&amp;token=36ffd6f6-38fb-4492-9726-aa85e4649fdf" alt=""><figcaption></figcaption></figure>

### Available sections

User Settings has four sub-pages:

* Personal Access Token: Store the GitHub Personal Access Token (PAT) that StepSecurity uses to orchestrate workflows on repositories you own
* Workflow Templates: Point StepSecurity at a GitHub repository that contains your own custom workflow templates, so they appear alongside the built-in ones during orchestration
* Orchestrate Options: Toggle the security controls that StepSecurity applies when it orchestrates a repository, such as restricting `GITHUB_TOKEN` permissions, adding `step-security/harden-runner`, and pinning Actions to full-length commit SHAs
* Pull Request: Customize the title, commit message, and description that StepSecurity uses on the pull requests it opens


---

# 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.stepsecurity.io/administration/user-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.