sections in the article
This article lists common questions asked about the Content Segmentation functionality in inRiver.
Q: What is Content Segmentation?
A: Content Segmentation is a functionality that allows you to divide your inRiver content into different parts, segments, and control which users that have access to that content. For example, you might want to make sure that groups of employees within a company are only able to access, view, and/or edit certain products. Read more in this article.
Q: Can a user have access to multiple segments?
A: Yes, a user can have access to multiple segments. They can also be assigned to different roles within each segment as needed. Read more in this article.
Q: What are the limitations of Content Segmentation?
A: Content Segmentation only applies to your entities (such as your Products, Items, Resources etc). An entity can only be assigned to one segment.
Q: What happens when Content Segmentation is activated in my environment?
A: Nothing, except that you now have access to the Segments application in Control Center. Once Content Segmentation is activated, you can start creating segments, assign users to roles in the segments, and move entities into the segments. To begin with, all entities are part of a default segment. ('Default' is a temporary name that you can change if you want to.) Read more in this article.
Q: How to divide your content into different segments?
A: Read more in this article.
Q: How does Content Segmentation work with channels and channel nodes?
A: Channels and Channel Nodes are also entities and will belong to a segment. It is possible to display products from different segments in a channel, to accomplish this you need to add products manually or through the API. The rules and queries will only add products from the same segment that the channel node has.
Q: If I change the segment on a Product, what will happen to related Items and Resources?
A: If you move a product from one segment to another, nothing will happen. Related items and resources will not automatically change segment. If you want to set up and apply rules related to moving products and related items and/or products between segments, use an Entity Listener extension.
Q: How does Content Segmentation work when using work areas?
A: Work areas don't belong to any segments, only entities belong to segments. However, Content Segmentation controls which content is displayed in a work area. You can also use Segment as a parameter in a work area query. The shared work areas that you create will be visible to all users, regardless of which segment(s) they have access to, but the visible content within the work area will differ depending on what segment(s) the user has access to.
Q: Does Content Segmentation work with inRiver Print?
A: Yes. Which publications, sections, and products you can access in inRiver is based on the role and segment available for your user.
Q: Does Content Segmentation work with the Planner?
A: Yes. All content you see will be dependent on the segments you have access to as a user. The list of shared views will however be seen by all users.
Q: Does Content Segmentation work with Content Store?
A: Yes. However, everyone that has access to the Content Store back end will have access to all the Content Store set-ups. All content in the channel used by the Content Store will be available to all Content Store Portal users.
Q: Does Content Segmentation work with Syndicate?
A: Yes. However, it doesn't allow you to control which segments can be seen by different users. In the future, this will be managed with new Syndicate-related permissions. When Syndicate accesses a work area to get the content that is to be syndicated, it functions as a system user that has access to all segments. If you want to restrict access to only one segment, add Segment as a parameter to the work area query.
Q: Does Content Segmentation work with Supplier Onboarding and Contribute?
A: This functionality is currently out of scope and has not been fully explored. There is no way of selecting which segment the content that is being approved will end up in. The content will probably be created in the first segment that the approver belongs to, but there could be errors.
Q: Does Content Segmentation work with the Rich Client?
A: No. The Rich Client is out of scope.
Q: Can a segment be deleted?
A: Yes, if it's not in use by either a user or entity.
Q: Can I only have some specific entities segmented?
A: No, as soon as Content Segmentation is activated, then it applies for all entity types (Product, Item, Task, Channel, Channel Nodes or any other custom entity). All entities will be assigned to a Default segment at first. You can change the name of this segment and also create other custom segments.