Request the access a new joiner needs, with a person approving
An access request with an explicit approver and a written record of the decision. Built for an IT lead who grants access by message and remembers it later, if at all.
Notion
Slack
4 steps2 integrationsRuns on demand
Access is granted by message and forgotten. What it costs while the work is still done by hand.
- 01Access requests arrive informally and are granted ad hoc.
- 02There is no record of who approved what.
- 03Leavers keep access nobody remembers granting.
- Read roleSupport Engineer · 6 systems
- Build list6 systems · levels set
- Ask approverpost_message · IT lead
- Record grantapproved · 6 tasks created
One workflow, four steps. ModuleX drafts this graph from a single sentence, and every step stays editable.
- 01Read the role and the access it should carry.Notion
- 02Assemble the list of systems and the level for each.ModuleX
- 03Send the request to the approver with the full list.Slack
- 04On approval, record the decision and open the provisioning tasks.Notion
The workflow is an editable graph. Reading runs freely; send the request to the approver with the full list waits for your opt-in approval until you loosen it. The graph is the receipt.
Requested, approved, recorded. Paste this into ModuleX chat, or hit Use this workflow.
request the access a new joiner needs, with a person approving: read the role and the access it should carry; assemble the list of systems and the level for each; send the request to the approver with the full list; on approval, record the decision and open the provisioning tasks. Ask me before anything is sent or written.
to: composerOr skip the workflow entirely. Ask the assistant in chat and it runs the same job agentically: it picks the right actions, chains them, and reports back. The composer is for when you want it repeatable.
Request the access a new joiner needs, with a person approving. An access request with an explicit approver and a written record of the decision.
- notion · create_page
- slack · post_message
An access request with an explicit approver and a written record of the decision.
Where this fits. The tools it runs on, and the teams that run it.
Keep the momentum. Nearby workflows that reuse the accounts you just connected.
Brief yourself on a candidate before the callA brief covering the role, the application, and what earlier rounds already established. Built for an interviewer who opens the CV two minutes before the interview.- Prepare everything a new joiner needs on day oneA per-role onboarding checklist with real owners and dates, created before the start date. Built for an operations lead who assembles the same onboarding list every time, from memory.
Prepare an offer and send it for signatureAn offer letter produced from the approved details, checked by a person, then sent for signature. Built for whoever assembles offer letters from a template and hopes the numbers are right.
About this use case.
No. It requests, records, and opens tasks. Granting stays with the people who hold that responsibility.