This feature is only available in the desktop editor.
This table shows which SAML attributes in a SAML assertion map to ScreenSteps user attributes.
When the following attributes are included in the AttributeStatement of the SAML assertion, the corresponding user attributes will be updated in ScreenSteps.
This article is for developers who want to allow users to sign in to their ScreenSteps site through a 3rd party application that the developer controls.
ScreenSteps for Salesforce Service Cloud is an add-on which is available on Enterprise accounts.
API Tokens can only be used with admin or contributor user accounts. Do not use API tokens in a situation where the resulting authorization string can be seen by the public.
The article will show you how to configure your site so that users either are required or aren't required to login before viewing your help articles.
Single Sign-on makes it easier for users to authenticate to ScreenSteps and improve adoption of ScreenSteps. Refer to What is Single Sign-on? if you are not familiar with what Single Sign-on is.
When configuring a Single Sign-on (SSO) endpoint in ScreenSteps, you will need to enter an Entity ID (sometimes called the "Issuer") into the 3rd party SSO provider.
Your Entity ID will match your Consumer URL, which can be found using the instructions in this article: How to Edit Single Sign-on Settings or Find your Consumer URL and Test URL
To begin installation of the ScreenSteps for Service Cloud Salesforce application please visit the App Exchange: