Slack access logs
Collect workspace sign-in records with the Slack access-log pull feed
Collect workspace sign-in records through team.accessLogs. This connector reads access logs, not the Audit Logs API. It uses source type slack_access_log and parser slack_access_ocsf.
Availability and permissions
Collect with a Slack pull feed on any edition, or on Self-run with the Slack Marketplace collector. Review the pull permissions matrix.
The manifest requires Business+ or Enterprise Grid: check whether User Token Scopes offers admin before configuring collection. A bot token cannot read these access logs. The collector has no refresh flow for tokens that expire through token rotation.
Setup
1. Create the vendor app and token
Create an app for your workspace at the vendor's app management site. Under User Token Scopes, add admin, install the app to the workspace, and copy its User OAuth Token. Use the xoxp- user token, rather than an xoxb- bot token. Leave Advanced token security via token rotation off for this collector.
2. Add a pull feed
Publish the slack_access_ocsf parser for the slack_access_log log source under Ingestion → Log Sources. Then open Ingestion → Log Sources → Pull feeds, add a Slack feed, and set:
| Field | Value |
|---|---|
User token (USER_TOKEN) | The user OAuth token with admin. It is stored in the credentials store and never shown again. |
Team ID (TEAM_ID) | Optional workspace ID for an org-level Enterprise Grid token. Leave blank for a workspace token. |
On Self-run you can instead install Slack from the Marketplace, open Connections → Connect tenant, set the same fields, and enable the access_logs stream (Sign-in records).
3. Verify collection
Check the feed's last status and runs on Pull feeds (or per-stream event counts and staleness in Connections), then search:
metadata.log_source="slack_access_log" | head 20Collection is scheduled hourly, with a five-minute run budget. Check the next scheduled run and its result before diagnosing an empty search.
Streams and fields
The access_logs stream contains sign-in records with user, IP, device, and network information. Records are mutable aggregates: a later response can update count and date_last for the same user, IP, and user agent. The collector's watermark uses date_last, falling back to date_first.
Troubleshoot
Need help with these checks? Contact support with the deployment, request ID and time with timezone.
The scope is unavailable
Check the workspace's User Token Scopes picker. If admin is absent, this connector cannot run there. Do not substitute auditlogs:read: that belongs to a different API.
Authentication fails
Check the user token, its admin grant, and whether it was revoked or expired. Replace the token in the credential store. Do not use a bot token or enable rotation that requires an unsupported refresh flow.
No recent events appear
Check the hourly schedule, per-stream run result, and selected workspace. For an org-level token, verify TEAM_ID. Access-log aggregates can be updated rather than representing one immutable row per sign-in.