Adding and editing users in a self-hosted environment

Note: This procedure does not apply for Oracle-hosted installations, unless you are a superuser. For more information, see Adding and editing a user in an Oracle-hosted environment.

1. To use single sign-on for authentication is a self-hosted environment, create the user in your single sign-on application.

2. Click Settings.

The Settings page appears.

3. In the Manage Users section, click Edit Users.

The Users page appears.

4. To add a user:

A. Click Add a New User.

The Add User page appears.

B. Fill in the fields.

5. To edit a user:

A. Locate the user in the table.

B. Click the row menu () for the user, and then click Edit.

Note: You can edit only users in your login group.

The Edit User page appears.

C. Fill in the fields.

6. Click Save.

Your changes are saved.

7. Provision newly created users with roles and permissions.

Note: If you selected a user profile, the user is already provisioned with roles and permissions.

8. If you plan to use the Topics feature of Empirica Signal, optionally do the following for newly created users:

A. Add the user to one or more work teams.

B. Assign work team permissions to the user.

Field descriptions

Field	Description
Authentication	Authentication method.
Username (Add User page only)	Unique name of the user account (up to 100 characters). You can reuse deleted user names. Does not apply if LDAP authentication is used. For more information, see About user names.
First Name	First name of the user (up to 64 characters).
Last Name	Last name of the user (up to 64 characters).
Email	Email address of the user. This address (or addresses, separated by a comma) is used: As the default email address if the user chooses to be notified of data mining run completion notification. When a message is generated by a topic email notification rule. When you use the Send Message to All Users link on the Settings page. It is recommended that all users have an associated email address.
User Profile	The user profile, or set of attributes (login group and quota), user roles, permissions, and default user preferences that can be applied to users. The default is determined by the site option Default user profile.
Quota	Maximum amount of server space in megabytes (M) that the user is permitted to use for creating runs. If this limit is exceeded, the user cannot submit new runs (or re-runs). To indicate an unlimited amount of storage space, leave this field blank. If you enter 0, the user cannot create any runs even if the user has appropriate permissions.
Login Group	Name of the login group to which the user belongs. Appears only if you are a superuser. If this field does not appear, the login group for the new user is the same as your login group.
Password (Local authentication only)	Password for the user account (up to 64 characters). The password does not need to be unique. Note that users can also modify their own passwords. Follow any recommendations by your organization related to creating secure (hard-to-guess) passwords. You must create passwords according to the password restrictions set by your site administrator. Does not apply if LDAP authentication is used.
Confirm Password (Local authentication only)	Re-enter the password for the user account to confirm it. Does not apply if LDAP authentication is used.
Superuser	If selected, the user can perform any activities. This check box is available only if you are logged in as a superuser. If you are not a superuser, the label Superuser appears (without a check box) for any previously created superuser.
Password never expires (Local authentication only)	If selected, the user password never expires. Note: If a user password has expired, a message at the top of the Edit User page tells you this when you edit the user. Does not apply if LDAP authentication is used.
User must change password at next login (Local authentication only)	If selected, the user is required to change the password when next logging in. This option is cleared automatically once the user has changed the password. Does not apply if LDAP authentication is used.
Account locked (Local authentication only)	If selected, the user cannot log in until you clear the check box. This check box is selected automatically for a user who tries to log in with an incorrect password more than the number of times allowed by the site option, Number of Attempts Allowed.
Account disabled	If selected, the user account is disabled. Disabled users cannot log in, receive notifications, or have objects such as topics assigned to them. Note: When a local user password has expired, the user account becomes disabled. To allow the user to log in again, you must both assign a new password to the user and re-enable the user account.

Related Topics