Field and Template Access Rights

Field and template rights allow you to control how fields can be accessed and modified in your repository. For instance, you could secure a sensitive field, such as a social security number, so that only users who should be able to see that sensitive information can access it. You can also secure fields to prevent people from modifying them, secure templates to hide the entire template from certain users, and use security to determine what users or groups should be able to modify a field or template's definition in Repository Administration.

Free Training: Supplemental Security in the Laserfiche Repository eLearning course in Aspire.

Securing a Field

  1. Open repository management by selecting the app picker and then selecting Repository Administration.
  2. On the left, under Metadata, select Fields.
  3. Select the field you want to set security for and click View Security.
  4. Select a trustee whose rights you want to modify, or click Add to configure security for a new trustee.
  5. Under Current Field Access Rights, allow or deny the appropriate rights.

Securing a Template

  1. Open repository management by selecting the app picker and then selecting Repository Administration.
  2. On the left, under Metadata, select Templates.
  3. Select the template you want to set security for and click View Security.
  4. Select a trustee whose rights you want to modify, or click Add to configure security for a new trustee.
  5. Under Current Template Access Rights, allow or deny the appropriate rights.

List of Field Rights

The following is a list of available field access rights:

  • Read: The ability to see the value of a field.
  • Create: The ability to set a value for a field during document creation. With this right, a user can fill in a field at the time of document creation whether that field has been applied as part of a template or independently. Automatically grants the Read right.
  • Edit: The ability to set a value for a field after document creation or apply an independent field to a document after document creation. Automatically grants the Create right.
  • Modify Definition: The ability to modify the field's definition in Repository Administration, including changing the field name, type, default value, and constraints.
  • Delete: The ability to delete the field's definition in Repository Administratoin.
  • Read Security: The ability to read the field access rights for the field.
  • Write Security: The ability to write field access rights for the field. Implicitly grants the Read Security right.

List of Template Rights

The following is a list of available template access rights:

  • Read: The ability to view a template's fields when the template is applied to a document, or to select it to apply to a document. Even if a user has the rights to all fields in a template, if they do not have this right for the template and the template has been applied to a document, they will not be able to see those fields. (This right has no effect on fields applied independently to the document, or fields applied via a different template, even if those fields are also present in this template.)

    • Note: The Read template access right does not control whether a user can see the template name in the document's metadata, just whether the user can see the fields.

  • Modify Template: The ability to change the template definition in Repository Administration, including the template name, the fields the template contains, and the order of the fields.
  • Delete Template: The ability to delete a template definition in Repository Administration. Note that a user must also have the Delete field access right to delete the fields contained within the template. If the user lacks these rights, the template definition will be deleted, but the individual fields will remain in the repository.
  • Read Template Security: The ability to view template security for the template.
  • Change Template Security: The ability to modify template security for the template.