Participant Events: The what, where and how
When signing in the real world, a lot of implicit events occur. For example, if several stakeholders gather to sign documents, they might witness each other enter the room, review each page and so on. In a digital environment, this can get lost.
What are Participant Events?
At Zigned we work hard to ensure transparency and integrity throughout the whole process. Therefore we log each step of a participants journey and embed it in the final, signed document. This provides a complete audit trail in the end which can act as supporting document if there is any doubt at any time.
Type of events
We log most actions a participant can take in the signing process. This includes but is not limited to: Visiting the signing room, initiating/cancelling a signature, scrolling a document etc. Since events are reactive, we can't log things that did not happen (such as not opening an attachment or not scrolling through a document), but that could be implied if a particular event is absent.
Events are dynamic and can change over time. We are constantly working on improving the logging of events and adding new ones. This means that the list of events can change over time. In general, new events follow new features, hence it should be regulated by the API version you are on. But be aware that things such as event titles and descriptions could change.
Read only
Participant Events are by definition read only. It is nothing but a log of what has happened and therefore can't be modified or deleted.