# Users & Roles
ZauberCMS uses the built in Identity system to .Net and Blazor, there are some quirks using it with Blazor, and you can read more below.
{% content-ref url="../identity" %}
[identity](https://aptitude.gitbook.io/zaubercms/identity)
{% endcontent-ref %}
### Users
Users lists everyone who has registered for your website, whether they are an admin or not. You can filter via role, and click on the user to edit their content (See below) or change their roles, to update their email address.
### Roles
Roles work like any other .Net application, and you can create specific roles for specific use cases. When there are no users on the site (i.e. First install) the first user to register will be assigned an admin role and you will be redirected to the admin.
Any subsequent user who registers, will be assigned the default role (Member) that is set in the appSettings.
```
"NewUserStartingRole": "Member",
```
If you want users to use a different default role name, then change it here.
### User & Role Content
Just like Content, you can assign Content Types to roles. So any user in a specific role will get that content.
This is different from the main content, as you can add many roles to a user, meaning the User will get all the properties from all Roles. If a role is removed, the properties are removed.
#### Querying / Getting Data
You use exactly the same syntax with a User as you do Content to get the data, read the below
{% content-ref url="querying-data" %}
[querying-data](https://aptitude.gitbook.io/zaubercms/creating-a-website/querying-data)
{% endcontent-ref %}
Example of adding an RTE to a Role
Example of the RTE being shown on a User in the Admin role
---
# Agent Instructions: 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:
```
GET https://aptitude.gitbook.io/zaubercms/creating-a-website/users-and-roles.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.
