The Authorization Workspace allows you to setup your B2B organization’s policies, or authorizations.
The first step is setting up Assets & Conditions. Asset Types are classes of assets that will define the nature of an asset, its attributes, actions, rulesets, and finally the assets themselves. For example, an asset type could be named Airport, and the airport assets might be MIA, JFK, LGA, and so on.
Conditions are restrictions placed to access your systems, such as date, time, IP, member, or request attribute.
Not all the configurations above are needed to create a policy, but a few will be required.
After setting Assets & Conditions, you can connect them with a policy, and then expose your policies and other B2B functionality to your legacy infrastructure (services and applications) using an application. With all of these set up and in place, you can embed and enforce B2B Authorizations for your third-party applications across your legacy systems and other connected services.