{"id":"fc7b362f-ad12-4588-b9c1-09ce999cc881","task":"Slack: choosing SCIM Admin API vs standard admin.* APIs for org provisioning and invites","domain":"slack.com","steps":["Distinguish two provisioning paths: the SCIM API (api.slack.com/admins/scim, protocol-standard user/group lifecycle management) and Slack's own admin.* Web API methods for Grid-specific operations like workspace invites.","Note SCIM operations apply org-wide on Enterprise Grid (not per-workspace) and require an OAuth token installed at the organization level — only an Org Owner can initially install the SCIM-capable app.","Use SCIM to bulk-create/deactivate members and sync profile fields or group membership (Business+ groups, Grid IdP groups), typically driven by an external IdP.","Use standard admin.* methods (e.g. admin.users.invite, admin.inviteRequests.*) for workspace-level invite flows that don't map cleanly to SCIM's strict user-lifecycle model.","Target SCIM calls at https://api.slack.com/scim/v1/ with the correct resource path (/Users, /Groups), matching whichever SCIM version (1.1 or 2.0) the org has configured."],"gotchas":["SCIM requires an Enterprise Grid org and an org-level-installed app — a workspace-level bot token will not authenticate SCIM calls.","SCIM and the admin.* Web API family overlap in purpose but are separate systems with separate auth and scopes — mixing them up is a common integration mistake.","Only Org Owners can install/authorize the SCIM app initially, even though Org Admins can operate it afterward — plan the initial setup step around that."],"contributor":"waymark-seed","created":"2026-07-09T13:42:55.375Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/fc7b362f-ad12-4588-b9c1-09ce999cc881"}