Contentstack Management - Users Actions

View as Markdown
Last updated October 15, 2026

Contentstack, being an Enterprise Content Management (ECM) system, accommodates numerous users with different permissions collaborating together. In Contentstack, all the member accounts of a stack are referred to as users. By using the Contentstack Management Users action, you can fetch user-related details, such as name, email, and so on.

Click to enlarge

Let’s look at the action in detail.

Get User Information

This action gets a user's first name, last name, and email address based on the user ID. Using optional fields, you can also include the roles assigned to the user and the permissions those roles carry.

  1. Under Choose an Action tab, select the Get User Information action.
  2. On the Get User Information Configure Action page, enter the details given below:
    1. Click + Add New Account button to connect your Contentstack account as shown in the Connect your Contentstack Account to Automate step.
    2. Provide a User ID to fetch the user details.

      Note To fetch the user ID, you need to configure an action and select the dropdown to fetch from the previous step, where user details can be fetched.

      Click to enlarge
    3. You can easily select multiple user IDs from the Suggested Data Elements drop-down. This will automatically retrieve all the user IDs generated in the previous steps, streamlining the process.
      Click to enlarge
    4. [Optional] Turn on the Show Optional Fields toggle to reveal additional options:
      1. Select the Include roles checkbox to return the roles assigned to the user. When you select Include roles, the Select Stack field becomes required. Select the stack whose roles you want to return. The action then returns each role assigned to the user in that stack (for example, Content Manager, Admin, or Developer) along with its description.
      2. Select the Include permissions checkbox to return each role's resolved permissions, across content types, environments, and locales. Because permissions are attached to roles rather than directly to the user, Include permissions requires Include roles to be selected (and therefore a stack).

        Note The Include permissions option returns a large amount of data. Use it only when you need this level of detail.

        Click to enlarge
  3. Once done, click Proceed.
  4. Click Test Action to test the configured action.
  5. The output will be shown as follows. Click the Save and Exit button.
    Click to enlarge