Disabled apps

After an app has been released, it may need to be disabled in response to some sort of issue, such as a security incident. When this happens, the app will be hidden from both new and existing users.

The details of how apps are disabled (and re-enabled) depend on whether it's a public app or a team app.

Public apps can be disabled by members of Canva's app review team.

There are many reasons why an app may be disabled, and it's not practical to describe every possible reason, but these are some examples of possible reasons:

• The app has a security issue.
• The app relies on a backend that is not responding to requests.
• The app has a significant bug.

1. The app is hidden from new and existing users.
2. The owner of the app receives an email that explains why the app was disabled.
3. A ticket is created in Jira Service Desk (JSD) for communication between Canva and the owner of the app.

The steps for re-enabling a public app depend on the type of change that needs to be made to the app.

If a change to the app's frontend source code or Developer Portal configuration is required:

1. Create a new version of the app.
2. Make the required change by uploading a new bundle and/or updating the app's configuration.
3. Submit the new version of the app for review.

If Canva approves the new version, it will replace the disabled version.

Sometimes, a change to the app's frontend source code or Developer Portal configuration is not required. For example, it might be that only the app's backend needs to be updated.

In this scenario:

1. Make the required change without creating a new version of the app.
2. Use the JSD ticket to inform Canva that the change has been made.

After Canva has confirmed that the change has been made, the app will be enabled.

Team apps can be disabled by the owner or an administrator of a team.

The reasons a team app may be disabled depend entirely on the team. Canva is not involved in the disabling or enabling of team apps, so any standards will be set within the team itself.

1. The app is hidden from new and existing users.
2. The owner of the app receives an email that explains why the app was disabled.

The steps for re-enabling a team app depend on the type of change that needs to be made to the app.

If a change to the app's frontend source code or Developer Portal configuration is required:

1. Create a new version of the app.
2. Make the required change by uploading a new bundle and/or updating the app's configuration.
3. Submit the new version of the app for review.

If the owner or an administrator of the team approves the new version, it will replace the disabled version.

Sometimes, a change to the app's frontend source code or Developer Portal configuration is not required. For example, it might be that only the app's backend needs to be updated.

In this scenario:

1. Make the required change without creating a new version of the app.
2. Use the JSD ticket to inform Canva that the change has been made.

After the owner or an administrator of the team has confirmed that the change has been made, they can re-enable the app via the Account settings > Team apps page.