User

From Tygron Support wiki
Revision as of 12:18, 12 August 2015 by Rudolf@tygron.com (talk | contribs) (Created page with "{{learned|what users are|how users relate to the Tygron Engine|what the different types of users are}} ==User== Anyone that makes use of a piece of software is said to be a u...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Template:Learned

User

Anyone that makes use of a piece of software is said to be a user of that software.

How do users relate to the Tygron Engine

A user is anyone who is using the Tygron Engine. When someone is not currently using the Tygron Engine, 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 Engine, 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).

Player

A user who participates in a (non-editor) session is referred to as a player, participant, or simply as a user. A project may contain stakeholders matching some or all of its users. 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.

Facilitator

A user who facilitates a (non-editor) session is referred to as a facilitator or admin. They control the settings and progression of a project in a running session, using the Admin Interface. They can also be considered a participant, especially when interacting from the perspective of the Non-playable stakeholders. However, since this ability is limited and inherently included in the tasks of the facilitator, facilitator or admin is preferred.

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.

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.

User

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 above (for example, because they are simply testing their hardware via the main menu) are also simply referred to as user.