Determine required systems and sufficient permission levels
Maps the engagement scope and method requirements against the client's known system landscape to produce a precise access request — naming each system, required access level, and the method step it enables.
In / outMethod system requirements + client system landscape → named access request (system, level, purpose) for each required credential
You might say…
“I ask for 'read access to your analytics platform' and three weeks later we're still negotiating because nobody specified which platform, which account, or what role.”
What it does
Works out which accounts, platforms, and tools the methodology needs and the minimum permission level each analysis step requires, so the access request is correct first time. Used before requesting credentials. Single judgement call balancing analysis needs against least-privilege.
Trigger: Use when the methodology requires direct system access and you need to translate method requirements into a concrete, actionable access request the client's IT team can process.
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation