Setting Default Permissions

When connected to a SIMULIA Execution Engine, you can set permissions on newly published objects (e.g., models, components, and objects) and newly published jobs. Setting permissions allows you to control which SIMULIA Execution Engine user can have access to items saved in the library (objects) or in the database (jobs).

  1. From the Design Gateway Edit menu, click Preferences.
  2. Click Default Permissions.

    The steps for setting permissions for newly published objects or jobs is the same. To set permissions for newly published objects, use the settings located in the upper portion of the dialog box. To set permissions for newly created jobs, use the settings located in the lower portion of the dialog box.

  3. Click Add to create a new permission.

    Note: You cannot edit an existing permission setting. Instead, you need to delete it and recreate it.

  4. In the Managed Name column, enter the user name or group name whose permissions you are setting.
  5. Click the Permission field, and select the type of permission:
    OptionDescription
    ALTER (for objects)
    • For objects, give the user or group full access to an object, including the ability to edit the object’s permissions. The user or group can copy the object to a local library, publish new versions of the object to the library, and delete any version of the object from the library.
    • For jobs, give the user or group full access to the job, including the ability to edit the job’s permissions. The user or group can view the details of the job, load the job into the Runtime Gateway and watch it run, and view any results generated by the job. The user or group can also pause, resume, and stop the job while it is running, and they can delete the job and all its results at any time.
    MODIFY Give the user or group all the accessibility granted with the ALTER option, with the exception of editing the permissions.
    READ
    • For objects, allow the user or group to only use the object in their local Design Gateway. Although the model and its contents (e.g., components, simulation process flows, parameters) can be viewed and altered and the model itself can be executed, no new versions of the model can be published to the library.
    • For jobs, allow the user or group to only view the job’s simulation process flow and execute it. No parameter access is allowed.
    REFERENCE For objects, provide an extra level of security for published models. Typically, when using a published model, you have access to all of the published model’s contents (e.g., components, simulation process flows, parameters). However, if this permission level is set for a user who incorporates a published model into their own model, all the contents of the model are hidden from view. For more information on referencing models, see Using Submodels and Referenced Models.
    NONE For objects and jobs, give the user or group no access to the published object or job. In addition, any model that references this object cannot be used.
  6. Click the Represents field, and select if the name specified in the Managed Name column represents an individual user or a predefined group:
    OptionDescription
    USER Specify a particular user name for the permission you are defining. You can add the user name in the Managed Name column as described above
    GROUP Specify a group of users to share the permission you are defining, instead of creating a permission for each user. You can add the group name in the Managed Name column as described in Setting Default Permissions.
  7. Click All other users to set permissions for all other users (except for those defined explicitly).

    The options available are the same as those described above. You can also specify that there is no default option for other users (in which case a system default is applied).

  8. To define additional user permissions, repeat the above steps.
  9. Arrange the listed users, as desired.

    You can use the Up or Down buttons to move a user up or down in the list. The selected user’s settings move up or down one line. The order of your list is important because a user name may appear in one or more groups (the GROUP option) as well as by itself. Therefore, it is possible for a user to be assigned more than one permission for the same object. If a user has multiple permissions, Isight uses the permission closest to the top of the list to determine the user’s actual permission for the object.

    You can use the Delete button to remove a user from the list.

    Note: For information on setting permissions for a specific job, see Setting Permissions for a Specific Job.

  10. Click OK to save your changes and to close the Preferences dialog box.