You are here: All Help Topics > Engagement Management > Users > About the Security ID
-- More Info --

About the Security ID

The security ID prevents unauthorized administrative access to a client file that has protection enabled. When creating a Data Store, enter a security ID in the Choose Security ID page of the Data Store Creation Wizard.

The ID ensures that only administrators connected to the correct Data Store be granted full access to a particular file. The security ID adds another level of protection to the client file; however, you can choose not to set it or disable it to allow administrators of other Data Stores to have full administrative access to files.

Important: The security ID feature does not affect non-administrators. It only serves to prevent unauthorized administrative access.

Once a security ID is set, it is locked to that Data Store. When a client file is first opened by someone connected to the Data Store, the security ID of the Data Store is written into the client file.

If a security ID is set, an administrator may log into a file only if the security ID of the data store matches the security ID of the client file. The security ID matching only occurs if a client file contains a security ID.

If the IDs do not match, a message is displayed indicating that the security ID for the Data Store does not match the security ID of the client file.

Important: It is not required that the same Data Store that was active when a client file was first accessed be used when subsequently accessing the client file as an Administrator. It is only required that the Security ID remain the same. If the user list in the data store needs to be recreated for any reason, it is then only necessary to re-enter the same ID to have continued access to client files as an administrator. For this reason, it is important that a record of the security ID be made when creating a Data Store.

Once the security ID is disabled and an administrator of a different Data Store opens the client file, the following occurs:

  • The Allow administrators connected to a different data store to log onto this file check box is cleared.
  • The security ID of the new store is linked to the client file and can only be opened with the new Data Store.
  • If no security ID exists in the new Data Store, the security ID is removed from the file.

Note the file is maintained under the original Data Store in the following circumstances:

  • When a non-administrator connected to a different Data Store opens the client file.
  • If the Allow administrators connected to a different data store to log onto this file check box is cleared before the file has been opened by an administrator of a new store.

The Working Papers Copy Components function has the following limitations where security IDs are concerned when you are logged in as an administrator:

Copy all components

The template is copied.

The security ID is copied.

Copy some components to a new file

The template is copied.

The security ID is copied.

Copy some components to an existing file

The security ID is not copied.

Note the following:

  • Where the security ID is set in both the source and destination files, but they do not match, the template is not copied. To copy the template, log in as a non-administrator with copy components rights. You need to log in to both files, so you need to have the appropriate rights for both files. You must also disable the security ID.
  • If the source file does not have a security ID and the destination file does, the template is not copied. To copy the template, you can open the file while connected to the same Data Store as the destination file. Alternately you can use a non-administrator login with the appropriate rights.
  • If copying from a protected file to an existing unprotected file, the security ID is not copied.

If the source file is protected and has a security ID set, that security ID overwrites the security ID of the destination file.

Related Topics