Configure Asana user provisioning

As an administrator, once you've set up SSO, your next step is to set up automated user provisioning to authorize, create, modify, or delete your users' identity once in G Suite, and have the changes to that identity reflected in Asana.

Set up user provisioning for the Asana application
  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML Apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click the Asana application.
  4. Select User provisioning.
  5. Under User provisioning, click Set up user provisioning.
  6. Enter the Service Account token available from the Asana Admin UI console.
    How do I find the Service Account token?
  7. In the Map attributes dialog box:
    1. Next to the selected Cloud Directory attribute, click the Down arrow Down Arrow to map to the corresponding Asana attribute. Attributes marked with (*) must be mapped.
    2. Click Next.
  8. Once you’re done, click Finish.
  9. Review the information in the Provisioning summary dialog box, then click OK.
  10. Click Activate provisioning.
  11. In the confirmation dialog box, click Activate.
Display user provisioning

Once provisioning is enabled, Google begins collecting usage information. Next to User Provisioning, you see the usage information section. There aren't any numbers next to the event names until you enable provisioning.

The following event names provide the usage information for the last 30 days:

  • Users created
  • Users hard deleted
  • User failures

For more information, see Monitor user provisioning.

Edit provisioning scope

You may want to restrict the scope of provisioning to members of groups you define.

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML Apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click the Asana application.
  4. Select User provisioning.
  5. Under User provisioning, click Edit provisioning scope
  6. In the Set provisioning scope dialog box, add a group to restrict provisioning to members of groups you define:
    1. Click the underscore and begin typing your group name. 
      A list of available groups appears.
    2. Selecting one adds it and opens another underscore to use to add another. Add more groups, if necessary. 
    3. To remove any group you've added, click Edit Edit next to it.
  7. Once you’re done, click Finish.
  8. The next time you click Edit provisioning scope under User provisioning, the groups you added appear in the Set provisioning scope window. If you've turned on the Asana application for a set of organizational units, the provisioning scope will be restricted to those users in the added groups who are also members of those organizations.
Deactivate user provisioning

To disable user provisioning for the Asana application without losing all the configuration information:

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML Apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click the Asana application.
  4. Select User provisioning.
  5. Under User provisioning, click Deactivate provisioning.
  6. In the Deactivate provisioning dialog box, click Deactivate.
Define deprovisioning timeframes

To define how long deprovisioning actions should be delayed before taking effect:

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML Apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click the Asana application.
  4. Select User provisioning.
  5. Under User provisioning, click Edit deprovisioning config.
  6. In the Deprovisioning configuration dialog box, select one or more of the following options to define how long deprovisioning actions should be delayed before taking effect:
    1. When an app is turned off for the user, their account remains unaffected or hard delete the account after the number of days you choose.
    2. When a user is suspended on Google, their account remains unaffected or hard delete the account after the number of days you choose.
    3. When a user is deleted from Google, their account remains unaffected or hard delete their account after the number of days you choose.

      The amount of time before deprovisioning takes effect can be set to within 24 hours, after 1 day, after 7 days, or after 30 days.

      The default for when an app is turned off for the user or when a user is suspended on Google is their account remains unaffected.

      The default for when a user is deleted from Google is to hard delete their account after the number of days you choose
  7. Click Save.
Remove user provisioning

To disable user provisioning for the Asana application and remove all the configuration information:

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Apps and then SAML Apps.

    To see Apps on the Home page, you might have to click More controls at the bottom. 

  3. Click the Asana application.
  4. Select User provisioning.
  5. Under User provisioning, click Delete provisioning.
  6. In the Delete provisioning config dialog box, click Delete to deactivate user provisioning and remove all configuration information. 

    Existing users on Asana are not deprovisioned.
Was this helpful?
How can we improve it?