As a Slack admin, you're the person who approves the &Open app for your workspace, so it's worth knowing exactly what it can and can't do once it's installed. This guide walks through every permission the app requests and why it needs it. Most are read-only lookups, and the app is scoped as narrowly as the gift notification features allow.
What the integration does
Once connected, the &Open app lets your team:
Get notified in Slack about gifting activity, such as a gift invitation being created or redeemed, or a gift being fulfilled and delivered.
Look up a gift's status by gift recipient email with the
/andopenand/giftslash commands.Use the app's home tab as a way into &Open to set up and manage notifications.
The permissions we request, and why
When you install &Open, Slack shows you a consent screen listing the permissions ("scopes") the app asks for. Here is each one and the feature it powers.
App permissions (the &Open bot)
These let the &Open app act inside your workspace: post updates, answer commands, and work out who a gift belongs to.
Scope | Why it's needed |
| Post gift status updates and command replies as the &Open app. |
| Post gift updates into any public channel your team chooses, without someone needing to invite the app to it first. |
| Provide the |
| During installation you pick one initial channel for &Open notifications, and this lets the app post gift updates there. You can add more channels later with your own notification setups. |
| List your public channels so you can choose where notifications go, and confirm which channels the app can post to. |
| The same, for private channels you've invited the app into. |
| Match Slack accounts to gift senders and gift recipients, and show the right name in notifications and command replies. |
| Look up gifts by a gift recipient's email address. This powers the |
| Read your workspace name, domain, and icon so the app knows which &Open account this workspace connects to. |
Permissions tied to the person who connects
When you authorize the app, Slack also grants a small set of read-only scopes on your own account: channels:read, groups:read, users:read, and users:read.email. These let the app run the same channel and people lookups on behalf of the admin who set up the connection. They don't let &Open act as you or post on your behalf.
What we don't ask for
Just as important is what we don't request. The &Open app can't:
Read your messages or conversation history. We request no history scopes, so the app never sees the content of your channels or direct messages.
Access your files. We request no file scopes.
Manage your workspace. We request no admin, user-management, or workspace-configuration scopes.
The app only reads the directory information (channels, people, email addresses) it needs to route gift notifications, and only writes the gift updates and command replies described above.
Questions and answers
How do we remove the app or revoke access?
An admin can remove the &Open app from your workspace's app management settings at any time. This immediately invalidates the app's access tokens and stops all notifications. We read and write nothing after removal.
Does the app keep access indefinitely?
Installing the app creates access tokens that stay valid until the app is removed. Remove the app and they stop working straight away.
Who should install the app?
An account administrator. Installing and authorizing the app needs the right access in both &Open and Slack.
Can we connect more than one Slack workspace?
No. Each &Open account connects to a single Slack workspace.
Who do we contact with questions?
Email hello@andopen.co and we'll connect you with the right person on our team.