For SmartServer 4.2 and higher, see Defining Users. For SmartServer 4.1 (Beta), see Defining Users (Release 4.1). |
You can create and manage SmartServer user accounts if you are signed into a SmartServer account with system administrator, owner, or supervisor privileges. User account management includes assigning roles and capabilities of each user account. This section consists of the following:
You can create a user account to add a new user for a SmartServer. To create a new user account, follow these steps:
Click the Action button () and select the Create User action.
The Create User view appears.
Click the Expand button ( ) for a better view of this widget. |
Select the user type as follows:
User
The following table summarizes the capabilities of each user type:
Tasks | Owner | Supervisor | User (see note) |
---|---|---|---|
Modify CMS license limits with an activation key | √ | ||
Manage account information | √ | ||
Manage non-admin user accounts | √ | √ | |
Grant access to a geozone or context | √ | √ | |
Grant access to individual widgets | √ | √ | |
Deploy or delete custom apps | √ | ||
Add, provision, replace, or delete devices | √ | ||
Create and modify schedules | √ | ||
Perform actions within a widget if visible | √ |
User roles are assigned by the system administrator, owner, or supervisor and define what tasks a user can perform in the system.
|
Set the Automatic password generation option for the new user.
If enabled, the automatic password generation requires the SmartServer IoT to be connected to a network with Internet access. A notification containing the automatically-generated password is sent to the specified email address for the newly created user.
If disabled, the following view appears requiring you to specify a password.
|
To create an admin user type, follow these steps:
Click the Action button () and select the Create User action.
The Create User view appears.
Click the Expand button ( ) for a better view of this widget. |
Supply a Google API Key for maps display.
The Google API Key is used for access to Google Maps for maps display in the Locations widget (prior to SmartServer 3.4, the Locations widget was called the Map widget). The default admin user will have an embedded key. New admin users should be supplied with a key in order to view maps. The same key that is used for the default admin user can also be used for new admin users. |
Set the Automatic password generation option for the new admin user.
If enabled, the automatic password generation requires the SmartServer IoT to be connected to a network with Internet access. A notification containing the automatically-generated password is sent to the specified email address for the newly created user.
If disabled, the following view appears requiring you to specify a password.
|
The Apollo Owner user account is available by default as the primary CMS user for the SmartServer IoT.
To edit the CMS apollo user account, follow these steps:
For information on managing the apollo user password, see Changing User Passwords in the (Optional) Secure Your SmartServer section.
You can assign user permissions and roles by geozone. A geozone is a geographic region that you define on a map using the Planning widget. The SmartServer includes a default World geozone which represents a region for the entire world. To assign a user to a geozone and set the roles for the user in the geozone, follow these steps:
You can remove a user account to disable access to a SmartServer for a user. To remove a user account, follow these steps:
You can remove multiple user accounts to disable access to a SmartServer for the selected users (you will need to leave at least one user for system access). To remove multiple user accounts, follow these steps:
Select the users to remove.
Or, if you have many users on the system and want to remove all of them, you can use the Select All button () to select all users.
Note: If you are deleting all users from the system using the Select All button, then be sure to deselect (at least) the Apollo Owner user in order to leave at least one user for system access. |