Limiting user roles to a content type

Feature Idea (one per thread):
The ability to give users access to only subset of content types. For example, an editor can manage blog content but not global content types or other content from other disciplines.

Issue that it solves:
Allows for a more granular control over permissions and volatility of content. Users will only have access to what is relevant to them and remove risk of accidentally changing content/controls.

Screenshot or video of the issue (if applicable):

1 Like

Hello, thanks a lot for joining the Community and for the feedback, it's always very much appreciated!

What you're suggested in something we've thought about in the past. We've slowly started developing new features that allow users to have more control in the way repo users interact with the Custom types and documents. Today, the best way you can control this is by having user roles setup in your repo. But this covers a different use case.

Granular user roles, that would allow users to adapt the user roles to Custom types, or even fields. Isn't something we're planning on doing in the near future. But I'll add this thread as an open feature request so we can be aware of it.


Thanks Paulina. Is there a separate feature thread I can follow for the new user features with custom types & documents?

Hello, your request is the only similar thread we have linked to this specific feature request.

This is how we manage them in general. If we ever actually develop the feature we inform everyone in the same thread, and whenever a feature request thread is automatically closed, other people can share their support for the idea by liking the original post.

Although please note that it isn't likely that we develop this feature in the near future.

This is being tracked as an open feature request.

If you have another use-case for this feature, you can 'Flag' this topic to reopen. Please use the :heart: button to show your support for the feature and check out our Feature Request Guidelines.