FlowData

How do I share FlowData with my team, and what happens to my colleagues' keys?

Published on 10. November 2026

FlowData is a separate product with its own access. As the owner of your team you always have it; everyone else only gets it once you or someone with team management rights grants it. This article explains how to give colleagues access, who sees which keys and what happens to integrations when someone leaves the team.

Who has access to FlowData?

  • The Owner always has FlowData, as do Co-owners you have given full access.
  • All other members need FlowData access to be granted.

Without access, a person can't open FlowData or create FlowData keys.

Granting FlowData to someone

  1. In FlowData, open Team under More on the left. You see it if you manage the team or are allowed to manage FlowData.
  2. Click Invite person.
  3. In the Invite to FlowData dialog, pick a team member from the suggestions or enter an email address. Separate several addresses with a comma or a line break.
  4. Confirm the dialog.

Members of your team get access right away. New addresses receive an invitation that applies to FlowData only.

The FlowData team page lists everyone with access and their role: Owner, Co-owner, Product admin or Member. The switch in the Manage product column lets a person grant FlowData to others themselves. Only people with team management rights can flip this switch. You remove access with Remove access to FlowData in the person's row; they keep their other areas.

Learn more about roles and access in Granting product rights and Inviting people to one product only.

Who sees which keys?

  • Owners and people with team management rights see all of the team's FlowData keys under API keys. The Created column shows who created each key, under the date. They can edit and revoke other people's keys. Only the person who created a key can use Regenerate, though, so that nobody else ever learns its value.
  • Everyone else sees only their own keys.

Every key belongs to the person who created it. The statistics and log of the areas, on the other hand, count for the whole team.

A key suddenly returns 403

A FlowData key only works as long as the person it belongs to still has FlowData access. If their access was removed, every request with that key is answered with HTTP 403 and the code flowdata_access_denied:

{"error":{"message":"...","type":"permission_denied","code":"flowdata_access_denied"}}

If the person has left the team altogether, the response looks like this (the error field is always in German):

{"error":"Kein Teamzugriff","message":"..."}

In both cases, either give the person access again or replace the key in the integration with a new one created by someone who has access.

Keeping integrations running

  1. Create keys for important integrations like your shop or website with an account that will stay in the team, ideally the owner's.
  2. Before you remove someone from the team, check under API keys which keys belong to them and replace those in your integrations.
  3. Members and roles explains how to remove members.

Who can top up the balance and change limits?

Everyone with FlowData access can see Billing, top up the balance there and change the team's monthly spend limit, so only grant FlowData to people you trust with that. A key's own limit, however, can only be changed by the person it belongs to and by whoever manages the team.

Was this article helpful?

Back to Getting started & API keys