Portal
Environments, people and roles, releases, billing, your profile.
Usage and invoices: what your organisation costs
Flow charges a monthly price per environment and per person, counted per day. Under Usage and invoices you, as an owner, see what an organisation has cost so far this month, what to expect for the whole month, what the amount is made of and which prices apply.
Your profile: password and recovery codes
Under your avatar at the top right you manage your own account. You change your password, sign out, and sign in again with the new password and a recovery code, as you would when your phone with the authenticator app is not at hand. Then you see how many recovery codes you have left and make new ones.
Your organisation's settings
Behind your organisation's name is Settings. There an owner changes the name, a colleague leaves the organisation and an owner deletes it, in the danger zone. You switch Governance on on a page of its own.
Environments: add, configure, restart
Every environment of your organisation is a Flow of its own, with its own database and address. In the portal you add a test environment, open an environment's settings, give it its own key for an AI model and restart it. A tour of every setting is in ‘One environment and its settings’.
People: change roles and remove someone
Under People you manage who works in your organisation. You make a colleague co-owner, revoke an invitation that is no longer needed, and take someone out of the organisation. You also see what that means for that person. Where everything is in the new portal, you read in ‘The new portal: where to find what’.
Releases: what was promoted when
Releases → History is your organisation's log: every time a version moves on to the next environment, it is there, with a note, who did it, when and what changed. You publish a version with a note and table data, and read back what was recorded. Putting a version into Production step by step is in ‘Put a version into Production’.
Share a module through the marketplace
What you built well once, you do not want to build again in every environment or branch. You publish a module as a package in your organisation's own catalogue, with a version and a release note. Colleagues find it in the portal's marketplace, see what it asks and install it into Development; it then travels with the normal releases. Only the design goes along: no rows, no secrets, no conversations.
Two owners in the portal
An organisation often has more than one owner, and they do not take turns. People follows what the other does by itself: an invitation from your fellow owner appears in your list, with who sent it. When the other was just ahead of you, the portal says so in plain words, with who and when — and nothing changes that you did not see. Whoever makes themselves less than an owner is asked first. Below you see both owners' screens side by side.
Platform admin: help customers and update every environment
Whoever runs Flow for others works under Admin: Overview, Customers, Updates, Contact and Marketplace. There you find every organisation, invite people into an organisation, open the settings of any environment and bring every environment to a new Flow version in one round: the personal Flows first, then Development, Test and Acceptance, Production last. Customers see the round coming beforehand. A customer makes their organisation themselves.