Skip to main content Skip to complementary content
Close announcements banner

Deactivating users

Deactivated users can no longer log in toTalend Cloud and cannot use their personal tokens.

However, the objects owned by these deactivated accounts remain intact and available to the active users who have appropriate access rights and permissions.

Before you begin

You must have the Users - Manage permission to complete this task.

Procedure

Use the public REST API or the Users & Security page in Talend Management Console to deactivate users when they leave your company.
  • In Talend Management Console:
    1. Go to Users & Security > Users.
    2. Hover your cursor over the user to be deactivated in the First name column to display the corresponding button.
      The button used to deactivate users
    3. Click the deactivate user button and in the dialog that is displayed, confirm the deactivation.

      The status of this user becomes deactivated in the Status column.

  • API:
    1. Create an API token from the portal:
      1. In the top-right corner, click your username.

      2. Click Profile preferences > Personal access tokens > Add token.

      3. Enter a token name and click Generate.
      4. Copy the generated token and paste it somewhere secure.
    2. Find the account name of the user to deactivate in Account & Subscription > Account.
    3. Find the username of the user to deactivate. From Talend Management Console, go to Users & Security > Users and copy the login of the user.
    4. Use the information from the previous steps to write your request. For example, using a curl request:
      curl -v -X POST 
      --header "Authorization: Bearer <token_value>" 
      --header "Content-Type: application/json" 
      -d '{ "accountName": "<account_name>", "userName": "<user_name>" }' 
      'https://iam.us.cloud.talend.com/scim/v2/Users/deactivate'

      Note that you must use a POST method, and the two headers are mandatory.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!