Best way to limit a user in creating Content in a workspace in ContentHub
Since the latest releases there was an update to limit the page types which a user could create in a channel or even in a specific path.
We have currently the issue, that we have content elements in ContentHub, which holds texts for a static widget which can be selected on a page. These elements are created by the admin, and it should not be possible for a user to create them, because there is only one for each static widget. Is there a way to limit the available content types in ContentHub or to limit them in a specific workspace or is there a plan to include this, like with the pages?
What we would need is to not show these content types if a user wants to create a new element and only the admin is able to create them.
Environment
- Xperience by Kentico version: 30.3.1
- .NET version: 9
- Execution environment: Private cloud (Azure)
Answers
These elements are created by the admin, and it should not be possible for a user to create them, because there is only one for each static widget.
Workspaces don't enable that kind of control today. The Content hub leans more towards supporting content editing and visibility control more than content creation control.
Is there a way to limit the available content types in Content Hub
No, not today. This also applies to web page content types in website channels. You cannot directly restrict which types of web page content types a marketer can use through configuration.
You can do this in an indirect way by limiting which web page content types can be used with allowed web page content types and scopes, and then combine this with web site channel page tree permissions for marketers.
If you need the ability to limit specific content creation to administrators only then request this on our roadmap and share your use-case.
Workaround
As an alternative solution, developers can model this "restricted" content as a custom object type and design the administration UI for managing it to only allow 1 instance of this data. This data can then link to content items in the Content hub and also be linked to in Page Builder component properties.
Our guide on creating a custom settings application uses this approach and the Kentico Community Portal does this for website channel settings.
In this screenshot, the administrator edits a custom object type but each of the fields is linking to a content item managed in the Content hub. There can be only 1 instance of this "settings", but there can be multiple instances of the linked content items. This is ok because they can't be used without selecting them here in this settings UI and permissions are restricted for this custom application.
To response this discussion, you have to login first.