For Filtered to work with a full set of features it needs Degreed to allow it certain permissions that affect content, pathways and user information.
Getting setup
1. From Admin > Settings > API Keys choose the Edit credentials for the associated Content Intelligence key.
Please generate Organization API keys, do not select a provider from the drop down box. If the keys will not generate, please contact your CSM or request a Technical Project Ticket to complete your request
2. Use the checkboxes to enable features
3. Generate your API key in the Degreed platform and then send over the following details to your Filtered Customer Success Manager who will get it processed in Filtered for you:
- client ID
- client secret
- host (either degreed.com, eu.degreed.com, ca.degreed.com)
4. Once these are setup in Degreed, your CSM will notify you and your integration will be setup
Definitions
Scope | Required | Description | Limitation |
content:read | Yes | Allows Filtered to pull in Content from Degreed | |
content:write | Yes | Allows Filtered to push tags associations to Content to Degreed | |
skills:read | Yes | Allows Filtered to verify Skill names entered against those in Degreed | |
pathways:read | Yes | Allows Filtered to pull in Pathways from Degreed | Without this Filtered will not be able to have any information on the pathways that are live in a Degreed instance.🚫 |
pathways:write | Yes | Allows Filtered to create and update Pathways in Degreed | Without this Filtered will not be able to push pathways into Degreed. |
users:read | Yes | Allows Filtered to assign a Degreed user as Collaborator for a newly created pathway | Without this Filtered will not be able to assign the creator of a pathway as a collaborator in Degreed. |
providers:read | Yes* | Allows Filtered to include Public Content (formerly known as One-Click Providers), if you have any enabled, within the platform for use in Pathways. | Without this Filtered will not be able to include assets from your Public Content libraries for use in pathways. |
*If you would like to include assets from the Public Content libraries you have enabled within Degreed in any pathways you curate
One example of an issue is that if a pathway is created in Filtered, pushed to Degreed and then deleted from Degreed, then Filtered will not know that the said pathway is no longer valid and will try to update a non-existing resource resulting in an error