System Information
Hey guys,
did anyone find a way (in v4) to restrict a users (user-permission plugin) access to only related collection type entries using graphQL? I am trying to update a collection entry that is connected to the authenticated user. By default, the authenticated user could theoretically update every entry in this collection - but I want him to be limited to only that entry, where he is related to.
I already find out a way to let the authenticated user query only the related entries via this solution
opened 08:45PM - 24 Dec 21 UTC
issue: bug
severity: medium
status: confirmed
source: plugin:graphql
## Feature request
### Please describe your feature request
- [ ] **I have… created my request on the Product Board before I submitted this issue**
- [x] **I have looked at all the other requests on the Product Board before I submitted this issue**
### Summary
I would like to add some extra fields in user like `firstName` and `lastName` but adding them using Content-Type Builder doesn't make them available in GraphQL API
### Steps to reproduce the behavior
1. Using the Content-Type Build, add a Text field in User
2. Go on http://localhost:1337/graphql and check GraphQL documentation
3. The added text field isn't exposed
### Screenshots
`firstName` and `lastName` text fields added in user using Content-Type Builder:
Added fields not available in GraphQL API:
### Why is it needed?
Since `user` is a central part for most authenticated API and adding extra fields or relations to `user` is a very common use case. For now, we have to manually write specific code to add extra fields (in addition to Content-Type Builder). Thanks @iicdii to remember me the way we do it in v3.
### Suggested solution(s)
The added text field should be exposed, both on query and mutation.
### Related issue(s)/PR(s)
None, since I have "transform" the current issue from "bug report" to "feature request" :wink:
Any help appreciated!