...
Access to stamps is controlled by the Security > Permissions section and is role based security.
What are the securities around stamps?
Stamp Security and Access
The ability for users to place stamps onto a plan set is regulated by a three-step process:
- 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.
- 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.
- 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?
...