Events

You can follow the usage of Seald through events, visible in the audit trails screen of the administration dashboard.

You can also ask for an export of these events. Here is a list of all the types of events possible, and what they mean:

  • DEVICE_ADDED: A user has registered a new device (happens during registration);
  • GET_OTP: A non-Seald user has requested access to an encrypted file;
  • MESSAGE_CREATE: A user has encrypted a file;
  • MESSAGE_ENTRUSTED_FAIL_OLD: A non-Seald user has tried to access an encrypted file, but used an expired one-time-password;
  • MESSAGE_ENTRUSTED_FAIL_WRONG: A non-Seald user has tried to access an encrypted file, but used a wrong one-time-password;
  • MESSAGE_ENTRUSTED_READ: A non-Seald user has read an encrypted file successfully;
  • MESSAGE_ENTRUSTED_READ_BROWSER_INSTEAD_SEALD: A registered Seald user has tried to open an encrypted file with the browser (like non-Seald users) instead of with the Seald app;
  • MESSAGE_ENTRUSTED_READ_UNAUTHORIZED: An unauthorized non-Seald user has tried to open an encrypted file;
  • MESSAGE_ENTRUSTED_READ_UNAUTHORIZED_REVOKED: A non-Seald user that was revoked from an encrypted file has tried to open it;
  • MESSAGE_READ_FAILED_DEVICE: A Seald user that has access to an encrypted file has tried to open it with one of their devices that does not have access to said file (should never happen);
  • MESSAGE_READ_OK: A Seald user has opened an encrypted file;
  • MESSAGE_READ_UNAUTHORIZED: A Seald user has tried to open a file for which they do not have access;
  • MESSAGE_READ_UNAUTHORIZED_REVOKED: A Seald user that was revoked from an encrypted file has tried to open it;
  • MESSAGE_TOKEN_CREATED_FOR: A new recipient was authorized for an encrypted file;
  • USER_CREATED: A new user was created;
  • USER_LOGGED: A user has logged in to the server (happens automatically when using the app);