---
title: Users
slug: reference/users
docTags: 
createdAt: 2025-09-03T12:56:51.368Z
---

Available at `Configuration > Users`, when viewing or editing a user, are the following fieldsets:

## User configuration

### Name

**Description:** The name of the user

### Password 

**Description:** The password for this user *(optional)*

### Description

**Description:** A description of the user *(optional)*

### First name 

**Description:** The user's first name *(optional)*

### Last name

**Description:** The user's last name *(optional)*

### Email  

**Description:** The user's email address *(optional)*

### Language

**Description:** Select the language of the interface for this user\*\*
**Default:** English

## User group configuration

Shows a list of groups this users belongs to. You can [add the user to a specific user group](docId\:P129QxI8jVE0utuuHGQNA) from this screen.

## Collector users

For every collector there will also be a corresponding collector user created. These users can not be deleted and can not be removed from or added to a user group.

## Default groups

Every organization gets four default groups: **Administrators**, **Managers**, **Reader** and **Collectors**.

### Administrators

They have almost all Historian privileges in this organization. Four privileges are deliberately not part of this group: managing users, managing organizations, reading organizations, and reading application logs. Members can read users but not create, edit or delete them.

### Managers

These users can manage everything, but can't access settings, audit logs, user groups, users or privileges, cannot read application logs, and cannot delete time series data.

### Reader

These users can view most things, but can't access settings, audit logs, user groups or prototypes.

### Collectors

The group that the automatically created collector users belong to.

## Tokens

### Session tokens

The session tokens correspond with all the active sessions the user is logged in on. Removing the session token will log the user out on that device.

### API tokens

API tokens can be used to communicate with the Factry Historian API, the token will have the same privileges as the user. These are the tokens used by the collector users and by the Factry Historian Grafana datasource to communicate with the API.

## How-Tos

For more information on how to manage your users, please consult these guides:

- [Creating a local user](docId\:psMMI93E4xutD2zxcqYNA) 
- [Managing a user](docId\:P129QxI8jVE0utuuHGQNA)