What FlowPins can and cannot do in your tenant.
People sign in with their Microsoft work account. FlowPins uses Microsoft’s supported interface. A person in your organisation confirms each change before it is written.
Your accounts, your roles.
- People sign in with their Microsoft work account. FlowPins never sees a password.
- An administrator of your organisation may be asked to approve FlowPins once, in Microsoft’s own consent screen.
- What a person can read or change in FlowPins depends on the role your organisation gives them.
- Each organisation’s data is kept apart from every other’s.
A person confirms. FlowPins writes.
- The assistant cannot write to your environment. Only a change a person confirmed is written.
- A confirmation covers the exact difference that person saw. If the change is altered, it has to be confirmed again.
- A copy of the flow as it was is stored before the change is written.
- FlowPins does not delete flows.
Sandbox first.
FlowPins starts with your sandbox environments. A production environment stays closed to changes until your organisation switches it on, and each change there needs a second confirmation.
Built to be checked.
Every confirmed change is recorded: who confirmed it, when, and what the difference was. The record stays with the flow’s history, so the question “what changed?” has an answer.
What we keep.
FlowPins stores your flow definitions and their history so changes can be reviewed; it does not store your business data or run contents.
Questions from your security or governance team?
Write to the address below. We answer in plain words.