From the Design Gateway or Runtime Gateway
Edit menu, select Preferences.
The Isight Preferences dialog box appears.
Click Default Permissions on the left side of
the dialog box.
The permissions options appear.
The list on the top half of the right side of the dialog box is used
to define default permissions. The lower section is used for job permissions.
For more information on job permissions, see Setting Permissions for a Specific Job.
Click Add to add a new permissions
setting.
Note:
You cannot edit an existing permission setting. Instead,
you need to delete it and recreate it.
In the Managed Name column, enter a name for
the user or group whose permissions you are setting.
Click in the Permission column, and select the
type of permission from the list that appears:
| Option |
Description |
|---|
| ALTER |
Select to give the
user or group full access to the object, including the ability to edit
the object’s permissions. The object can be fetched (copied to a local
Isight library), new versions of the object can be published to the Isight
library, and any version of the object can be deleted from the Isight
library. |
| MODIFY |
Select to give
the user or group all the accessibility granted with the ALTER
option, with the exception of editing the object’s permissions. |
| READ |
Select to allow the
user or group to use the object only in their local Design Gateway. If
the object is a model, its contents (components, simulation process flows,
parameters, etc.) can be viewed and altered, and the model itself can
be executed; however, no new versions of the model can be published to
the Isight library. |
| REFERENCE |
Select to 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 (components, simulation process flows, parameters, etc.). 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 |
Select to give the
user or group no access to the published object. Furthermore, any model
that references this object cannot be used. |
Click in the Represents column, and determine
if the name specified in the Managed Name column
represents an individual user or a predefined group:
| Option |
Description |
|---|
| USER |
Select to specify a particular user name
for the permission you are defining. |
| GROUP |
Select to specify a group of users to share
the permission you are defining, instead of creating a permission for
each user. |
In the All other users list, set object permissions
for all other users (except for those explicitly defined). The options
available are the same as those described in Step 5.
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 the list is important
because a user name may appear in one or more groups 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 click Delete to remove a user name
from the list.
If desired, repeat Steps 3-8 to set default permissions for jobs stored
in a SIMULIA Execution Engine database. For more information on jobs,
the jobs database, and setting options for a specific job, see Executing and Managing Jobs.
Click OK to save your changes and to close the
Isight Preferences dialog box.
|