Security Options

All enterprise databases use login security (i.e., they are secure). A standard database can be configured with or without login security (i.e., it may be secure or non-secure). (See Manage Repository Security for instructions on how to determine whether a standard database will have security enabled.)

In a non-secure standard database, any user who has read/write access to the database file (*.rsrp) will have full administrative and user permissions throughout the repository. Security-related features (such as the ability to create a private project or to lock a project) will still be visible in the interface to help you prepare for the transition from a non-secure to secure database, if desired. But the only factor that will prevent any user from performing any function in the repository is whether another user who is simultaneously logged in to the same database has the record currently in use.

In a secure database (both standard and enterprise), the actions that a user can perform in any given project within the repository depend on multiple factors:

Note: In addition to the factors listed above, the security groups can also be used to assign certain permissions that apply throughout the entire repository (such as the ability to manage user accounts or manage repository time units). If one of these permissions is granted via any of the security groups assigned to the user’s account, he/she will have the capability throughout the entire repository.

In both secure and non-secure databases, the centralized data storage allows multiple users to work collaboratively on analysis projects. Therefore, access to a particular record at any given time will also depend on whether it is currently in use by another user who is simultaneously logged in to the same repository.

 

 

© 1992-2013. ReliaSoft Corporation. ALL RIGHTS RESERVED.