Skip to content

Commit

Permalink
[SHIELD-730] Custom Applications permissions updates docs and release…
Browse files Browse the repository at this point in the history
… notes (#3116)

* docs: permissions updates release note

* docs: remove limitation

* docs: feature not announcement

* docs: rephrase

* docs: tech writers review

* docs: tech writers review - revert

* docs: tech writers review #2

* docs: change release date
  • Loading branch information
kark authored Jul 3, 2023
1 parent f7fdabe commit a8c1c11
Show file tree
Hide file tree
Showing 2 changed files with 15 additions and 17 deletions.
17 changes: 0 additions & 17 deletions website/src/content/help-needed.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -130,23 +130,6 @@ In the browser, the session token is stored in a secure cookie named `mcAccessTo

Custom Applications have the following limitations:

## OAuth Scopes cannot be changed in the Ready state

OAuth Scopes cannot be changed when a Custom Application is in the **Ready** state as it can be installed and used while in this state. You can change the list of OAuth Scopes assigned to the Custom Application permissions only in the **Draft** state when [configuring the Custom Application in the Merchant Center](https://docs.commercetools.com/merchant-center/managing-custom-applications#configuring-custom-applications).

To change the OAuth Scopes:

1. [Move the Custom Application to the **Draft** state](https://docs.commercetools.com/merchant-center/managing-custom-applications#moving-the-custom-applications-to-the-draft-state).
2. Update the list of OAuth Scopes.
3. Change the state to **Ready**.
4. [Install the Custom Application](https://docs.commercetools.com/merchant-center/managing-custom-applications#installing-a-custom-application) again.

<Info>

When a Custom Application state is changed from **Ready** to **Draft**, it is uninstalled from all Organizations and Projects. Thus, when installing the Custom Application again, [Team permissions must be assigned](https://docs.commercetools.com/merchant-center/managing-custom-applications#assigning-team-permissions) again.

</Info>

## Project access is not automatically updated for newly created Projects on AWS

When a new Project is created in the Organization, the Project cannot be accessed despite the **Project access** setting being configured to **Install for all projects of this organization** for an installed Custom Application.
Expand Down
15 changes: 15 additions & 0 deletions website/src/releases/2023-07/permissions-updates.mdx
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
---
date: 2023-07-03
title: Improved permission management for Custom Applications
description: Permissions of installed Custom Applications can now be updated.
type: enhancement
topics:
- Merchant Center
- Configuration
---

You can now modify the permissions of your Custom Applications in both **Draft** and **Ready** states, a feature that was previously limited to the **Draft** state.

This enhancement allows you to make changes to permission, for example, adding new OAuth Scopes, managing permission groups, or removing unused scopes, all without uninstalling the application. With this update, all existing team permissions remain unaffected.

If you have questions or feedback, open a GitHub [discussion](https://github.com/commercetools/merchant-center-application-kit/discussions) or [issue](https://github.com/commercetools/merchant-center-application-kit/issues).

1 comment on commit a8c1c11

@github-actions
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deploy preview for merchant-center-application-kit ready!

✅ Preview
https://merchant-center-application-e2yqd7ni4-commercetools.vercel.app

Built with commit a8c1c11.
This pull request is being automatically deployed with vercel-action

Please sign in to comment.