User: Difference between revisions
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
A user who participates in a (non-editor) session is referred to as a participant, or simply as a user. A project may contain stakeholders matching some or all of its users. | A user who participates in a (non-editor) session is referred to as a participant, or simply as a user. A project may contain stakeholders matching some or all of its users. | ||
These users are often stakeholders with a vested interest in the case modeled in the project. They can participate in the urban development process within the safety of the | These users are often stakeholders with a vested interest in the case modeled in the project. They can participate in the urban development process within the safety of the [[project]] [[session]], mirorring their real world interests. They use the indicators of a project as their goals, and their actions as their means of attaining those goals. A user needn't necessarily partake as themselves. For instance, a representative from the municipality can take on the role of a project developer in a session. The user can then be referred to as the project developer. | ||
===Editor=== | ===Editor=== | ||
Revision as of 17:14, 30 January 2023
A user is anyone who is using the Tygron Platform. When someone is not currently using the Tygron Platform, but has a valid account and intends to use it again, that person is also referred to as a user. It is a broad term, which is further narrowed depending on what the user's current actions are. "User", and the more specific variations, refer to the actual people (or programs) interacting with the software.
Types of users
The term user can be used to refer to all people using the Tygron Platform, but it is often useful to differentiate between different users. Depending on what the user is currently doing, a user can be referred to using a number of terms. Users can be different kinds of users in different sessions (even when those sessions are running at the same time). A user with an (active) account, but who is not using the software, is simply referred to as a user. Users who are logged in, but who are not currently part of one of the definitions below (for example, because they are simply testing their hardware via the main menu) are also simply referred to as user.
Participant
A user who participates in a (non-editor) session is referred to as a participant, or simply as a user. A project may contain stakeholders matching some or all of its users.
These users are often stakeholders with a vested interest in the case modeled in the project. They can participate in the urban development process within the safety of the project session, mirorring their real world interests. They use the indicators of a project as their goals, and their actions as their means of attaining those goals. A user needn't necessarily partake as themselves. For instance, a representative from the municipality can take on the role of a project developer in a session. The user can then be referred to as the project developer.
Editor
A user who uses the editor to create or edit an existing project is themselves also referred to as an editor, an editing user, or an editor user. They require an account with at least editor rights.
Editors's are tasked with implementing the details of a case into a project in the Tygron Platform. They should either collect or receive the data required, and input this data using the editor. Editors with a technical background (such as programmers) will find it easier to create more complex scenario's using the Tygron Platform's functionalities.
User administrator
A user with an account with sufficient rights to manage user accounts is referred to as a user administrator, or simply administrator. These users can manage all projects and users in their domain, and, when present, should be any other user's first point of inquiry regarding their accounts, rights, projects, and license.
In most cases, the license holder's account also permits them to manage their domain. This allows them to configure and distribute accounts to the people in their organisation who should be able to create or use projects. They are also responsible for cleaning up older projects in their domain, so that the allowance of their license can be reused for new projects.