Difference between revisions of "User"

From Request Tracker Wiki
Jump to navigation Jump to search
m (2 revisions imported)
 
 
Line 1: Line 1:
An RT user is identified by their e-mail address.
An RT user is identified by their e-mail address and a username. Each user is also assigned an id by RT, but this id is typically hidden in the RT interface and is not usually used directly.


A user with the '''Let this user access RT''' attribute (known as "unprivileged users") can use the [[SelfService]] web interface to see [[Tickets]] they raised and their full history.
A user with the '''Let this user access RT''' is an active user, meaning they can login (if they have a password) and perform actions in RT. Uncheck this option to disable the user account.


[[Staff]] (formerly known as "privileged users") have the '''Let this user be granted rights''' attribute and can access the full web interface to modify [[Tickets]].
Selecting the checkbox 'Let this user be granted rights (Privileged)' on the user administration page makes a user [[Privileged]]. It is also possible to set various configuration options to make new users Privileged when they are created. Privileged users can access the full web interface and can see and modify objects in RT based on their [[Rights]].


A user can have [[Rights]].
If you leave this checkbox unchecked, the user is [[Unprivileged]]. They can still log in if they have a password and they will see the [[SelfService]] interface.


A user can be a member of a [[Group]].
A user can be a member of a [[Group]].


A user with the global user right [[SuperUser]] can do anything.
A user with the global user right [[SuperUser]] can do anything.

Latest revision as of 09:09, 1 September 2021

An RT user is identified by their e-mail address and a username. Each user is also assigned an id by RT, but this id is typically hidden in the RT interface and is not usually used directly.

A user with the Let this user access RT is an active user, meaning they can login (if they have a password) and perform actions in RT. Uncheck this option to disable the user account.

Selecting the checkbox 'Let this user be granted rights (Privileged)' on the user administration page makes a user Privileged. It is also possible to set various configuration options to make new users Privileged when they are created. Privileged users can access the full web interface and can see and modify objects in RT based on their Rights.

If you leave this checkbox unchecked, the user is Unprivileged. They can still log in if they have a password and they will see the SelfService interface.

A user can be a member of a Group.

A user with the global user right SuperUser can do anything.