Is it a correct behavior that developer can delete readonly project? | Community
Skip to main content
New Participant
July 19, 2023
Solved

Is it a correct behavior that developer can delete readonly project?

  • July 19, 2023
  • 2 replies
  • 983 views

I created a project on developer console and added Adobe Stock API. When I added this API, I selected a product profile.

 

When the developer who belongs to another product profile accessed this project, the status was readonly. But he/she was able to delete this project. Is it a bug or correct behavior?

 

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by rawvarun

While most projects can be deleted, sometimes a project is related to an application you have published and, therefore, cannot be deleted.

  1. If a project contains an API submitted for approval (status: In Review or Approved), then the project cannot be deleted.
  2. If an App Builder project has been submitted for approval (status: Pending or Published), then that project cannot be deleted. However, you can always revoke a published app and delete the project.

2 replies

tmj
Employee
July 31, 2023

Hey @nasokikoide - this should now be fixed thanks for raising this! And, yes, a developer with read-only access to a project should not be able to delete it. 

New Participant
July 31, 2023

Thank you so much for modifying that!

rawvarun
rawvarunAccepted solution
New Participant
July 24, 2023

While most projects can be deleted, sometimes a project is related to an application you have published and, therefore, cannot be deleted.

  1. If a project contains an API submitted for approval (status: In Review or Approved), then the project cannot be deleted.
  2. If an App Builder project has been submitted for approval (status: Pending or Published), then that project cannot be deleted. However, you can always revoke a published app and delete the project.
New Participant
July 25, 2023

Thank you very much! Oh, it is not a bug... I accept that.