Change tip to warn

Author: ThumulaPerera

en/developer-docs/docs/administer/configure-access-control.md

@@ -54,7 +54,7 @@ Follow the steps given below to assign the **Developer** role to the **Engineeri
 6. In the **Assign Roles to Group in Project** dialog that opens, click the **Roles** list and select **Developer**.
 7. Click **Selected Environments** radio button under **Applicable Environments**
 
-!!! tip
+!!! warning "Important"
     Configuring the Applicable Environment for a Role to Group assignment is currently available only for selected organizations.
 
 8. Select **Development** environment from the environment selecction dropdown 

en/developer-docs/docs/choreo-concepts/access-control.md

@@ -70,7 +70,7 @@ By combining these attributes, you can create four types of assignments.
 |`Environement Scoped`|Organization|Environment|
 |`Project-Environment Scoped`|Project|Environment|
 
-!!! tip
+!!! warning "Important"
     Configuring the Applicable Environment for a Role to Group assignment is currently available only for selected organizations.
 
 !!! warning "Important"
@@ -117,7 +117,7 @@ For environement scoped assignments, allowing **non environment specific** actio
 !!! example
     Suppose you assign the Developer role to the Engineering Developer group, but only for the Development environment of the Engineering project. The purpose of this assignment is not to prevent developers from performing actions like `build component`, which don’t depend on a specific environment. Instead, the goal is to restrict developers from performing actions such as `promote component` on environments they aren’t authorized to access, like Production.
 
-!!! tip
+!!! warning "Important"
     Environment Scoped Assignments are currently available only for selected organizations.
 
 !!! warning "Important"
@@ -131,7 +131,7 @@ For environement scoped assignments, allowing **non environment specific** actio
 
 Similar to previous case, allowing **non environment specific** actions on resources across project is intentional. This design aligns with real world Access Control use cases.
 
-!!! tip
+!!! warning "Important"
     Project-Environment Scoped Assignments are currently available only for selected organizations.
 
 !!! warning "Important"

en/pe-docs/docs/choreo-concepts/access-control.md

@@ -70,7 +70,7 @@ By combining these attributes, you can create four types of assignments.
 |`Environement Scoped`|Organization|Environment|
 |`Project-Environment Scoped`|Project|Environment|
 
-!!! tip
+!!! warning "Important"
     Configuring the Applicable Environment for a Role to Group assignment is currently available only for selected organizations.
 
 !!! warning "Important"
@@ -117,7 +117,7 @@ For environement scoped assignments, allowing **non environment specific** actio
 !!! example
     Suppose you assign the Developer role to the Engineering Developer group, but only for the Development environment of the Engineering project. The purpose of this assignment is not to prevent developers from performing actions like `build component`, which don’t depend on a specific environment. Instead, the goal is to restrict developers from performing actions such as `promote component` on environments they aren’t authorized to access, like Production.
 
-!!! tip
+!!! warning "Important"
     Environment Scoped Assignments are currently available only for selected organizations.
 
 !!! warning "Important"
@@ -131,7 +131,7 @@ For environement scoped assignments, allowing **non environment specific** actio
 
 Similar to previous case, allowing **non environment specific** actions on resources across project is intentional. This design aligns with real world Access Control use cases.
 
-!!! tip
+!!! warning "Important"
     Project-Environment Scoped Assignments are currently available only for selected organizations.
 
 !!! warning "Important"

en/pe-docs/docs/user-management/groups-and-roles/configure-access-control.md

@@ -54,7 +54,7 @@ Follow the steps given below to assign the **Developer** role to the **Engineeri
 6. In the **Assign Roles to Group in Project** dialog that opens, click the **Roles** list and select **Developer**.
 7. Click **Selected Environments** radio button under **Applicable Environments**
 
-!!! tip
+!!! warning "Important"
     Configuring the Applicable Environment for a Role to Group assignment is currently available only for selected organizations.
 
 8. Select **Development** environment from the environment selecction dropdown