User Accounts and Permissions
This manual is in pilot operation.
|
Each user who uses fusion_place needs to be given a user account.
User Account Name
The user account name is used to uniquely identify the user account. The user account name can be up to 50 characters long and can use alphanumeric characters, periods (.), underscores (_), and hyphens (-). Case sensitivity is observed.
The user account name must be unique within the system (not per application). Once a user account is set up, it can be used in any application.
Password
Each user account can have a password set between 5 and 50 characters. Alphanumeric characters and most special characters can be used, but Japanese characters and the like cannot[1]. Passwords are case-sensitive. Passwords can be changed by both the administrator and the user assigned to the account.
The administrator can check the latest password change date.
Permissions
The following permissions can be granted to each user account.
Basic Permissions
Basic permissions include three types: designer permission, administrator permission, and query-only user permission.
- Designer permission
-
The authority to add, change, and delete design objects and administration objects using the [Manager].
- Administrator permission
-
The authority to add, change, and delete administration objects using the [Manager].
- Query-only user permission
-
The authority to use fusion_place limited to data query functions. Query-only users are considered a type of permission because, although they have limited capabilities, they receive special license considerations.
Only one of the designer permission, administrator permission, or query-only user permission can be granted.
| Designer permission includes administrator permission. |
A user account that has none of the three permissions granted has the authority to handle all general operations focused on data input and output (excluding design and management). This, together with query-only users, is referred to as operational users. They may also be referred to as "general users."
Additional Permissions
Users with either designer or administrator permissions can also be granted the following permissions:
- User management permission
-
The authority to add, change, and delete user accounts.
- License management permission
-
The authority to generate license purchase orders and incorporate license agreements[2].
- Processing record management permission
-
The authority to delete master maintenance logs and ledger update histories.
- Application-specific permission
-
This is more of a restriction than a permission. Designers and administrators granted this restriction can only design and manage specified applications. The specific applications for which they have authority can be specified in the Design and Management Permission Table for each application.
| Users with user management permission can grant themselves any permissions. Therefore, they effectively have all permissions, so please be aware of this. |
Disabling User Accounts
Designers and administrators with user management permission can temporarily disable individual user accounts. A disabled user account cannot use fusion_place, and disabled user accounts are not included in the user count for license agreements.
Disabling is a temporary measure. After disabling a user account, it can be re-enabled. In that case, the user account will retain the permissions it had before being disabled.