|
|
All data is closely monitored and tracked
through history logging. This process helps
in determining who and when the file was
created, modified, deleted or recovered.
All data are protected with utmost concern
thus ensuring that any unauthorized access is
virtually impossible.
|
|
|
|
Data Ownership
|
|
When User A for example creates a document, then
views it, the only document he'll see is his own,
even if User B already has one in the system. On
the otherhand, User B will not be able to view,
modify, delete, or recover User A's documents.
But, a manager, who is someone on a higher level
than the two users, can view, modify, delete, or
recover both User A's and User B's documents.
|
|
|
No Coding Restriction
|
|
Account codes stored in e2B can easily
be altered anytime you want and how often you want.
|
|
|
Data Expiration
|
|
All data stored in e2B can be set with
expiration dates. When that certain data exceeds
its expiration date, it becomes inactive and
unavailable for use.
|
|
|
Data Versioning
|
|
Whenever someone changes something on a user's data,
it is recorded and can be viewed in the data's
history log which contains the time and date it was
altered and who changed it. Every modification made is
closely monitored and tracked down. This protects the
user's documents from malicious data alteration by
other people.
|
|
|
Data Recovery
|
|
Accidentally deleted data can easily be recovered
by e2B. Data ownership is enforced in
data recovering. If User A accidentally deletes
his data, he can't expect User B to recover it.
Only he and someone with a higher level than him
(e.x. a manager) can do that.
|
|
Return to previous page
|