IssueNet Online Help System

www.elsitech.com

Users

Modified: 2009/12/30 16:24 by Sean White - Categorized as: Administrator



Edit

1 What are Users

IssueNet users define who can log on and what privileges to IssueNet items they are granted. In IssueNet, the UserID is used only for authentication to the application, the users contact information is displayed in IssueNet items, and therefore, each user must have related contact information.

Users can either be created manually by the IssueNet administrator, or automatically using the LDAP integration.

Edit

2 Creating and Editing Users

The user item defines IssueNet users which can either be created manually or be created using the IssueNet LDAP integration, which creates users based on Directory Services settings.

  1. Select File|New|User OR Right-Click Users in the Data Source Explorer and select New OR Click the New User button and enter the following information:
    • User Name
    • Password
    • Password Hint
    • First Name
    • Last Name
    • Email
  2. (Optional) Enter a Description of the user
  3. (Optional) On the Group Membership tab, click Add to open the Find Groups dialog and add the user to an existing group
  4. (Optional) On the Security tab, click Add to limit the user to specific system items
  5. (Optional) Licensing Options
  6. Click the Update button or select Actions|Update

The user item is divided into the following tabs: ScreenCap
  • General- In addition to Contact information, the general tab provides a Description box for the user.
  • Group Membership- The group membership tab allows the Administrator to Add or Remove the user from Groups. Clicking Add opens the Permissions Wizard.
  • Security-The security tab allows the administrator to Add or Remove specific objects from the user security settings. Clicking Add opens the Permissions Wizard.
  • Licensing- The Licensing tab allows the administrator to associate a user with a particular license. Clicking the Add button opens the Assign License dialog, from which the Administrator can pick which serial number(s) to associate with the user.

Edit

2.1 Cloning Users

Cloning a user creates a new user with the same properties – including permissions. Cloning users allows you to save time by cloning users with identical permissions, and making adjustments, instead of creating each user separately. When adjustments are made on the cloned user, the original user is unaffected.

Cloning a User:
  1. In the Data Source Explorer highlight Users and select the User you wish to clone
  2. Select Edit|Clone
  3. Enter a Name in the New User form
  4. Select Actions|Update or click the Update button

Edit

2.2 Setting User Permissions

Permissions for IssueNet users are defined using the Permissions wizard. Permissions determine whether users have full access, read, write, create or delete privileges to IssueNet objects. Permissions can be applied to all instances of an Object in the Class or to a specific Object and its children. For example an administrator may wish to limit a user's ability to update Issues in a specific Folder.

IssueNet grants full access to all members of a class until permissions are applied. Once permissions are applied to a member of a class, IssueNet denies access to all other members until specific permissions are allowed.

Permissions are set in two basic ways:

1- Permissions can be set based on a relationship to a parent object, and the permissions are inherited by the child objects. For example, permissions can be set to deny access to issues that are related to a specific folder or tasks based on a relationship to a project. When permissions are set on a parent object such as a folder or project those permissions are inherited by their children.

2- Permissions can be set on specific members of a class. A user or group can be denied access to a specific issue, folder, query, report, or other item. For example, you may want to prevent a user or group from viewing or modifying a specific issue, folder, or query.

When permissions are set based on a relationship to a parent object, such as a folder or project, an object will be granted permissions based on the parent object that is most closely related to it. For example, if permissions are set to deny access to tasks on a root level project and to grant access on a sub-project, access will be denied to all tasks except those related to the sub-project or a child of the sub-project.

The following are the permissions that may be allowed or denied:
  • Full Access- Allows the user full control to the selected Object
  • Read- Allows the user to fetch and view the Object
  • Write- Allows the user to update the Object
  • Create- Allows the user to insert an instance of the Object into the database
  • Delete- Allows the user to delete the Object from the database

Edit

2.3 The Permissions Wizard

  1. Open a User Form and select the Security tab to open the Permissions Wizard
  2. Click Add to open the Permissions Wizard and click Next
  3. Select the Class from the Drop down menu (e.g: Issue)
  4. Select either All Objects or Specific object and its children.
    • If you select All Objects, click Next.
    • If you select Specific objects and its children click the Find button to open the Query dialog. Select an appropriate Query (For example, if you are working with Issues, you could select a query related to Folders to limit or allow access to Issues contained within the specified Folder(s)) and click OK to close the Query dialog and click Next.
  5. Select the appropriate permissions for the Object and click Finish