As an admin, you should never assign entitlements randomly.
Every entitlement:
-
allows resource usage
-
may have cost implications
-
affects what developers can do
So even in a trial account, we do this carefully and intentionally.
Entitlements are always:
-
assigned at subaccount level
-
based on what is available at global account level
This means:
-
admins don’t assign entitlements to spaces
-
admins don’t assign entitlements to users
-
admins assign entitlements to subaccounts
In real projects, admins usually don’t guess.
They ask questions like:
-
What type of application is being built?
-
Which environment is used?
-
Which services are mandatory?
-
Which services are optional?
Only after this discussion are entitlements assigned.
Step 1: Go to the Entitlements section
This page shows:
-
which services are already allowed
-
which plans are available
-
what quota is assigned
In the latest SAP BTP cockpit, the option earlier called “Configure Entitlements” is now shown as “Edit”.
The functionality is the same — this is where admins manage service entitlements for the subaccount
This is the screen where admins actually work.
Here, SAP shows:
-
all services available in the Global Account
-
which ones are already assigned to this subaccount
After clicking Edit in the Entitlements section, I clicked on Add Service Plans.
This is the screen that opens.
Step 3: Select the plan and quota and save the entitlement
Here, SAP is asking a very simple question:
Which service, and which plan of that service, should this subaccount be allowed to use?
Note: In trial account we have limitations what to choose.
Step 6: Check the Service Marketplace
Now go back to the Service Marketplace.
You’ll notice something important.
The service you just entitled is now:
-
visible in the marketplace
-
available with the plan you selected
This is where the connection becomes clear:
Entitlements control what appears in the marketplace.
Comments
Post a Comment