functions.distributions.permissions.set

View other methods

Set the access type of a custom slack function and define the users to be granted access if permission_type is set to named_entities

Reference docs Tester

Facts

Method access

HTTP

JavaScript

Python

Java

HTTP

POSThttps://slack.com/api/functions.distributions.permissions.set

Bolt for Java

app.client().functionsDistributionsPermissionsSet

Bolt for Python

app.client.functions_distributions_permissions_set

Bolt for JavaScript

app.client.functions.distributions.permissions.set

Required scopes

Bot tokensapp_configurations:write

User tokensapp_configurations:write

Content types

application/x-www-form-urlencodedapplication/json

Rate limits

Tier 3

Arguments

Required arguments

token

token

·Required

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

Example

xxxx-xxxxxxxxx-xxxx

One ofpermission_type

permission_type

enum

The type of permission that defines how the function can be distributed

Value should be one ofeveryoneapp_collaboratorsnamed_entities

Optional arguments

function_app_id

string

·Optional

The encoded ID of the app

Example

A12345

function_callback_id

string

·Optional

The callback ID defined in the function's definition file

Example

my_function

function_id

string

·Optional

The encoded ID of the function

Example

Fn12345

user_ids

array

·Optional

List of encoded user IDs

Example

U1234,U2345,U3456

Usage info

Set the permission_type to define how your custom function can be distributed for use in other workflows. Supply a list of user IDs to grant access to if distributing to a specific group of users.

Identify your function by supplying its callback ID and your app ID. The encoded ID of the function can also be used instead.

Example responses

Common successful response

If successful, the command returns the permission type and if applicable, the list of users with access

{
    "ok": true,
    "permission_type": "app_collaborators",
    "users": [
        {
            "user_id": "U01565LTEBD",
            "username": "joe_smith",
            "email": "joesmith@salesforce.com"
        }
    ]
}

Common error response

Typical error response when an invalid user ID is supplied in user_ids

{
    "ok": false,
    "error": "user_not_found"
}

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.

Error	Description
`unknown_method`	This method does not exist.
`access_denied`	Access to a resource specified in the request is denied.
`function_not_found`	This function does not exist.
`invalid_permission_type`	This function requires permission_type to be set as named_entities before adding users.
`user_not_found`	One or more of the named entities was not found.
`app_not_found`	This app does not exist.
`permission_type_required`	`permission_type` is a required input.
`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.
`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.
`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.
`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_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_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_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.
`ratelimited`	The request has been ratelimited. Refer to the `Retry-After` header for when to retry the request.
`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.

Warning	Description
`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.

API response

URL

POST body

Submit your arguments to see the API response