WHAT WE'RE UP TO
SEE WHAT THE SILVERTECH TEAM IS UP TO
SilverTech CTO Shares Insights on Xperience by Kentico's Workspaces Features
By: Derek Barka | 1/8/25
SilverTech works in a lot of regulated industries like financial services, public utilities, and government and website governance is frequently a hot topic. As a Kentico partner, we got notice of Xperience by Kentico’s (XbyK) latest features in the December release, and I was excited about how easy it can make content governance with Workspaces.
Workspaces serve as role-based views within your content management system, allowing you to tailor access and functionality for different users. You can create as many workspaces as you want and apply different roles and permissions to those workspaces. When users log into XbyK, they only see the workspaces and corresponding content their assigned role permits them to access.
In the case of a bank or credit union, for example, they have lots of subject matter experts that need access to website content but should only be accessing that specific content. For example, a Community Outreach Manager should only have access to community content, or the Small Business Product owner should only have access to Small Business Content.
Most web content management platforms do allow you to limit access to certain folders or even content types like Rates, or Branch Locations, but that can become a permission management nightmare and force content admins into creating complicated folder hierarchies in order to enforce permissions. Content should be organized in a logical and semantic manner that makes sense for the content’s purpose and not based on permissions.
Workspaces allow users to organize the content logically and then grant access to it by assigning it to a workspace. Now, all content can be organized logically and in the same manner, but content editors are only seeing the content that is in their workspace.
Kentico has also made it really easy to move content from one workspace to another. This is key because, unfortunately, permissions change or content governance plans are not finalized before development starts. This way, the developers can begin building out the site logically and governance can be applied as content is added to the system.
I will say that I was disappointed that a content item can only live in one workspace. I do see use cases where a content item may need to exist in multiple workspaces. However, that’s not a showstopper and our Kentico developers can certainly work around that by adding distinct roles to different workspaces. I also made sure to let the XbyK Team know so hopefully we’ll see that in a release soon – that’s the beauty of monthly release cycles!