The new portal
Calmer: one question per screen, four fixed places in the bar, and your personal Flow always first.
The portal has been rearranged. Every screen answers one question, with plenty of space; details are one click deeper. Nothing has disappeared. The manual The new portal: where to find what says exactly where everything is now.
In short
Environments
Development → Test → Acceptance → Production in a row, with what waits for you at the top.
One environment, a short list
General, Secrets and keys, Add-ons, People here and the Danger zone.
Who may do what
Builders and colleagues side by side, with a small table of what each role may do.
Who may come in
Signing in through your company: only invited people, a group, or everyone on your domain.
One switch per capability
The chat with AI Colleagues and operating websites for all environments at once.
Marketplace
Find modules, install them and share your own.
What you can do
Start at Start
After signing in you first see your personal Flow, then your organisations. The bar at the top has four fixed places: Environments, Releases, People and Marketplace. The rest is behind the name of your organisation.
Look up where something is now
The Before → Now table lists every part of the portal: where it was, where it is now and how you get there.
Do the things you often do
Step by step: open your environment, put a version into Production, invite someone and update Flow.
The guides
Start and your personal Flow
After signing in you land on Start. At the top is your personal Flow, below it your organisations. The bar at the top has four fixed places: Environments, Releases, People and Marketplace.
Environments
Environments answers one question: is everything running? You see your environments in a row, from Development to Production, and at the top what waits for you. This is also where you add an environment.
One environment and its settings
Click an environment and you see a short list: General, Secrets and keys, Add-ons, People here and the Danger zone. Every setting has a page of its own. The list already shows how each one stands.
Releases
Releases shows what changed: every version of your work, and which environment it is in now. You also move a version on to the next environment here. At the bottom it says when there is a new version of Flow itself.
People and ‘Who may do what’
People answers the question who may do what. There are two kinds of people: builders, who work in the studio, and colleagues, who use what has been built. A small table shows per environment what each role may do.
Who may come in
Does your company sign in through its own sign-in service, such as Microsoft? Then you choose here who may come in: only people you invite, also people in a certain group, or everyone with an address of your company. Working at your company does not give access by itself.
Open my environment
You want to get to work in Flow. This is how you get from the portal into the right environment, in three clicks.
Put a version into Production
A version of your work goes to Production step by step: first to Acceptance, where the business tests and approves, then to Production. Each time you first see what changes. Only an owner promotes to Production.
Invite someone
You want to bring in a colleague or a builder. You invite them with an email address and a role. Only an owner invites. An invitation holds while whoever sent it may still do so; otherwise it waits for an owner.
Update Flow
There is a new version of Flow. You move all your environments to it with one button. It goes one after another, Production last. If an environment does not come up healthy, it goes back and it stops before Production.
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’.
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.
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.
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.
More that is new
Secrets and key vaults
Passwords, tokens and keys as a named secret nobody reads back, in Flow's own vault or in the one of your own cloud.
Governance
Quotes, projects, people and decisions in one place next to Flow, with gates, four eyes and a decision ledger you can have checked.
AI Colleagues build what is on the Board
Let an AI Colleague build an item that is ready: you approve the plan, follow it live and a colleague reviews the result.
The Board
The work from idea to done on one board, with cards that say what is still missing.
Dashboards
Everything your tables and workflows produce, at a glance, built the way you will see it.
The company home
One place where everyone starts the day: in your house style, with what matters to each role.
Security you can see
Who can open what, and why, explained in plain words everywhere in Flow.
RPA screenshots
See what the browser saw, right where you follow the run.