cs-icon.svg

Organization Stacks

Under the Stacks tab of the Organization Settings page, you will see the list of stacks created under the Organization.

To access the STACKS page, you need to perform the following steps:

  1. Log in to your Contentstack account.
  2. Select the Organization from the dropdown on the header, and click on the “Org Admin” icon on the left navigation panel.
  3. Click on the STACKS tab.

Here, you will find the following basic information related to the stacks:

  • NAME: Name of the stack
  • OWNER: Name and email address of the Stack owner
  • USERS: Number of users added in the stack
  • CREATED AT: Date and time of stack creation

Organization_stack_1_highlighted.png

From this page, you can only Delete a stack.

Delete a Stack

Note: Only the Organization Owner or Stack creator/owner has the right to delete a stack.

Let us look in detail the steps that need to be performed by the respective roles.

Organization Owner

To delete a stack through the Settings page, perform the following steps:

  1. Log in to your Contentstack account.
  2. Select the Organization from the dropdown on the header, and click on the “Settings” icon on the left navigation panel.
  3. Select the STACKS tab, and click on the “Delete” icon that appears on the extreme right side.image.png
  4. Confirm the Delete action.

Your stack will now be permanently deleted.

Stack Creator/Owner

There's an alternative method of deleting stacks through the Stack Settings page. This method can be performed by the Stack Creator/Owner. To delete a stack, perform the following steps:

  1. Log in to your Contentstack account and go to the stack that you want to delete.
  2. Click the “Settings” icon on the left navigation panel and select Stack.
  3. On the Stack Settings page, click on Delete Stack button.image.png
  4. Confirm the Delete action to delete your stack permanently.

Warning: Deletion of the stack will result in the permanent deletion of all the content stored within that stack.

API Reference

You can refer to the following API calls:

Was this article helpful?
^