Board not visible for team/circle members

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Describe the bug
When we share a board in deck with a team the users in that team can't see the board in their deck app.
When i check deck_board_acl table the entry for the team is there with type 7 which should be good.
When i try to open the board directly from it's id https://nc.domain.com/apps/deck/board/69 it gives me a board not found and a 403 forbidden error in the dev console.

To Reproduce
Steps to reproduce the behavior:

1. Create a board.
2. Share with a team.
3. Check visibility in deck as a user of that team.
4. Try to load the board directly.

Expected behavior
The board should be visibile to any users of a team with the permissions granted after sharing a board with the team.

Screenshots
If applicable, add screenshots to help explain your problem.

Client details:

• OS: Windows 11
• Browser: Any but tested edge and chrome
• Version mutiple
• Device: Desktop

Server details

Operating system:
Ubuntu 24.04

Web server:
Apache

Database:
Mysql 8.0.45

PHP version:
8.3.6

Nextcloud version: (see Nextcloud admin page)
33.0.3

Where did you install Nextcloud from:
Nextcloud repo

Login as admin user into your Nextcloud and access
http://example.com/index.php/settings/integrity/failed
paste the results here.

No errors have been found.

Nextcloud configuration:
Deck - Version 1.17.1

**Are you using an external user-backend, if yes which one:** LDAP/ActiveDirectory/Webdav/...
Microsoft 365 

</details>

<details>
<summary>Logs</summary>

#### Nextcloud log (data/nextcloud.log)
No issue logged

#### Browser log

Insert your browser log here, this could for example include:

Reproduce the problem by sharing a Deck board with a team, checking visibility for a team member, and opening the board directly at the reported URL. Inspect the deck_board_acl entry and the browser's 403 response; done means team members can see and open the board with the granted permissions.