Skip to main content
Once Claude Tag in Slack is connected to AccessOwl, your team handles day-to-day access work by mentioning @Claude in a channel, in their own words. There is no syntax to learn: describe what you need the way you would ask a colleague. This page shows what that looks like, using an HR channel as the running example. Two things stay true for everything on this page:
  • Claude requests; it never grants. Every request follows your approval policies, and everything shows up in AccessOwl as usual, so your audit trail stays complete.
  • Claude confirms before creating anything. Read-only questions are answered directly.

​
What a conversation looks like

AccessOwl already announces new joiners and leavers in your HR Slack notification channel. Invite Claude into that channel, and the announcement and the follow-up work live in one thread:
You: @Claude Maria starts Monday in Marketing. She needs Slack, Notion, and a HubSpot Marketing seat. Claude: Ready to submit access requests for Maria Schmidt:
  • Slack: Member
  • Notion: Member
  • HubSpot: Marketing seat
OK to submit? You: yes Claude: Done. I submitted 3 access requests for Maria. They now go through your normal approval flow.
Claude looked up the user, checked which roles each application offers, and asked before creating anything. If an application requires a mandatory resource such as a seat, Claude asks which one to include instead of guessing.

​
What you can ask

Giving someone the same access as a colleague

​
Best practices

  • Keep the channel small. Everyone in the channel acts with the same Org Admin permissions. Use a private channel for IT and HR.
  • Be specific about people. Use email addresses when two colleagues share a name.
  • Let approvals stay with your approvers. Claude creates requests only; approving them happens in your normal flow, in Slack or the AccessOwl interface.
  • Speak naturally. The phrasings above are examples, not commands. “Tom needs Notion” works just as well as a formal request.
Don’t set it up that way. The API token acts as an Org Admin, so Claude could grant a request if told to explicitly, but approvals are your control point. Let Claude create requests and leave approving them to your managers and Business Owners in the normal flow.
Connections set up through an Access bundle apply to channels. For access work, use a channel that Claude has been invited to.
Claude can only see what exists in AccessOwl. Users come from your connected directory, and applications are added in AccessOwl, where you can pick them from the catalog and connect an integration.