Does anyone have experience using Share Point as the default storage for Articulate Projects? My IT department is going away from the Shared Drive (default) and pushing all files to SharePoint. I would love to hear if anyone is doing this and what/if any impact they saw saving Articulate files to Share Point.
We are HUGE SharePoint - and now Teams - fans and have been using Sharepoint/Teams as the main development project management tool for many years...
In the early days (before Teams) we set up a SharePoint site for each client and then a new page for each project. By using Microsoft's industrial strength security we were able to allow each client secure access to share information on their own project pages. Each site had
An asset library
A source file library
An outline project development plan
An issue tracking log etc. etc
all setup in seconds from a project site template.😊
This saved us an enormous amount of time - no searching through emails from our clients to locate the image they sent, or the comments they made via email - and yes, you can run a published web version of a Storyline course from a SharePoint library! - (although now we use Articulate Review because that is just awesome!). Strict version control built in and the absolute heaven associated with a single source library for everything - with automatic back up! Transformational!! NO searching No lost files No confusion over versions. No "I didn't get your email!"
Is there anything else we would like - yes, you can't edit the Storyline source directly in the cloud - you have to have some discipline if two developers are working on the same course!
When Teams emerged we were a bit slow to transfer because of what we had set up - but then as soon as Microsoft allowed for "external" users to join a Team we realised we could also track meetings and ALL emails in the same location as the above. (the Team has an email address which we just put in the cc block!!)
What's not to like!! Applause and full credit to your IT department!! When I rule the world - everyone will have a Teams account - mandatory!! The world would be a better place😁
1 Reply
We are HUGE SharePoint - and now Teams - fans and have been using Sharepoint/Teams as the main development project management tool for many years...
In the early days (before Teams) we set up a SharePoint site for each client and then a new page for each project. By using Microsoft's industrial strength security we were able to allow each client secure access to share information on their own project pages. Each site had
An asset library
A source file library
An outline project development plan
An issue tracking log etc. etc
all setup in seconds from a project site template.😊
This saved us an enormous amount of time - no searching through emails from our clients to locate the image they sent, or the comments they made via email - and yes, you can run a published web version of a Storyline course from a SharePoint library! - (although now we use Articulate Review because that is just awesome!). Strict version control built in and the absolute heaven associated with a single source library for everything - with automatic back up! Transformational!! NO searching No lost files No confusion over versions. No "I didn't get your email!"
Is there anything else we would like - yes, you can't edit the Storyline source directly in the cloud - you have to have some discipline if two developers are working on the same course!
When Teams emerged we were a bit slow to transfer because of what we had set up - but then as soon as Microsoft allowed for "external" users to join a Team we realised we could also track meetings and ALL emails in the same location as the above. (the Team has an email address which we just put in the cc block!!)
What's not to like!! Applause and full credit to your IT department!! When I rule the world - everyone will have a Teams account - mandatory!! The world would be a better place😁