Issues Connecting to Sharepoint from Workfront

[DeborahLeigh123]

Is there any materials out there talking about the Workfront to Sharepoint integration? I'm having a heck of a time getting my IT department to help me get this sucker connected and now I have to figure it out. I'm looking for ANYTHING on this. I've done everything the pages can teach me but it's still not right. 

It seems as though they are pointing people to a specific Sharepoint folder inside of Sharepoint instead of the root folder. Can anyone share information with me on this?

Thank You,

Deb

[KellieGardner]

Users have access to the same sites, collections, folders, subfolders, and files through the Workfront SharePoint integration as they have in their SharePoint account.

Are users able to see the breadcrumb trail on the SharePoint popup and navigate to the correct folder?

[KellieGardner]

a follow up question: is your sharepoint integration setup through the backen setup area or is this something they are each configuring on their own?

[DeborahLeigh123]

Hello Kellie! Thank you for responding. I'm going to give a little more context here to explain what's happening. There's actually two issues.

Issue #1:

1. I've inherited a Workfront Instance where my company has one instance shared by 5 different lines of business.
2. Four of the Five have files scattered all over Sharepoint in various folders. So they can't just point to 1 folder.
3. I need all five lines of business to see files they want to link into Workfront.
4. I've asked our IT department to do this, but they are struggling to understand how to set this up.
5. They've given only one folder to access and it has nothing to do with the other lines of business. 
6. I know this is a permissions issue.
7. We are using Sharepoint Graph API and I've turned off the specific integration pointing to a specific folder.

Issue #2

1. One of the lines of business was acquired by my company before I started. 
   1. They had their own Sharepoint instance in another location.
   2. They have moved their instance into the corporate Sharepoint.
   3. They have one singular folder where they organize all files on Sharepoint for Workfront.
      1. However, Some of my users cannot see any net new Sharepoint files, only the files from the first day they migrated the instance over on 10/23/23..
         1. It doesn't matter what we do they cannot see any net new files in Workfront when trying to link them. Only 10/23/23 (When the instance migrated over.)

Any suggestions? I hope that helped explain what I'm up against. Let me know if you have any further questions.

[KellieGardner · Accepted solution]

This helps, thank you for all the details

The only thing I can think is that on the permissions side of SharePoint, you need to make sure the users have permission to the folders inside of SharePoint itself. Since the user is essentially logging into their Microsoft account when linking to a document, they must have access to it in SharePoint. Outside of Workfront, are the users able to see the folders you want them to use inside of Workfront? 

To see a site collection in Workfront, the following conditions must be met:

• The user must have view access to the site collection in SharePoint.
• To verify this in SharePoint, check the site collection’s permissions in SharePoint.

For your second scenario where they aren't able to see anything created after the migration: 

• Is the person who created the folder still an active user? If the user who linked a SharePoint folder can no longer authenticate, Workfront can no longer access the contents of the folder. This can happen if the user who originally linked the folder leaves the company. To ensure continued access, a user with access to the folder must re-link the folder.
• Is it possible any of these were created using the legacy SharePoint integration? If so, you do have to reconfigure the access to legacy SharePoint for continued access in Workfront. 

After verifying the SharePoint permissions are all there, I would suggest reaching out to Workfront Support to see if they can help you by digging into your system a little more. They will be better able to see what's happening on the Workfront side of things. 

Doing some digging around the community it seems like there have been some issues that may be tied to how large the SharePoint Instance is:

https://experienceleaguecommunities.adobe.com/t5/workfront-questions/sharepoint-integration-using-gr...

https://experienceleaguecommunities.adobe.com/t5/workfront-questions/new-sharepoint-document-link/m-...

[DeborahLeigh123]

I have noticed that I can see almost every single folder inside of our Sharepoint instance. I would think the mapping would only show me folders I have access to, no? Is there a way to cull down what they are allowed to see? 

Incredibly helpful Kellie! Thank you so much! We will get hopping on this. If I have any follow-ups, I will return to comment. 

[KellieGardner]

I agree that it should only show you what you have access to. When I test in my instance with the integration, I can only see what I have access to and nothing more.

[DeborahLeigh123]

@KellieGardner , I have one more question:
Kellie's comment:

• Is it possible any of these were created using the legacy SharePoint integration? If so, you do have to reconfigure the access to legacy SharePoint for continued access in Workfront. 

Can you explain to me what this means? 

[KellieGardner]

I came across this when reading through the documentation. To continue accessing documents, you have to continue to maintain anything connected to Workfront through the legacy SharePoint Integration.

"To ensure that your users have continued access to documents linked to Workfront through the legacy SharePoint integration, you must reconfigure access to the legacy SharePoint integration and keep the SharePoint Client Secret up to date."

https://experienceleague.adobe.com/en/docs/workfront/using/administration-and-setup/configure-integr...