This article provides information about the Settings/Configuration/Stamps page. Upload your electronic stamps in PNG or JPG format, then assign the stamps to the users who will conduct plan review. Stamps saved in PNG with a transparent background are recommended. 

Users who conduct plan review will be assigned specific stamps to use in the Plan Review page. See Managing User Accounts - Steps to creating a new user account.

Prerequisites:

1. Create PNG or JPEG image format stamp files with good resolution. (See examples below)

In this article:

Best Practices for Creating Electronic Stamps

When migrating from a paper review process to an electronic review process, we recommend the following approach:

1. Upload stamps for plan review Approvals, Conditional Approvals or Rejections only. In other words, stamps that communicate a pass or fail status.
2. Stamp file size minimum recommendations are 800 x 800 pixel and 300 dpi will provide good visual quality when resizing. Below are examples of various stamp sizes:

When migrating from a paper review process to an electronic review process, we recommend the following approach:

1. Do not upload stamps that consist of redlines, instructions, comments, notes, etc.
   1. Instead, users should create comments on their plan reviews to communicate instructions, comments, notes, etc. to their customer.
   2. We recommend creating Standard Comments for these commonly used comments, instructions or notes so they are available to all users.

Uploading Electronic Stamps

Electronic stamps in PNG or JPG format uploaded to the application will be assigned to users who conduct plan review.

Stamps can be shared among many users or assigned individually to specific users.

1. From the Configuration/Stamps page, select the + button to open a Stamp Detail form.
2. Browse for a PNG.
   1. Stamp file size minimum recommendations are greater than 100KB and 300 dpi.
3. Provide the Firm/Agency name associated to the stamp, as appropriate. 
4. Stamps placed on documents during review will display data based on the settings toggles:
   1. Make sure to set the stamp to 'Active.'
   2. Set whether to display the datestamp.
   3. Set whether to display the Project number.
   4. Set whether to display the First and Last Name of the person who placed the stamp.
   5. Finally, determine whether to display the information either below the stamp or at the center of the stamp using the correct toggle.
5. Select the Save button. (required)

Once a stamp has been uploaded, it can be added to any user account. See Managing User Accounts - Steps to creating a new user account

Stamp Permissions 

Access to stamps is controlled by the Security > Permissions section and is role based security.

Stamp Security and Access
The ability for users to place stamps onto a plan set is regulated by a three-step process:

1. First, the ability to upload stamps into EPR is controlled by an Agency-defined Admin by default. Stamps are uploaded by the Administrator and configured to display project number, user, and/or date information as desired.
2. The Admin then assigns a stamp or stamps to users who the Agency determines should have access. In this way, stamp access can be restricted to a specific individual, such as with a signature stamp, or provided more broadly to multiple users, such as with a department-wide annotation stamp.
3. Third, the ability to place stamps onto a plan set is regulated by permissions and user role. By default, non-Admin users must be granted access to a project and have markup rights in order to place a stamp onto a plan set for a given project.

Stamping Process

• The stamp tool allows for a user to place a stamp markup onto a plan set onto either an individual page or a series of pages on a single plan set. The stamp event is recorded (“Document – Stamp Insert”) in the EPR Event Log along with the date, time and user who placed the stamp.
• If a stamp is configured to display user and/or date stamp information, matching data will be recorded and displayed on the plan set as well.
• When a plan set deliverable is generated, EPR creates a new pdf document that includes the stamp annotation as part of the same pdf image layer as the document itself. The stamp is not a separate, editable annotation.

Stamps Security (TBD)

• What are the securities around stamps?
• Is the security for electronic stamp equivalent or better than manual physical stamp?

To answer these questions, electronic stamps must:

• Have security on who can use it and guarantee this functionality
  • Who can use the stamp and how can we best guarantee he/she is the only person using the stamp?
    • Required password whenever a stamp is used can fulfill this requirement.
    • Stamps specifically assigned per user can help
  • How can we best guarantee once a stamp is uploaded that it cannot be changed?
    • Hashing the stamp can fulfill this requirement
  • How can we best guarantee which stamp was placed on the document?
    • Hashing the document after stamp placement can fulfill this requirement