Good to know
- Permissions are exact names with no wildcards, and a name that is renamed or removed is announced as a breaking change.
- The Owner role moves only by transferring ownership, and a key can never hold it.
Capability area
Access and drivers
Decide who may do what in your organization, with named permissions and provided policies checked on every request.
Give each person and key exactly the reach they need
Everything a caller may do is a named permission. Give people and API keys the provided policies, checked on every request.
Every action has a name such as asset.charger.read, a policy is a set of permissions, and a binding gives a policy to a member or an API key across the organization or in one project. Flowion provides Owner, Admin and User, plus Charging, which lets a person who charges start a charge. A fourth, Statements, goes to the people who bill residents.
Access is checked on every request against what each member and key holds now, so removing a binding applies to the very next request. If the check cannot be made, the request is refused. You can only give what you hold.
Being the Owner does not make a card charge: no management policy allows starting a charge.