Retrieve content with Optimizely Graph

Restricted Content with Optimizely Graph

Restricted content refers to content that is not visible to users. To designate content as restricted, you need to remove the Read permission for the Everyone group.

Indexing and Accessing Restricted Content

Restricted content is indexed into Optimizely Graph. However, it is not accessible when querying data from Optimizely Graph using single key authentication. To access restricted content, you must utilize Basic or HMAC authentication.

Restricted Content in Content Areas

When a content area is indexed, any referenced content is "inlined" into the area. This lets you query the content area as if the referenced content is part of it. Optimizely Graph does not evaluate user permissions at query time to verify access to content within a content area; this is determined during indexing.

Criteria for Content appearance in Content Areas

For content to be included in a content area, it must meet at least one of the following criteria:

• The content is public (i.e., it has Read permission for the Everyone group).
• The content is located in the For this Page folder.
• The content shares read permissions with its parent, and for nested content, permissions are checked against the top-level content.

Example of Restricted Content for Nested Content

A page has read access for the groups WebAdmins, Editors A, and Editors B. Inside that page, a block is placed in a content area. The block has read access only for the groups Editors A, Editors B, and Editors C.

When Optimizely Graph delivers content, it enforces access control based on each item’s permissions. Because the block does not grant read access to WebAdmins, it is excluded from the Graph response, even though the page is available to that group.

As a result, the block is not inlined into the content area and is not available to any user or integration that does not have explicit read access to the block.