> 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/codescan/getting-started/users-roles-and-permissions/user-account.md).
# User Accounts
### Overview
As a CodeScan user, you have your own space where you can see the things that are relevant to you. View your personal space under the **`My Account`** page.
### Profile
It gives you a summary of your:
* Login
* Email Address
* Groups
* SCM accounts
### Security
Manage your own authentication tokens in this section. You can create as many tokens as you want. Once a Token is created, you can use it to perform analysis on a project where you have **Execute Analysis** permission.
### Notifications
Email notifications are managed here. It is possible to define your overall notifications settings applied to all projects. By default, email notifications are turned on for the following notification types:
* Background tasks in failure on my administered projects
* Changes in issues/hotspots assigned to me
* New quality gate status
* My new issues
{% hint style="info" %}
**Point to Note:**
1. A notification is never sent to the author of the event.
2. The author will not get notified about their own issues. It's only the assignee who gets notified and not the author.
3. The author/developer can look at their respective issues from the CodeScan UI.
{% endhint %}
### **Adding Notifications to a Project**
To add notifications for a specific project, select **`Add a Project`** and **`Search`** a project by name in the search menu. Two additional notification option types, especially applicable to team projects, are available on the per-project level:
* Issues resolved as false positive or won't fix
* New issues
### Projects
The **`Projects`** tab lists all of the projects you are administering. You can select a project from this tab for full access.
---
# 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://knowledgebase.autorabit.com/product-guides/codescan/getting-started/users-roles-and-permissions/user-account.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.
