Skip to content

OpenCGA Catalog Admin operations

imedina edited this page May 16, 2016 · 1 revision

User operations

Add user

  • This action will create a new user in the database with a random password. The user will be able to change it later at any moment.

Delete user

  • The user will be marked with the status Deleted, so it will no longer be able to login or perform any more operations.
  • All the documents the user might have in other collections, such as projects, studies, files, jobs... will be therefore deleted.

Ban user

  • The user will be marked with the status Banned. The user will no longer be able to login or perform any more operations until the administrator re-enables it.
  • All the documents the user might have will remain in case the admin wants to re-activate the user in the future.

Enable user

  • A user with a previous Banned status will be marked again as Active. This action will, therefore, re-enable the user to perform any actions that could be made before the banning.

Change the disk quota

The admin can modify at any point the disk quota of a user. The only critical scenario is:

  • The admin has lowered the disk quota to a user and the user is using more disk than the new quota:
  • In this case, the user will no longer be able to perform any actions that imply generating or updating any file in its projects/studies. However, the user will still be able to perform queries of any already created data at any point.
  • These permissions will not affect the user if it has been given proper permissions to create or update new documents or files in other user's study if the study's owner user still has available disk quota.

Otherwise, if the user still has not reached the disk quota limit, it will still be able to perform any action.

Summary stats

Clone this wiki locally