User status (delete or Inactive) handlining

I would like to understand how SeaTable handles active users in the following scenarios:

1) User has never created a row but is tagged as a collaborator in multiple activities

1.1 If the admin deletes this user:

  • Will all activities where I tagged this user disappear?

  • What steps will the user need to take to log in again?

  • Anything else will impacted?

1.2 If the admin deactivates this user:

  • Will all activities where I tagged this user disappear?

  • What steps will the user need to take to log in again?

  • Anything else will impacted?


2) User has created rows or bases

2.1 If the admin deletes this user:

  • Will all activities where I tagged this user disappear?

  • What steps will the user need to take to log in again?

  • Anything else will impacted?

2.2 If the admin deactivates this user:

  • Will all activities where I tagged this user disappear?

  • What steps will the user need to take to log in again?

  • Anything else will impacted?

In SeaTable, a user is identified by its username (i.e. abc123…xyz@auth.local). You find more information on the username at Overview - SeaTable Admin Manual.

In collaborator, creator and last modifier columns as well as in comments, SeaTable uses a user’s username to refer to a user.

When a user is deleted from SeaTable, the username does not cease to exist. But the information that the user behind the username abc123…xyz@auth.local was name, for instance, “Max Mustermann” is deleted.

Hence, after deleting a user, you will see the username in all places where the user’s display name was previously shown.

Bases belonging to a deleted user a moved to trash and deleted permanently after 30 days.

Rows created by the deleted user in bases belonging to other users and groups will NOT be affected.

Disactiving a user and deleting a user are two completely different things. A user whose status was set to “inactive” cannot log into their account. But the user continues to exist in the system and, as a consequence, the inactive user can still be invited to bases/apps and referenced in collaborator columns.