# Action appears on development and production but not staging

**URL:** <https://community.forestadmin.com/t/action-appears-on-development-and-production-but-not-staging/4844>\
**Category:** Help me!\
**Created:** [June 19, 2022, 9:27am UTC](https://community.forestadmin.com/t/action-appears-on-development-and-production-but-not-staging/4844 "2022-06-19T09:27:27Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yonatan\_Naor](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/yonatan_naor/32/4148_2.png) [@Yonatan\_Naor](https://community.forestadmin.com/u/Yonatan_Naor)\
**Post date:** [June 19, 2022, 9:27am UTC](https://community.forestadmin.com/t/action-appears-on-development-and-production-but-not-staging/4844/1 "2022-06-19T09:27:27Z")

</div>

## Feature(s) impacted

Custom actions

## Observed behavior

Action does not appear on the staging environment although it appears on the production and development environment

## Expected behavior

Action should appear in all environments

## Failure Logs

## Context

- Project name: GSL\_Admin
- Team name: Developers
- Environment name: Staging
- Agent type & version: “forest-express-mongoose”: “^8.6.3”
- Recent changes made on your end if any: none

---

<div class="post-metadata">

**Author:** ![anon39940173](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@anon39940173](https://community.forestadmin.com/u/anon39940173)\
**Post date:** [June 20, 2022, 12:18pm UTC](https://community.forestadmin.com/t/action-appears-on-development-and-production-but-not-staging/4844/2 "2022-06-20T12:18:20Z")

</div>

Hello!  
Welcome to our community

For a smart actions to be visible in the list-view multiple conditions must be satisfied.  
Can you check them?

- The smart action must be implemented in the agent (check in the `.forestadmin-schema.json` file if you can find it)
- The smart action must be marked as visible in the collection settings (see screenshot)
- When not in development, the smart action must be marked as triggerable in the role that the user has (see screenshot)

Collection settings:

> **[Create and manage Smart Actions](https://docs.forestadmin.com/documentation/reference-guide/actions/create-and-manage-smart-actions#creating-a-smart-action)**

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/e/edbf91e48da6746f1034edb3b5d425796492aa69.png)

Roles (this screenshot if for projects with approval workflow, you may not have all columns):

> **[Manage roles and permission levels](https://docs.forestadmin.com/user-guide/project-settings/teams-and-users/manage-roles)**

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/a/af02fd44e26be9b7e4963de76d2dae98dab250fc.png)