One place for everything that needs a person before it happens.
What shows up here
- Exports of customer contact details in bulk (rule BASE-04).
- Company knowledge suggestions, like saving a definition people keep asking about.
- Actions: things Runmate will do in another app or send, like a draft Shopify product someone asked for in Ask, or a run's results going to someone outside your company. The request shows exactly what will happen. Approve does it right away and shows the result; Decline cancels it.
- Support access requests from Runmate, with a reason and an end time.
Who can decide
Each request says who it needs. "Needs a Client admin" means only a Client admin can approve or decline it. Everyone with access can still see what's waiting.
Deciding
Give a short reason, then Approve or Decline. The outcome shows at the top of the page, and the decision, the reason and who made it are kept in History and the audit log. A decided request can't be changed.
Approving a company-knowledge suggestion adds the definition to your company's knowledge, so answers use it from then on.
What sends without approval
By default every email Runmate sends, such as a run's results or an alert, waits here first. A Client admin can turn on Emails to people on your team send without approval at the bottom of this page. Then results and alerts to people who are members of your workspace go out on schedule.
Some emails still wait here whatever the setting:
- emails to anyone outside your company (rule BASE-07);
- a repeat of the same email to the same people within 7 days (a clash).
Every change to this setting is kept in the audit log.