# 403 on Production Environment for newly added users

**URL:** <https://community.forestadmin.com/t/403-on-production-environment-for-newly-added-users/7065>\
**Category:** Help me!\
**Created:** [February 21, 2024, 10:59am UTC](https://community.forestadmin.com/t/403-on-production-environment-for-newly-added-users/7065 "2024-02-21T10:59:14Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevin\_Baumgartner](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/kevin_baumgartner/32/4323_2.png) [@Kevin\_Baumgartner](https://community.forestadmin.com/u/Kevin_Baumgartner)\
**Post date:** [February 21, 2024, 10:59am UTC](https://community.forestadmin.com/t/403-on-production-environment-for-newly-added-users/7065/1 "2024-02-21T10:59:14Z")

</div>

Hello!

## Feature(s) impacted

I’m also getting a 403 error when accessing any tables on my environments similar to this ticket:

> [@403 Forbidden Error on Test env](https://community.forestadmin.com/t/403-forbidden-error-on-test-env/7063):
>
> [image] Feature(s) impacted I receive 403 errors on each model on TEST env (ADMIN role). But on Prod env all is working. Also other team members also receive 403 errors on creation (ADMIN role). Failure Logs ================================== 2024-02-20 13:56:51.199 at async cors (/app/node\_modules/@koa/cors/index.js:109:16) 2024-02-20 13:56:51.199 at async bodyParser (/app/node\_modules/koa-bodyparser/index.js:78:5) 2024-02-20 13:56:51.199 at async ErrorHandling.errorHandler (/app/…

This only occurs tho on users I just added to the project. The user I created the project with can open all tables even tho all users are in the same team and have the same roles (ADMIN)

## Observed behavior

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

User that can access the tables:

- Dev Deckweiss

Users that cannot access the tables and get the 403 errors:

- Kevin Baumgartner
- Elisabeth Klenner

## Context

- Project name: BTPCalc
- Team name: Deckweiss (Operations in ForestAdmin)
- Environment name: Live & Staging
- Agent (forest package) name & version: “forest-express-sequelize”: “^9.3.11”
- Database type: PostgreSQL
- Recent changes made on your end if any: -

---

<div class="post-metadata">

**Author:** ![morganperre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/morganperre/32/1296_2.png) [@morganperre](https://community.forestadmin.com/u/morganperre)\
**Post date:** [February 22, 2024, 9:23am UTC](https://community.forestadmin.com/t/403-on-production-environment-for-newly-added-users/7065/2 "2024-02-22T09:23:23Z")

</div>

Hello @Kevin_Baumgartner,

Thanks for your report and sorry for the inconvenience.

We fixed your project. 👌 It should work for them now. 🙏

Let us know if everything is clear on your side.

Kind regards,  
Morgan

---

<div class="post-metadata">

**Author:** ![Kevin\_Baumgartner](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/kevin_baumgartner/32/4323_2.png) [@Kevin\_Baumgartner](https://community.forestadmin.com/u/Kevin_Baumgartner)\
**Post date:** [February 22, 2024, 9:54am UTC](https://community.forestadmin.com/t/403-on-production-environment-for-newly-added-users/7065/3 "2024-02-22T09:54:48Z")

</div>

Thanks @morganperre for the quick fix, it seems to work now \<3

Do you know what the problem was?

---

<div class="post-metadata">

**Author:** ![morganperre](https://dub1.discourse-cdn.com/flex013/user_avatar/community.forestadmin.com/morganperre/32/1296_2.png) [@morganperre](https://community.forestadmin.com/u/morganperre)\
**Post date:** [February 22, 2024, 10:07am UTC](https://community.forestadmin.com/t/403-on-production-environment-for-newly-added-users/7065/4 "2024-02-22T10:07:08Z")

</div>

Hey @Kevin_Baumgartner,

> [@Kevin\_Baumgartner](#):
>
> Do you know what the problem was?

Some of your project data were corrupted. As an unfortunate consequence, it broke an internal role mechanism… We don’t know what causes the corrupted data at first and we will conduct an internal audit to avoid having the same issue with other clients…

Again, thanks for your patience and your report it helps us improve the platform for everyone. 🙏

Kind regards,  
Morgan