Merge pull request #8953 from Trkyyy/development

Add release notes for Sprintr 2025.01.26

content/en/docs/control-center/people/roles-permissions.md

@@ -8,71 +8,33 @@ no_list: true
 
 ## Introduction
 
-On the **Roles & Permissions** page in Control Center, you can view and manage project roles and permissions. Additionally, you can migrate default project-level roles to centralized company-level roles.
-
-## Default Project Roles
-
-Default project roles are the default [team roles](/developerportal/general/app-roles/#team-roles) assigned for every new project created in your company.
-
-{{< figure src="/attachments/control-center/people/roles-permissions/roles-permissions.png"  alt="Roles & Permissions page" >}}
-
-To create a new role, click **Create Project Role**.
-
-To edit a role, click **Edit Role**.
-
-To delete a role, click **Edit Role** and then **Delete Project Role**.
-
-You can not edit or delete the **SCRUM Master** role.
+On the **Roles & Permissions** page in Control Center, you can view and manage centralized company-level project roles and permissions.
 
 ## Centralized Project Roles
 
-### Migrating to Centralized Company-level Project Roles {#migrate-centralized-roles}
-
-#### Why Migrate?
-
-Previously, project roles were managed at the individual project level. This allowed Scrum Masters of a project to create custom project roles within their specific project, even though Mendix Admins could create templates for project roles at the company level.
-
-Mendix has now centralized project roles at the company level. To take advantage of this update, you just need to migrate all individual project roles to the new centralized project roles. This will enhance your ability to govern access across all Mendix projects and also enable the programmatic assignment of project roles via [the Mendix Projects API](/apidocs-mxsdk/apidocs/projects-api/).
-
-{{% alert color="warning" %}}
-Mendix expects you to migrate to centralized company-level project roles by January 26, 2025. We will auto migrate all remaining companies on January 26, 2025.
-{{% /alert %}}
-
-#### How to Migrate?
-
-{{% alert color="warning" %}}
-Migrating to the centralized company-level project roles is a permanent action. Once it is done, it cannot be reversed.
-{{% /alert %}}
-
-To migrate to centralized company-level project roles, click **Learn More** on the blue banner at the top of the page and follow the outlined steps to complete the migration.
-
-{{< figure src="/attachments/control-center/people/roles-permissions/learn-more.png"  >}}
-
-#### After the Migration
-
-The results of migrating to the centralized company-level roles will be as follows:
+All companies use centralized project roles. This means:
 
 * Mendix Admins will be the only ones who can create or modify project roles.
 
 * Scrum Masters and team members will only be able to view the project roles established by Mendix Admins and select the appropriate one. They will not have the ability to modify the permissions of project roles. If a custom permission set is needed, they must reach out to a Mendix Admin for assistance in creating it.
 
-* If there were any old custom project roles before the migration, they will appear with the tag **Inherited from project** on the **Roles & Permissions** page in Control Center. Mendix Admin can review these custom project roles, keep the useful ones, and merge any duplicates.
+* Some roles will appear with the tag **Inherited from project** on the **Roles & Permissions** page in Control Center. A Mendix Admin can review these custom project roles, keep the useful ones, and merge any duplicates.
 
   {{% alert color="info" %}}
-  When members of your company  [invite someone to an project](/developerportal/general/team/#inviting), they cannot select any old custom role with the tag **Inherited from project** shown here, as these roles will not be shown to them.
+  When members of your company  [invite someone to an project](/developerportal/general/team/#inviting), they cannot select any role with the tag **Inherited from project** shown here, as these roles will not be shown to them.
   {{% /alert %}} 
 
 ### Project Roles Overview
 
-On the **Roles & Permission**s page, you have an overview of all centralized project roles. Per role you see a brief summary of the permissions that the role has as well as in how many projects and by how many team members they are used.
+On the **Roles & Permissions** page, you have an overview of all centralized project roles. You will see a brief summary for each role of the permissions that the role has as well as in how many projects and by how many team members they are used.
 
 Clicking the number of projects that use the role opens up a pop-up window with a list of projects where the role is used.
 
 From the overview page you can **Create**, **Edit**, or **Delete** a role.
 
 ### Creating a Role
 
-To create a role, do as follows:
+To create a role, do the following:
 
 1. At the upper-right corner of the page, click **Create Project Role**. A wizard opens to guide you through the steps to set up the new role.
 
@@ -93,7 +55,7 @@ To create a role, do as follows:
 
    {{< figure src="/attachments/control-center/people/roles-permissions/edit-project-role-step-3.png" alt="Project Role Step 3" >}}
 
-   Set the environment permissions for non-productive environments, such as the test or acceptance environments, as instructed below. These permissions are applied to the assigned team members on the [Permission](/developerportal/deploy/environments/#permissions) page in the Cloud Portal.
+   Set the environment permissions for non-productive environments, such as the test or acceptance environments, as described below. These permissions are applied to the assigned team members on the [Permissions](/developerportal/deploy/environments/#permissions) page in the Cloud Portal.
 
    1. Set the correct access rights.
    2. For **Permission Management**, you can select **Fixed** or **Custom**. 
@@ -104,7 +66,7 @@ To create a role, do as follows:
 
     {{< figure src="/attachments/control-center/people/roles-permissions/edit-project-role-step-4.png" alt="Project Role Step 4" >}}
 
-    Set the environment permissions for productive environments as instructed below. The permissions you set here will be fixed for this role. They cannot be altered later on the [Permission](/developerportal/deploy/environments/#permissions) page in the Cloud Portal.
+    Set the environment permissions for production environments as described below. The permissions you set here will be fixed for this role. They cannot be altered later on the [Permissions](/developerportal/deploy/environments/#permissions) page in the Cloud Portal.
 
     1. Set the correct access rights.
     2. For **Permission Management**, you can select **Fixed** or **Custom**. 
@@ -113,11 +75,11 @@ To create a role, do as follows:
 
         * If you select **Custom**, you allow anyone with Manage Permissions rights, for example, the Technical Contact, to set the permissions per environment.
 
-    {{% alert color="warning" %}}Editing and saving the productive environment permissions can only be done after a **multi-factor authentication** has taken place.{{% /alert %}}
+    {{% alert color="warning" %}}Editing and saving the production environment permissions can only be done after a **multi-factor authentication** has taken place.{{% /alert %}}
 
 ### Showing Details
 
-To show the details of a role, click **Show Details**. The **Project Role Details** pop-up window opens with detailed information of the role.
+To show the details of a role, click **Show Details**. The **Project Role Details** pop-up window opens with detailed information about the role.
 
 {{< figure src="/attachments/control-center/people/roles-permissions/project-role-details.png" alt="Project Role Details" >}}
 
@@ -127,7 +89,7 @@ In the **Project Role Details** pop-up window, you can find the role ID that can
 
 ### Editing a Role
 
-To edit a role, do as follows:
+To edit a role, do the following:
 
 1. Click **Edit Role** for the role you want to edit.
 2. Make the changes.
@@ -143,7 +105,7 @@ You cannot edit the Scrum Master role. This ensures that there is always someone
 
 ### Deleting a Role
 
-To delete a role, do as follows:
+To delete a role, do the following:
 
 1. Click **Edit Role** for the role you want to delete.
 2. Review the role.

content/en/docs/developerportal/general/team/_index.md

@@ -19,18 +19,14 @@ To view and manage your team members, follow these steps:
 
 Team members with the [Scrum Master](/developerportal/general/app-roles/#team-roles) role or [Mendix Administrators](/control-center/company-settings/#mendix-admins) can manage the app team.
 
-{{< figure src="/attachments/developerportal/general/team/team.png" class="no-border" >}}
+{{< figure src="/attachments/developerportal/general/team/team.png" >}}
 
 On the **Overview** tab, you can do the following:
 
 * Select a new **Role** for a team member (for details on available roles, see [App Roles](/developerportal/general/app-roles/))
 * Click **Remove** to remove a user from the team
 * Click **Invite New Member** to invite a new user to the team (for more information, see the [Inviting Team Members](#inviting) section below)
 
-Navigate to the **Role Settings** tab to view and edit permissions for the team roles as well as to **Add New Role**:
-
-{{< figure src="/attachments/developerportal/general/team/role-settings.png"   width="400"  class="no-border" >}}
-
 Navigate to the **Pending Invites** tab for an overview of all sent and unaccepted invitations. You can retract pending invitations from there.
 
 ## Inviting Team Members {#inviting}

content/en/docs/developerportal/general/team/app-roles.md

@@ -36,11 +36,7 @@ Within a team, there are predefined roles that can be provisioned to team member
 * Who has the [node permissions](/developerportal/deploy/node-permissions/) for access to the node information
 * Who can change the app's [Settings](/developerportal/collaborate/general-settings/)
 
-Scrum Masters can edit and create new team roles on the [Team](/developerportal/general/team/) page, and Mendix Admins can edit and create new team roles within the company in [Control Center](/control-center/).
-
-{{% alert color="info" %}}
-It is not possible to maintain project dedicated roles, if your company is using [Centralized Project Roles](/control-center/roles-and-permissions/).
-{{% /alert %}}
+Mendix Admins can edit and create new team roles within the company in [Control Center](/control-center/roles-and-permissions/).
 
 ## Technical Contact {#technical-contact}
 

content/en/docs/releasenotes/developer-portal/_index.md

@@ -19,6 +19,12 @@ To see the current status of the Mendix Portal, see [Mendix Status](https://stat
 
 ## 2025
 
+### January 26, 2025
+
+#### New Features
+
+* We have migrated all companies to use [Centralized Roles](/control-center/roles-and-permissions/#centralized-project-roles). 
+
 ### January 5, 2025
 
 #### Deprecations

layouts/partials/landingpage/latest-releases.html

@@ -13,7 +13,7 @@ <h4 class="lp-panel-title">Latest Releases</h4>
     </li>
     <li class="lp-panel-list">
         <a href="/releasenotes/developer-portal/">Apps</a>
-        <p class="rn-date">Jan 5, 2025</p>
+        <p class="rn-date">Jan 26, 2025</p>
     </li>
     <li class="lp-panel-list">
         <a href="/releasenotes/developer-portal/deployment/">Deployment</a>