All apps in our App Directory have a unique set of permissions, called scopes, that tell you what information the app can access, and how that information can be used. Generally, an app will ask permission to do the following:
An app's full set of permissions are listed when the app is installed. You can find a detailed list of scopes in our API documentation.
Tip: Some developers submit detailed information about their security and compliance practices to us. If available, you can see that info in the Security & Compliance tab on an app’s page in the App Directory.
Workspace Owners can control exactly which apps get installed by creating lists of approved and restricted apps. In the App Directory, members will clearly see which apps are approved for the workspace, which apps need approval, and which apps are not allowed.
👨✈️ Decide who can manage apps and integrations
By default, only Workspace Owners can manage apps. With the Approve apps setting turned on, Owners can allow selected members to manage approved apps and respond to app installation requests.
Turn on app approval
From your desktop, click your workspace name in the top left.
Select Settings & administration from the menu, then click Manage apps.
Click App Management Settings in the left sidebar.
Toggle on Approve apps.
Tip: For apps that require approval, set expectations with your team by letting them know how long it’ll take to review their app requests.
4. Develop an approval policy
Whether members are requesting apps or installing them as needed, protect your workspace by developing an app approval policy with help from your IT, security, and policy teams.
Carefully consider internal protocols around data management to craft a policy that feels right for your team. Here are some questions to include in your review:
Is there a valid business reason for using the app?
Are there other apps being used for this purpose?
How long will the app be needed on the workspace?
How often will the app post to a channel?
Are there any additional costs or licenses?
Creating internal integrations
Who will maintain the integration?
Are additional servers, databases, or integrations needed?