Decide whether to approve a SaaS app an employee requested
Reviews a requested cloud app's data access, permissions, and vendor security to recommend approve, approve with conditions, or decline.
The prompt
Help me decide whether to approve a SaaS app or browser extension that an employee requested.
App and vendor: [NAME, website]
Who wants it and why: [team, business need, number of users]
Data it will touch: [e.g. "customer emails", "source code", "nothing sensitive"]
How it connects: [SSO? OAuth scopes requested - PASTE them; API keys; browser extension permissions; file uploads]
What I know about the vendor's security: [certifications, privacy policy notes, data location, AI training on customer data, breach history I found]
Existing approved tools that do something similar: [LIST - or "none"]
Cost and contract: [free tier / paid / click-through terms]
Assess:
1. Data risk: what is the worst case if this vendor is breached or misuses data?
2. Access risk: are requested permissions broader than the use case needs (e.g. "read all mail" for a scheduling tool)?
3. Vendor basics: SSO and MFA support, admin controls, audit logs, data retention and deletion, whether our data trains their AI models, and where data is stored.
4. Overlap with tools we already pay for.
5. Exit: can we export data and remove access easily?
Return:
- Recommendation: approve / approve with conditions / decline, with the reasons in 3 bullets.
- Conditions if approved (e.g. "SSO only", "no customer data", "review in 6 months").
- Questions to send the vendor for anything I marked unknown.
- A short, friendly reply to the requester explaining the decision.
Do not state facts about the vendor I did not provide; list them as things to verify.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Thinking & Decisions prompts
What to fill in
- NAME, website
- team, business need, number of users
- e.g. "customer emails", "source code", "nothing sensitive"
- LIST - or "none"
- free tier / paid / click-through terms
How this prompt is built
This prompt follows the Few-Shot structure (Few-shot prompting). A few-shot prompt includes one or more worked examples of the input and the output you want, so the model can copy the pattern instead of guessing it.
Related prompts
- Choose my classes for next semesterA balanced class schedule that meets your requirements, avoids an overloaded term, and has backups ready for registration day.
- Build a downturn playbook with trigger points and pre-agreed actionsA staged plan linking specific warning signals to pre-agreed actions, so the leadership team acts early instead of debating under pressure.
- Decide whether to scrap, rework, or use nonconforming partsA Material Review Board recommendation on nonconforming material, weighing risk, cost, and customer approval, with the disposition written up for the record.
- Design an employee wellness program people actually useA needs-based wellness program with mixed offerings, policy fixes, an engagement plan, privacy-safe measurement, and a 12-month roadmap.