Provisioning and deprovisioning users with SCIM

With SCIM functionality, super admins of Enterprise organizations can quickly and easily provision and deprovision users in Asana from their identity management provider. Your organization can also be used to configure with SCIM. SCIM provisioning allows super admins to:

• Create a new user
• Update a user's profile attributes (Okta and Azure AD only)
• Import Asana users into their identity management provider
• Import Asana teams into their identity management provider (Okta only)
• Create teams in Asana from their identity management provider (Okta and Azure AD only)
• Deactivate a user

The following provisioning features are not supported by Asana:

• Reactivating users
• Deleting teams in Asana

Set up provisioning

To use SCIM provisioning, you will need to connect your organization's Asana account with one of our supported identity providers. Setup will vary according to the identity provider you use. Asana supports SCIM provisioning via:

• Microsoft Azure AD - Visit the Asana - Azure AD integration tutorial
• Google Workspace
• Okta
• OneLogin

Okta

Features

Super admins of Enterprise organizations can quickly and easily provision and deprovision users in Asana from Okta. The integration between Asana and Okta relies on an industry-standard protocol called SCIM that allows super admins to:

• Create users: Okta users assigned to the Asana application in Okta are automatically added as Members to your organization in Asana.
• Update user’s profile attributes: Attributes such as userName, title and department for a user’s profile can be synced from the user’s Okta profile to Asana.
• Import users: Users created in Asana can be imported in Okta either matched against existing Okta users or created as new Okta users.
• Import groups: Teams created in Asana can be imported as groups in Okta. Take into account Okta does not allow you to manage memberships of these imported groups.
• Push groups: Groups and their members in Okta can be pushed to Asana (as Asana teams and team members).
• Link groups: Existing teams in Asana can be linked to groups in Okta after importing the teams from Asana.
• Deactivate users: Users can be deactivated in Asana if they are no longer assigned to the app in Okta.

The following provisioning features are not supported at the moment:

• Reactivating users
• Deleting teams in Asana

Importing users or groups with emojis in their names to Okta will cause failure, as Okta only supports characters encoded with 3 bytes or fewer.

Requirements

Please ensure that you meet the following requirements before turning on SCIM for your organization.

1. You’re a super admin for an organization in Asana that’s on the Enterprise tier.
2. You have the correct Okta plan for provisioning users via SCIM. Please see Okta’s lifecycle management offerings for more information.

If you meet these requirements, use the following steps to enable SCIM for your organization.

Steps

Step 1: Add Asana’s Okta integration app to your Okta account

Step 2: Connect your organization’s Asana account to your Okta account

To use SCIM provisioning, you will need to connect your organization’s Asana account with your Okta account.

Complete the following steps in Asana

Complete the following steps in Okta

Login to your Okta admin portal and under the Applications tab, navigate to the Asana application.

Step 3: Set up provisioning options for Asana in your Okta account

In Okta

Under the applications tab, navigate to the Asana app and click on Provisioning.

We recommend you enable Create Users, Update User Attributes, and Deactivate Users.

Step 4: Map provisioned users into teams in Asana

To map Okta groups to Asana teams, you can decide to push new groups into Asana or link groups in Okta to existing teams in Asana. If you’re linking groups, please ensure that the teams you’d like to map them to are already set up inside Asana. Find out more about how to create a team in Asana in the guide article here.

In the Okta admin portal:

• Go to the Asana app and click on Refresh App Groups in the Push Groups tab to update any imports or changes that occurred in Asana. This ensures that all groups from the target app are represented in Okta.
• Click the Action button (Group Push Settings) if you want the ability to rename a group in Asana when linking. We recommend not renaming the app group to avoid any unintended changes to team names in Asana.

Please note that deletion of teams in Asana from Okta isn’t supported by this integration

Please use the Teams tab in the admin console in Asana to manage and delete teams.

Step 5: Configure attribute mappings for Asana

To configure and map attributes to user profiles in Asana, please follow the following steps.

• Go to the Asana app and click on the Provisioning tab.
• Configure the right options under the Asana Attribute Mappings section.
• Select Create or Create and Update from the choices under the Apply on column.

Attribute	Type	Info	Notes on limitations
userName	string	Unique identifier for the User, typically used by the user to directly authenticate to the service provider. Each User MUST include a non - empty userName value, and it must be an email address. REQUIRED.
name	complex	The user’s name
name.given	string	Unsupported, use formatted
name.familyName	string	Unsupported, use formatted
name.formatted	string	The full name of the user
emails	complex	Email addresses for the user
emails.value	string	Email address for the user
email.primary	string	Whether this email address is the preferred email address for this user. True may only appear once for this attribute.
title	string	The user's title, such as "Vice President".
department	string	Identifies the name of the department that the user belongs to.
preferredLanguage	string	Indicates the User's preferred written or spoken language. Used for selecting a localized user interface; e.g., 'en_US' specifies the language English and country US.	“Preferred language” can only be set for a user when the user is being created in Asana. Updates to the preferredLanguage field in Okta for existing Asana users don’t get reflected inside Asana.
Active	boolean	Indicate whether the user’s account is active in Asana.

Step 6: How to update your current Asana - Okta integration

If you’re currently using the Asana - Okta integration, please use the following steps in order to enable/access the latest updates.

Then, click on Edit again, check Enable API integration, enter the API token and click Save. Then, enable provisioning features. After this, you’ll see new attribute updates and integration capabilities reflected in the integration.

Assigning the Asana app to users in Okta will create that user profile within Asana, and trigger the same behavior as if they had been invited to Asana. It's important to note this when informing users that they have been assigned the Asana app.

When creating or updating users, the users must have email addresses that correspond with the Asana organization. Organization guests will continue to be provisioned and deprovisioned, and managed within the admin console's Members tab only.

OneLogin

Learn how to configure SCIM provisioning using OneLogin here.

To enable SCIM functionality with non-natively integrated IdPs please check the necessary accepted attributes here.

SCIM deprovisioning customization

The super admin of an organization can choose how a user’s tasks are handled after they have been deprovisioned via SCIM or the API.

When a user is deprovisioned from Asana, a Previously assigned tasks project containing all of the public tasks that were assigned to the user is created.

An organization-wide setting in the admin console allows you to choose a super admin to become the owner of this project. The project owner can reassign the tasks as they see fit.

To assign the project owner role to a super admin:

These customization settings will only apply when the user is removed from the organization via SCIM or API with a Service Account token.

You will find more information on user deprovisioning in our FAQ article.