Skip to content

Latest commit

 

History

History
26 lines (13 loc) · 2.92 KB

account-model-with-subaccounts-049d331.md

File metadata and controls

26 lines (13 loc) · 2.92 KB

Account Model with Subaccounts

This simple account model shows how to structure your global account into three subaccounts, without making use of directories. It can later easily be expanded to make use of directories as further structuring elements.

In this scenario, the IT department creates separate Dev, Test, and Prod subaccounts for their development projects in different functional areas. In addition to the structuring according to functional areas, you can create separate dev, test, and prod subaccounts for large projects that use different components or services and have a completely separated support process and operations model than your other projects.

With a separate account landscape per functional area, you can use multiple instances of the same SaaS subscription (e.g. in case you need to keep data or user access separated). For example, HR subaccounts would use an internal identity provider, whereas for public or external scenarios, an external identity provider could be used.

Using this account model, you can distribute the subaccount administration to several teams, which allows for easy scaling as the number of cloud projects grows while still having a manageable amount of maintenance and governance efforts. If possible, consider assigning responsible colleagues to each group of three subaccounts, i.e. to each account landscape.

A SaaS application can only be used once within a subaccount, so if each functional area has their own subaccount (for dev, test, and prod), you won't encounter limitations as to using the same SaaS offering in different projects. Still, in the Cloud Foundry environment, you can separate different projects within a subaccount into different spaces.

In the Cloud Foundry environment, if you use a central Fiori Launchpad, and you want to deploy applications that use it in a different subaccount, use the Launchpad Module. If you want to create applications in the same subaccount as the Fiori launchpad, we recommend to deploy them to the HTML5 repository as described in Developing HTML5 Applications.

Tip:

We recommend adding directories to structure your subaccounts, as soon as you have more than three subaccounts: Account Model With Directories and Subaccounts.

Related Information

Account Model With Directories and Subaccounts