# Dev env missing collection permissions **URL:** \ **Category:** Help me!\ **Created:** [May 25, 2021, 6:07pm UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556 "2021-05-25T18:07:26Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![username1](https://avatars.discourse-cdn.com/v4/letter/u/ee59a6/32.png) [@username1](https://community.forestadmin.com/u/username1)\ **Post date:** [May 25, 2021, 6:07pm UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/1 "2021-05-25T18:07:26Z")
We’re trying to setup a production environment on localhost development environment but am encountering errors due to table permissions. When comparing dev to prod we can see that dev has most of the table permissions missing, even though it’s the same user and database. For most tables on dev, these permissions are totally missing, sometimes only one option shows but is disabled, and for some they are all there as expected. On prod they are all visible and enabled. Please help. Thanks in advance. ## Expected behavior We are expecting to be able to access all the same collection permissions as in production. ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/4/4f88abbf82d077264ffb368782f22428b480d6b1.jpeg) ## Actual behavior The collection permissions are missing from tables. ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/1/1942377a84311e32c56351d7e149be0f0f43b37a.jpeg) ## Failure Logs Here’s the corresponding log error: ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/9/9d088d58abf7d6329674e617d95397619daeea23.jpeg) ## Context - Express Version: 4.16.4 - Sequelize Version: 4.8.0 - Database Dialect: PostgreSQL - Database Version: 9.6 ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [May 26, 2021, 7:57am UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/2 "2021-05-26T07:57:28Z")
Hi and welcome in our community 🍾 ! Could you please share the name of your project ? You are experiencing this issue on the same project right ? Because your production is clearly using our old permissions system while your development seems to be using our new permissions system “Roles”. Which means that the permissions are moved into your project settings under the tab roles instead of inside the collection settings. ---
**Author:** ![username1](https://avatars.discourse-cdn.com/v4/letter/u/ee59a6/32.png) [@username1](https://community.forestadmin.com/u/username1)\ **Post date:** [May 26, 2021, 2:57pm UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/3 "2021-05-26T14:57:41Z")
Hi Vince, thanks very much for your assistence. I’m unable to disclose the project name, though yes, we are experiencing this on the same project. When viewing the Settings \> Role \> we are unable to see any options, says it needs to be deployed to production first which wouldn’t be practical. We need to be able to work on dev first before deploy. ![Captura de Pantalla 2021-05-26 a la(s) 9.42.54](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/8/85401c7c868f9ae96b940e3f79580b44e47d4e7e.png) Shouldn’t all collections have permissions available by default? Even on dev. We are unable to test some smart actions which require full colllection permissions access. Please help. Thanks. ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [May 27, 2021, 8:39am UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/4 "2021-05-27T08:39:17Z")
Hey @username1 you can of course send it in private message 😉 Is it really the same project cause it seems you have no remote at all 🤔 ? It would really help me if you could send me your project name in private 🙏 ---
**Author:** ![username1](https://avatars.discourse-cdn.com/v4/letter/u/ee59a6/32.png) [@username1](https://community.forestadmin.com/u/username1)\ **Post date:** [May 27, 2021, 3:57pm UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/5 "2021-05-27T15:57:52Z")
Ah sorry, it’s not the same Forest Admin project, we are needing to replicate that setup on a new project from scratch. What I meant by same project is the codebase and DB are exactly the same. We just need to be able to get this working on our local dev env first. It’s not practical to have to deploy to remote staging env to be able to see the collections permissions options. We need these working on local machines so we can develop locally. Not to mention avoid unecessary costs in remote hosting while developing. Is there any way we can have all collections permissions enabled by default on dev? What benefit is there to only allowing these permissions on remote and not local dev? Thanks. ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [May 28, 2021, 9:15am UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/6 "2021-05-28T09:15:41Z")
What I meant everything should be allowed on your new project on development environment. That’s why I was asking for your project name so I can find out what is going wrong. Which version of forest-express-sequelize are you on ? ---
**Author:** ![username1](https://avatars.discourse-cdn.com/v4/letter/u/ee59a6/32.png) [@username1](https://community.forestadmin.com/u/username1)\ **Post date:** [May 28, 2021, 2:39pm UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/7 "2021-05-28T14:39:40Z")
Thanks Vince, sequelize version is 4.8.0 ## Context - Express Version: 4.16.4 - Sequelize Version: 4.8.0 - Database Dialect: PostgreSQL - Database Version: 9.6 ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [May 28, 2021, 3:20pm UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/8 "2021-05-28T15:20:29Z")
I mean your `forest-express-sequelize` version not `Sequelize` 😉 ---
**Author:** ![username1](https://avatars.discourse-cdn.com/v4/letter/u/ee59a6/32.png) [@username1](https://community.forestadmin.com/u/username1)\ **Post date:** [May 28, 2021, 4:28pm UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/9 "2021-05-28T16:28:01Z")
Sorry, forest-express-sequelize is v3.1.1 ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [May 31, 2021, 8:07am UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/10 "2021-05-31T08:07:04Z")
No worries. This is a really old version, could you try to upgrade to the latest version by following our upgrade guides ? This should fix your issue 😉 - [Upgrade to v4](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v4) - [Upgrade to v5](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v5) - [Upgrade to v6](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v6) - [Upgrade to v7](https://docs.forestadmin.com/documentation/how-tos/maintain/upgrade-notes-sql-mongodb/upgrade-to-v7) ---
**Author:** ![username1](https://avatars.discourse-cdn.com/v4/letter/u/ee59a6/32.png) [@username1](https://community.forestadmin.com/u/username1)\ **Post date:** [June 1, 2021, 4:21pm UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/11 "2021-06-01T16:21:32Z")
Thanks, though this wouldn’t be possible without a ton of work. Is there anyway to resolve this on v3? How is it possible that the exact same DB and codebase using v3 are still working fine in production (ever since deployment 2 years ago) but now the same doesn’t work when redeployed on a new Forest project? Wouldn’t our production also experience this same issue? Any additional info would be much appreciated. Thanks again. ---
**Author:** ![anon62739609](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@anon62739609](https://community.forestadmin.com/u/anon62739609)\ **Post date:** [June 2, 2021, 7:14am UTC](https://community.forestadmin.com/t/dev-env-missing-collection-permissions/2556/12 "2021-06-02T07:14:32Z")
Because we refuse old versions when creating new projects basically. That’s why you have this issue. If you stay on your project and create new environments everything will work fine. But new projects have to be up to date