Add contributors to your app

An app owner can add contributors to apps. These collaborators can modify the model, train, and publish the app.

Management of contributions from collaborators depends on the current status of the app.

For authoring resource migrated apps: contributors are managed in the Azure portal for the authoring resource, using the Access control (IAM) page. Add a user, using the collaborator's email address and the contributor role.

For apps that have not migrated yet: all collaborators are managed in the LUIS portal from each app's Manage -> Collaborators page. On this page, add a user's email address. This provides authoring access to this app only.

Add contributor to Azure authoring resource

The following procedure is for all users that have migrated to use the Azure authoring resource.

You have migrated if your LUIS authoring experience is tied to an Authoring resource on the Manage -> Azure resources page in the LUIS portal.

  1. In the Azure portal, find the Language Understanding (LUIS) authoring resource. It has the type LUIS.Authoring.

  2. On this resource's Access Control (IAM) page, select +Add then select Add role assignment.

    In Azure portal, add role assignment on authoring resource.

  3. In the Add role assignment window, select the Role of Contributor. In the Assign access to option, select Azure AD user, group, or service principal. In the Select option, enter the user's email address. If the user is known by more than 1 email address for the same domain, make sure the enter the primary email account.

    Add user's email to the contributor role for Azure AD

    When the user's email is found, select the account and select Save.

    If you have trouble with this role assignment, review Azure role assignments and Azure access control troubleshooting.

Add collaborator to LUIS app

The following procedure is for all users that have not migrated to use the Azure authoring resource.

You have not migrated if your LUIS authoring experience is not tied to an Authoring resource on the Manage -> Azure resources page in the LUIS portal.

An app has a single author, the owner, but can have many collaborators. To allow collaborators to edit your LUIS app, you must add the email they use to access the LUIS portal to the collaborators list. Once they are added, the app shows in their LUIS portal.

  1. Select Manage from the top right menu, then select Collaborators in the left menu.

  2. Select Add Collaborator from the toolbar.

    Add collaborator

  3. Enter the email address the collaborator uses to sign in to the LUIS portal.

    Add collaborator's email address

Users with multiple emails

If you add contributors/collaborators to a LUIS app, you are specifying the exact email address. While Azure Active Directory (Azure AD) allows a single user to have more than one email account used interchangeably, LUIS requires the user to sign in with the email address specified when adding the contributor/collaborator.

Azure Active Directory resources

If you use Azure Active Directory (Azure AD) in your organization, Language Understanding (LUIS) needs permission to the information about your users' access when they want to use LUIS. The resources that LUIS requires are minimal.

You see the detailed description when you attempt to sign up with an account that has admin consent or does not require admin consent, such as administrator consent:

  • Allows you to sign in to the app with your organizational account and let the app read your profile. It also allows the app to read basic company information. This gives LUIS permission to read basic profile data, such as user ID, email, name
  • Allows the app to see and update your data, even when you are not currently using the app. The permission is required to refresh the access token of the user.

Azure Active Directory tenant user

LUIS uses standard Azure Active Directory (Azure AD) consent flow.

The tenant admin should work directly with the user who needs access granted to use LUIS in the Azure AD.

  • First, the user signs into LUIS, and sees the pop-up dialog needing admin approval. The user contacts the tenant admin before continuing.
  • Second, the tenant admin signs into LUIS, and sees a consent flow pop-up dialog. This is the dialog the admin needs to give permission for the user. Once the admin accepts the permission, the user is able to continue with LUIS. If the tenant admin will not sign in to LUIS, the admin can access consent for LUIS, shown in the following screenshot. Notice the list is filtered to items that include the name LUIS.

Azure active directory permission by app website

If the tenant admin only wants certain users to use LUIS, there are a couple of possible solutions:

  • Giving the "admin consent" (consent to all users of the Azure AD), but then set to "Yes" the "User assignment required" under Enterprise Application Properties, and finally assign/add only the wanted users to the Application. With this method, the Administrator is still providing "admin consent" to the App, however, it's possible to control the users that can access it.
  • A second solution, is by using Azure AD Graph API to provide consent to each specific user.

Learn more about Azure active directory users and consent:

Next steps