> For the complete documentation index, see [llms.txt](https://support.incidents.cloud.solarwinds.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/manage-users/types-of-users.md).
# Types of Users
Squadcast has **three different types of users**:
### Account Owner
Squadcast allows only one Account Owner per Organization. An Account Owner has all the privileges in that Organization and by default will also be responsible for the billing of the account.
{% hint style="info" %}
The user that first signs up for the account & creates an Organization is by *default* the `Account Owner`. Learn about transferring ownership of the account to another user, [here](/~/changes/lGFY3mJPy207GveiFTeX/manage-users/change-account-owner.md#transferring-account-ownership).
{% endhint %}
{% hint style="warning" %}
Each Squadcast Organization can have only **one** `Account Owner` type of user.
{% endhint %}
### User
Users, by default, have the ability to customize their Profile, Notification Rules, Respond to, and resolve incidents. Typically, Users are the Engineers, SREs, Systems Engineers or anyone in your team that handles incident management & on-call.
### Stakeholder
As the name implies, these are typically other participants from the Organization who may have an interest in the incident management process. They could be Product Managers, Customer Support Representatives, CxOs, and so on.
Stakeholders have **view-only access** to all incidents. This means that Stakeholders are **not notified by default** for any of the incidents created in Squadcast. If Stakeholders need to be notified of incidents, [this](/~/changes/lGFY3mJPy207GveiFTeX/incidents-page/incident-notes.md#mentioning-users-squads-and-teams-in-notes) is how it can be done.
Stakeholders also have the ability to create manual incidents should they notice something wrong and want to notify the on-call team of it.
{% hint style="warning" %}
**Important:**
* Stakeholders will not receive SMS/Phone call notifications for incidents in Squadcast.
* Stakeholders cannot be added to Schedules or Escalation Policies.
{% 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://support.incidents.cloud.solarwinds.com/~/changes/lGFY3mJPy207GveiFTeX/manage-users/types-of-users.md?ask=&goal=
```
`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.