 |
 |
|
 |
 |
|
 |
 |
 |
All enterprise databases use login security, meaning that the ReliaSoft applications use Windows authentication (or alternative credentials) to identify each user and control the user’s access via security groups. For a standard database, you can choose whether to apply login security; if you don’t, any user who has read/write access to the file will have full permissions throughout the database.
By default, each user in a secure database will have the same set of permissions for every public/reference project in the database (e.g., Jane Engineer has read-write access to all projects, Bill User has read-only access to all projects, and so on). Alternatively, you can configure the database to provide different permissions for different public/reference projects, if desired (e.g., Jane Engineer has read-write access to all of Department A’s projects, but she has read-only access to other projects). With either approach, you also have the option to further limit access for specific project items (e.g., folios, diagrams, system hierarchy items, etc.) if needed. There are many different ways these options can be configured depending on your organization’s particular needs.
Tip: If you need to be able to manage an enterprise database without using a ReliaSoft desktop application (i.e., without taking up one of the available license seats), you can access the same security features from the ReliaSoft Admin tool.
Applying Login Security (for standard databases)
Alternative Credentials (for users that need to log in from a different domain)
Managing Security Groups (sets of permissions) and Associating Security Groups with Active Directory
Status Indicators ("in use" or "restricted access")
Resetting "In Use" Flags (if an item is incorrectly locked for editing)
© 1992-2019. HBM Prenscia Inc. ALL RIGHTS RESERVED.
 |
E-mail Link |