Content Integration Security Levels

April 3, 2017 Stuart Grossman

One of the concerns Xyleme customers have is how to secure content once it’s been published to CDS.  We’ve found that many customers want flexibility and require a number of different ways to distribute their content to different audiences.  We have a variety of options for distributing and securing content.  

The table below looks at each in order from least secure to most secure.

Level

Description

Typical Application

1

Public link

A URL link accessible to anyone with the link.  Does not require an account on CDS to access the content.

Information you want to make publicly available, often via a website.

One of my favorite uses of this option is for those that sell their content.  The public link together with Studio’s ability to easily link content into new assemblies allows them to create mini samples of their content and make those available through their website, in email, on social media.

Anyone that has that link can just click to access that content, so it's a great way to try before you buy without having to manage accounts.

2

Public link with whitelisted domains

A URL link only accessible from  specific web site(s)

You may have users both internal and external to your organization and you don’t have a central database of users that could be used to set up Single Sign-On. You may have a partner portal or other website with some access control that can be leveraged via the whitelist option.

You can put public links on that web site (could be a hidden page on your public website perhaps) and when a user click those links from that website they are allowed to access that content.  If they tried to access that link by any other method (a link in an email, bookmarking, copy and paste in a browser) they would not be able to access that content.

Note: Once the whitelisting option is enabled on your instance that is the only way public links will work.   So you can’t make some links only accessible via a whitelisted site and also send public links out in emails.

This only applies to Public Links, so Preview Links, Thin Packages, and Private links are still available to users with accounts on the system.

3

Private Link

Private Thin Package

Users must have an account on the system and permission, but do not need specific access to the folder where the content is stored.

This is used for employee access where you don’t want to manage permissions to individual folders/documents. 

You could store content in folders that no one has permission to access through the CDS Portal but if they have the Private link they will have access via that link.

Note: A number of customers have been concerned that if they send a Preview Link to a user (see level 4) they would be able to access additional content by going back to the root of the URL (training.bravais.com).   This method of giving access via a Private link would prevent them from begin able to access other content from the portal. 

Additional we’ve recently added the ability to disable portal access altogether for groups of users. 

4

Preview Link

Launch Link

Thin Package

A URL link that requires a user to have an account on the system AND have permission to access the folder where the content is stored

This is typically used for employee access to specific content often through Single Sign-on.

 

Have a question? Come to open Q&A or ask your account manager.

About the Author

Stuart  Grossman

Stuart Grossman is the Vice President of Education and Training for Xyleme. Stuart has over 20 years of experience in design, development and implementation of training systems and performance support tools and has been a contributing member to Xyleme's success since 2007.

More Content by Stuart Grossman

No Previous Articles

Next Article
Saving 30% on translation is always a good answer
Saving 30% on translation is always a good answer

×

Get free learning content best practices!

First Name
Last Name
Company Name
Job Role- optional
!
Read the blog!
Error - something went wrong!