admin.auth.policy.assignEntities

Assign entities to a particular authentication policy.

Notices

This API method can only be used on Enterprise Grid workspaces.

Facts

Method access

HTTP
JavaScript
Python
Java
HTTP
POSThttps://slack.com/api/admin.auth.policy.assignEntities
Bolt for Java
app.client().adminAuthPolicyAssignEntities
Powered by Bolt
Bolt for Python
app.client.admin_auth_policy_assignEntities
Powered by Bolt
Bolt for JavaScript
app.client.admin.auth.policy.assignEntities
Powered by Bolt

Content types

application/x-www-form-urlencodedapplication/json
  • Rate limits

    Tier 4
  • Arguments

    Required arguments

    Authentication token bearing required scopes. Tokens should be passed as an HTTP Authorization header or alternatively, as a POST parameter.

    Example
    xxxx-xxxxxxxxx-xxxx

    Array of IDs to assign to the policy.

    Example
    ['U12345','U27345']

    The type of entity to assign to the policy. Currently, USER is supported.

    The name of the authentication policy to assign the entities to. Currently, email_password is the only policy that may be used with this method.

    Example
    email_password

    Usage info

    This Admin API method assigns entities (currently, users) to an authentication policy—for example, signing in with email and password.

    For help understanding URL-encoded vs JSON format in your request (particularly entity_ids), see POST Bodies below.

    This admin scope is obtained through version two of the OAuth V2 flow, but there are a few additional requirements. The app requesting this scope must be installed by an Admin or Owner of an Enterprise Grid organization. Also, the app must be installed on the entire org, not on an individual workspace. See below for more details.

    If the app is installed by an Org Admin or Owner, ensure the Channel Management settings provide the appropriate permissions. In order to manage channels after they are created, you must update your token to enable permissions for Org Admins or Owners (not just the Primary Org Owner).

    Admin API endpoints reach across an entire Enterprise Grid organization, not individual workspaces.

    For a token to be imbued with admin scopes, it must be obtained from installing an app on the entire Grid org, not just a workspace within the organization.

    To configure and install an app supporting Admin API endpoints on your Enterprise Grid organization:

    1. Create a new Slack app. Your app will need to be able to handle a standard OAuth 2 flow.
    2. In the app's settings, select OAuth & Permissions from the left navigation. Scroll down to the section titled Scopes and add the admin.* scope you want. Click the green Save Changes button.
    3. In the app's settings, select Manage Distribution from the left navigation. Under the section titled Share Your App with Other Workspaces, make sure all four sections have the green check. Then click the green Activate Public Distribution button.
    4. Under the Share Your App with Your Workspace section, copy the Sharable URL and paste it into a browser to initiate the OAuth handshake that will install the app on your organization. You must be logged in as an Admin or Owner of your Enterprise Grid organization to install the app.
    5. Check the dropdown in the upper right of the installation screen to make sure you are installing the app on the organization, not an individual workspace within the organization. See the image below for a visual.
    6. Once your app completes the OAuth flow, you will be granted an OAuth token that can be used for calling Admin API methods for your organization.

    When installing an app to use an Admin API endpoint, be sure to install it on your Grid organization, not a workspace within the organization.

    POST Bodies

    As outlined in Using the Slack Web API, you may present your arguments as either standard POST parameters or use JSON instead. This may be confusing in terms of the array argument type, so let's look at an example for each.

    Here's an example of calling the method with a URL-encoded query string: curl --request 'POST' --header 'Authorization: Bearer xoxp-...' 'https://slack.com/api/admin.auth.policy.assignEntities?entity_ids=U0130R122E8%2C%20U0133AHT0M8&entity_type=USER&policy_name=email_password&pretty=1'

    Here's an example of calling the method with a JSON body: curl --request 'POST' --header 'Authorization: Bearer xoxp-...' --header 'Content-Type: application/json; charset=utf-8' 'https://slack.com/api/admin.auth.policy.assignEntities' -d '{ "entity_ids": [ "U0130R122E8", "U0133AHT0M8" ], "entity_type": "USER", "policy_name": "email_password" }'

    Both will yield the same result, so it's potato po-tah-to as far as we're concerned.

    Example responses

    Common successful response

    Typical success response

    {
        "ok": true
    }

    Errors

    This table lists the expected errors that this method could return. However, other errors can be returned in the case where the service is down or other unexpected factors affect processing. Callers should always check the value of the ok params in the response.

    ErrorDescription
    admin_unauthorized

    The token provided doesn't have permission to revoke a session.

    entity_not_found

    At least one entity_id was not found.

    feature_not_enabled

    This method is only available for Enterprise organizations.

    internal_error

    The server could not complete your operation(s) without encountering an error, likely due to a transient issue on our end. It's possible some aspect of the operation succeeded before the error was raised.

    invalid_arguments

    The method was either called with invalid arguments or some detail about the arguments passed is invalid, which is more likely when using complex arguments like blocks or attachments.

    invalid_auth

    Some aspect of authentication cannot be validated. Either the provided token is invalid or the request originates from an IP address disallowed from making the request.

    not_an_admin

    This method is only accessible by Org Owners and Admins.

    over_max_entity_limit

    The number of entities assigned to this policy has reached its upper limit.

    policy_not_found

    The policy name doesn't match any of the existing org policies.

    ratelimited

    The request has been ratelimited. Refer to the Retry-After header for when to retry the request.

    unknown_method

    This method is currently not available.

    access_denied

    Access to a resource specified in the request is denied.

    account_inactive

    Authentication token is for a deleted user or workspace when using a bot token.

    deprecated_endpoint

    The endpoint has been deprecated.

    ekm_access_denied

    Administrators have suspended the ability to post a message.

    enterprise_is_restricted

    The method cannot be called from an Enterprise.

    is_bot

    This method cannot be called by a legacy bot.

    method_deprecated

    The method has been deprecated.

    missing_scope

    The token used is not granted the specific scope permissions required to complete this request.

    not_allowed_token_type

    The token type used in this request is not allowed.

    not_authed

    No authentication token provided.

    no_permission

    The workspace token used in this request does not have the permissions necessary to complete the request. Make sure your app is a member of the conversation it's attempting to post a message to.

    org_login_required

    The workspace is undergoing an enterprise migration and will not be available until migration is complete.

    token_expired

    Authentication token has expired

    token_revoked

    Authentication token is for a deleted user or workspace or the app has been removed when using a user token.

    two_factor_setup_required

    Two factor setup is required.

    accesslimited

    Access to this method is limited on the current network

    fatal_error

    The server could not complete your operation(s) without encountering a catastrophic error. It's possible some aspect of the operation succeeded before the error was raised.

    invalid_arg_name

    The method was passed an argument whose name falls outside the bounds of accepted or expected values. This includes very long names and names with non-alphanumeric characters other than _. If you get this error, it is typically an indication that you have made a very malformed API call.

    invalid_array_arg

    The method was passed an array as an argument. Please only input valid strings.

    invalid_charset

    The method was called via a POST request, but the charset specified in the Content-Type header was invalid. Valid charset names are: utf-8 iso-8859-1.

    invalid_form_data

    The method was called via a POST request with Content-Type application/x-www-form-urlencoded or multipart/form-data, but the form data was either missing or syntactically invalid.

    invalid_post_type

    The method was called via a POST request, but the specified Content-Type was invalid. Valid types are: application/json application/x-www-form-urlencoded multipart/form-data text/plain.

    missing_post_type

    The method was called via a POST request and included a data payload, but the request did not include a Content-Type header.

    request_timeout

    The method was called via a POST request, but the POST data was either missing or truncated.

    service_unavailable

    The service is temporarily unavailable

    team_added_to_org

    The workspace associated with your request is currently undergoing migration to an Enterprise Organization. Web API and other platform operations will be intermittently unavailable until the transition is complete.

    Warnings

    This table lists the expected warnings that this method will return. However, other warnings can be returned in the case where the service is experiencing unexpected trouble.

    WarningDescription
    missing_charset

    The method was called via a POST request, and recommended practice for the specified Content-Type is to include a charset parameter. However, no charset was present. Specifically, non-form-data content types (e.g. text/plain) are the ones for which charset is recommended.

    superfluous_charset

    The method was called via a POST request, and the specified Content-Type is not defined to understand the charset parameter. However, charset was in fact present. Specifically, form-data content types (e.g. multipart/form-data) are the ones for which charset is superfluous.

    Arguments

    Need a token? Create and install a Slack app to begin.
    This will make a real API request. Beware of using it with live workspaces.

    API response


    Submit your arguments to see the API response