From dcdfed2547b07984c4f445363b79b72700109cfd Mon Sep 17 00:00:00 2001 From: Max Strivens <74908625+mstrivens@users.noreply.github.com> Date: Wed, 23 Jul 2025 15:03:30 +0100 Subject: [PATCH] updated go1 and brainier docs --- connection-guides/lms/brainier.mdx | 7 +++++++ connection-guides/lms/go1.mdx | 10 ++++++++++ 2 files changed, 17 insertions(+) diff --git a/connection-guides/lms/brainier.mdx b/connection-guides/lms/brainier.mdx index 158fd3a6..dee21962 100644 --- a/connection-guides/lms/brainier.mdx +++ b/connection-guides/lms/brainier.mdx @@ -98,6 +98,13 @@ Click **Test Connection** to verify that the credentials are correct. +## Content Visibility + +In order for a user to be able to view content either on the UI or in the API, they need to be assigned to the content. This can be done directly or by bring +part of a group which has access. + +The suggested approach is to ensure content is correctly assigned to the users/groups that will have visibility and will need access, otherwise they may be refused access to the content. + ## Troubleshooting If you encounter issues during the integration process, check the following: diff --git a/connection-guides/lms/go1.mdx b/connection-guides/lms/go1.mdx index 2b7b2849..38eb5566 100644 --- a/connection-guides/lms/go1.mdx +++ b/connection-guides/lms/go1.mdx @@ -83,3 +83,13 @@ description: "If you've been directed to StackOne to integrate with GO1, the fol + + ## Content Visibility (Pulling Content from Go1) + + In order to give you control over managing what content will be available to your users you can curate the content via Go1Admin. + + This is a centralised way to manage which content will be made available to your users in the third party LMS/LXP. + + [GO1 Admin](https://developers.go1.com/products/go1-admin/) + +