SPIRITTSharePoint

SharePoint
Lists into working services

SPIRITT builds apps around SharePoint lists and libraries, maintains document workflows, and connects site records to the people and systems doing the work.

SPIRITT Workspace input reading Connect me to SharePoint, with the SharePoint icon in a compact app tile.

What you can do with SharePoint.

  • Useful list-backed apps

    Turn SharePoint fields, items, and attachments into focused request desks and operational registers with a usable interface.

  • Controlled document changes

    Carry a document through checkout, content and metadata updates, and check-in, with its final version verified before handoff.

  • Current site operations

    Use list and file change tracking to keep indexes and connected work queues aligned without rebuilding them from scratch.

Get started in three steps.

01

Open a workspace

Create a SPIRITT workspace for the SharePoint-backed service or document operation you want to run.

A workspace connected to documents and knowledge
02

Connect SharePoint

Authorize the relevant SharePoint sites and the list, library, and administration permissions needed for your mission.

SPIRITT Workspace input reading Connect me to SharePoint, with the SharePoint icon in a compact app tile.
03

Delegate a site outcome

Name the lists, libraries, and completion rules. SPIRITT builds the service, connects your tools, and maintains the workflow.

Knowledge, work items, and recurring workflow arrows

Make your sites do the work

Questions

SharePoint, with SPIRITT.

01Can SPIRITT build an app backed by SharePoint lists?+
Yes. It can create lists and fields, create or update items, and add or retrieve attachments. Those objects can support a facilities desk, inspection service, or supplier register. SPIRITT builds the interface and operating workflow while SharePoint remains the record store.
02Can it manage document content as well as list fields?+
Yes. SharePoint actions include file download and upload, file metadata updates, checkout, check-in, and version restoration. SPIRITT can therefore run a controlled revision workflow as well as update the operational list tracking that document. Library requirements and the selected check-in behavior still apply.
03How does access work across sites, lists, and items?+
SPIRITT works within the authorized SharePoint scope. It can inspect site groups and role definitions, change list or item inheritance, and add role assignments. Site permissions and file-sharing details do not prove list access. For list changes, SPIRITT can coordinate authorized read and edit tests with designated users and record expected versus observed results.
04Will a workflow notice changes below the top-level folder?+
It can. A complete initial inventory must traverse subfolders rather than treat a single folder listing as recursive. SPIRITT can then maintain saved file-change checkpoints and process list changes to refresh the relevant records, including renamed or removed content.
05How can SharePoint coordinate with the rest of our operation?+
Salesforce can supply a project handoff, Microsoft Teams can carry technician updates, and Outlook can pursue missing supplier documents. SPIRITT keeps their outcomes tied to SharePoint list items, attachments, and library files, so communication and the operational record stay connected.
06Does a successful copy request mean the file is ready?+
Not necessarily. SharePoint file copying can run asynchronously, so acceptance only starts the operation. SPIRITT checks for completion and verifies the destination before handing over a package. Recovery is also explicit: restoring a recycle-bin item and restoring a file version are different actions for different problems.
Buy from builders who use what they sellBuilt usingSPIRITT