Fintura
Fintura logoSharePoint logo
Pulled in, read-only

Fintura SharePoint integration

See your client folders from SharePoint and OneDrive inside each client's Files tab, without moving or copying anything.

What is the Fintura SharePoint integration?

The Fintura SharePoint integration is a read-only view of your existing SharePoint and OneDrive folders, shown on the Files tab of whichever Fintura client each folder is mapped to. Fintura holds an index of what is there, the names, folder structure, sizes and modified dates, and fetches a file itself only when somebody opens or imports it.

One way is enforced at the permission level rather than by convention, so Fintura is not capable of writing to your drive even if somebody asked it to.

What syncs, and in which direction

Every row is what the SharePoint connection does today.

What syncs between Fintura and SharePoint, in which direction, when it happens, and what happens.
DataDirectionWhenWhat happens
Folder and file listingSharePoint to FinturaOn the first crawl, then on a scheduleNames, file types, sizes, modified dates and the folder structure are indexed for the folders you mapped.
File contentsSharePoint to FinturaOn demand, when you open or import a fileThe file itself is fetched at the point you need it, so Fintura is not holding a second copy of your drive.
A single file copied into FinturaSharePoint to FinturaOn Import to FinturaImport to Fintura puts one chosen file in Fintura's own document vault, which is what signing, reminders and expiry tracking run on.
Folder to client mappingIn FinturaOn setup, and whenever you change itA remote folder is pointed at a Fintura client, and only mapped folders show up anywhere in the product.
Sync healthIn FinturaDuring the first crawl, and after each runA sync health view reports progress and anything that failed, so a half-built index is visible rather than silent.

How you would use it

  1. Connect with a practice-owned account

    Documents, then Cloud, then the Connect tab, then Connect on the SharePoint tile. Use an account the firm owns rather than one person's, because the connection lives and dies with the account that made it.

  2. Map folders to clients

    On the Mapping tab, point each SharePoint or OneDrive folder at the client it belongs to. Whole-drive sync is deliberately not on offer, so every file that appears in Fintura belongs to a named client.

  3. Open the client's Files tab

    Each client's Files tab now carries two tabs, Cloud and Fintura Files. Cloud shows the real folder hierarchy with a provider badge and a freshness chip, and opening a file takes you to it in SharePoint.

  4. Import the ones Fintura has to act on

    Where a document has to be signed, chased or watched for expiry, choose Import to Fintura to copy that one file into Fintura's own vault. Everything else stays exactly where it is.

What it does not do

  • Does not work both ways. It is read-only and one way, enforced at the permission level, so documents created in Fintura do not flow out to SharePoint.
  • Does not mirror or back up your files. Fintura holds an index of what is there, not a copy of it.
  • Does not sync your whole drive. Folders have to be mapped to a client, and unmapped files never appear.
  • Does not let you upload, rename, move or delete from inside Fintura. Those stay jobs for SharePoint or OneDrive.
  • Does not make a cloud file behave like a Fintura document. Signing, reminders and expiry tracking need an explicit Import to Fintura first.
  • Does not outlive the account that made the connection. Connect with an account the practice owns, because a connection made with an individual's account dies when they leave.
  • Does not reach other cloud storage. The connection Fintura makes is a SharePoint one, and OneDrive folders are covered because they sit behind it.

Three steps to connect SharePoint

  1. 1

    Open the Cloud connect tab

    In Fintura, go to Documents, then Cloud, then Connect, and choose Connect on the SharePoint tile.

  2. 2

    Authorise with an account the firm owns

    Sign in with a practice-owned account, such as a shared files address, so the connection does not disappear when one person leaves.

  3. 3

    Map folders to clients

    On the Mapping tab, point each SharePoint or OneDrive folder at the Fintura client it belongs to, then let the first crawl build the index.

FAQ

Frequently asked questions.

What South African firms ask about SharePoint in Fintura.

Yes. The tile in Fintura is named SharePoint because that is the connection being made, and the OneDrive folders it reaches are mapped to clients in exactly the same way. Both appear together on a client's Files tab once mapped, in their real folder hierarchy.

No, and not merely by convention. It is read-only and one way, enforced at the permission level, so Fintura is not capable of writing to your drive. Documents created in Fintura stay in Fintura, and nothing anyone does in the product can rename, move or delete a file in SharePoint.

No, and that is deliberate. Folders are mapped to the client they belong to, and only mapped folders are indexed or shown, so a file with nothing to do with a client never lands in Fintura. It also means a folder nobody has mapped is invisible in the product, which is worth remembering when a file seems to be missing.

Only when you ask it to. Fintura holds an index of names, file types, sizes, modified dates and folder structure, and fetches the file itself when somebody opens it. Import to Fintura is the one action that copies a file into Fintura's own vault, and that copy is what signing, reminders and expiry tracking run on.

The connection stops working, which is why the connect screen asks for an account the practice owns rather than an individual's. A connection made with one person's account depends on that account continuing to exist, so a shared files address held by the firm is the safer choice. Remapping folders afterwards is avoidable work.

Interactive demo