Slack permissions and historical search
What workspace admins enable when they install Arialine's recent and historical context features.
Written By Andrii
Last updated 17 days ago
Arialine receives new message events only in conversations covered by the app's installed scopes and Slack access. Those events support the 72-hour recent-context buffer. The search:read.public scope separately lets Arialine use Slack Real-time Search after a member explicitly invokes it. For the most reliable older-discussion search, mention @Arialine; Slack supplies the user-initiated action token on that event. Slack makes Real-time Search available to directory-published and internal apps. A workspace installed before Arialine requested this scope may need an admin to reauthorize the app before historical search works.
Public-channel search returns only content Slack permits for the invoking member and installed app. It can find older messages that Arialine did not receive as events. Keyword search is available without Slack AI Search. Semantic matching depends on the workspace's Slack AI Search capability. Arialine does not sell semantic search as a separate plan and does not persist Real-time Search results as a conversation archive.
Who can see a board. Arialine can read every channel it has been invited to, but it only shows or changes a board for someone who could open that board's channel in Slack. This applies to @mentions, App Home, 📌, exports and Slack's built-in assistant. When you name a board yourself, Arialine uses it if you can open it. When Arialine finds an answer in a board from another channel that some people in the current channel can't open (a private channel they aren't in, or guests and Slack Connect partners here), it first shows the answer only to you, with a warning and Yes, post it / No. Nothing is posted for the channel unless you choose Yes; the posted answer notes who shared it and from which channel.
This release does not request the user-token scopes required for private-channel, DM, or group-DM historical search. Adding those sources would require a separate consent flow and an updated admin review. Admins can review the requested scopes during installation and remove Arialine to stop new processing. Use the Privacy Policy and Contact support for retention, deletion, or access questions.
Was this helpful?
Still need help? Ask the team