How is AccessPoint different from a FOI/ATIP request tool like ATIPXpress, GovQA, AccessPro, or AMANDA's FOI module?
Those tools manage access requests and stop there. AccessPoint manages the full access-and-privacy mandate in one platform — requests plus Privacy Impact Assessments, Algorithmic Impact Assessments, breach notification, complaints, and a privacy risk register — and it runs natively inside your own Microsoft 365 tenant rather than a vendor's cloud. Your data never leaves your control.
How is it different from a privacy platform like OneTrust?
General-purpose privacy suites are built for commercial enterprises and host your data on their own cloud. AccessPoint is purpose-built for public-sector access and privacy, unifies the access (FOI/ATIP) side that those suites don't cover, and deploys into your Microsoft 365 and Azure tenant so you keep full data sovereignty. It operates the work — screeners, section assignment, the live breach-notification calculator, the risk register — rather than handing you a template library.
Does AccessPoint help with Ontario's Bill 194 PIA requirements?
Yes. Since July 1, 2025, FIPPA institutions must complete written Privacy Impact Assessments before collecting personal information, and Bill 194 introduces new AI requirements. AccessPoint's assessment engine runs PIAs and Algorithmic Impact Assessments end to end — screening, questionnaire, risk register, review, and a regulator-ready summary — with a full audit trail.
Can AccessPoint redact video and audio recordings?
Yes, natively — no per-seat video add-on. Body-worn camera, CCTV, 911 and dispatch audio, interview recordings, voicemail, and Teams meeting recordings up to 50 GB open in a viewer built for review. Every mark covers a span of the timeline and, for video, a region that can follow a person automatically; the effects are box, blur, and pixelate for the picture, mute, bleep, and voice distortion for the sound, or withholding the whole recording. Each mark carries its statutory exemption, alternates, and approval exactly like a page redaction. Faces and on-screen text are detected in your own tenant and proposed for a person to accept, transcripts let you find a spoken name and mute the moment it is said, and the release is a burned MP4 or MP3 with the citation captioned in the frame, a manifest of file hashes, and a per-span redaction log.
Does AccessPoint have a public request portal and online payments?
Yes. The public request portal is an optional web app you deploy in your own Azure subscription. Requestors file requests, complaints, or privacy concerns through guided, accessible forms; confirm their e-mail address with a one-time code; track status and reply; answer fee estimates and pay online through your own payment provider (Stripe, Paymentus, or another processor's hosted payment page); and download released records through a secure delivery. Approved releases can be published to a searchable public reading room. Every submission lands in a Portal inbox for your team to triage. The portal, payments, and reading room are included in every AccessPoint plan.
Can AccessPoint search records outside Microsoft 365?
Yes, through repository connectors. Records in GCdocs (OpenText Content Server), Hyland OnBase, Laserfiche, Axon Evidence, network file shares, CMIS repositories such as Alfresco, SQL databases, Azure Blob storage, and MCP search servers are browsed and searched from the same picker as SharePoint and Outlook, then captured server-side with a verified hash and a record of where each came from. Connectors for on-premises systems run beside the source and are reached through Azure Hybrid Connections — no VPN or inbound firewall rule. Connectors are included in every plan, with no per-connector fee, and an open protocol and SDK let you build your own.
Can we adopt it just for access requests now and add the privacy modules later?
Yes. Every module shares one platform but is enabled through configuration. Many teams start with ATIP/FOI request management and turn on assessments, incidents, complaints, and the risk register as their privacy program matures — no migration, no new system.
We're on a legacy ATIP/FOI system today — can we bring our history with us?
Yes. Settings → Data import & export generates an Excel template pre-filled with your tenant's own type codes; fill one row per historical request, assessment, incident, or complaint — plus requestors, risks, and vendors — upload it, and read a per-row validation report before anything imports. Legacy case files stage through a pre-provisioned container in your own Azure storage, with optional hash verification for chain of custody. Imported records are historical by construction: no notifications fire, no deadlines recompute, and every record carries an Imported audit-trail entry. The Export tab produces the same workbook back at any time, so you can rehearse against a test tenant first — and you're never locked in.
Where does our data live, and who can see it?
All records, documents, assessments, incidents, and audit history reside in your own Azure and Microsoft 365 tenant. The publisher has no runtime access to your environment. Within your tenant, role-based access control and a PII filter keep custodians and contributors walled off from requestor and data-subject identity.
What about AI — does AccessPoint send our data to an AI service?
Only if you choose to deploy the optional AI Assist components, and even then the Azure OpenAI, AI Search, and OCR resources run inside your own tenant's Azure subscription with managed-identity-only access — nothing goes to the vendor or any third-party AI service, and Microsoft does not train models on your content. Every AI output is a suggestion or an editable draft a person decides on, prompts and responses are never stored, a monthly token budget you control caps all AI processing, and each request's case audit export discloses any AI involvement.
What Microsoft 365 licenses and infrastructure are required?
AccessPoint has no dependency on specific Microsoft 365 licensing tiers and needs no Power Platform or Dataverse licensing. It runs as a SharePoint web part or Teams app against an Azure backend you deploy from a one-click Bicep/ARM template in the Azure portal — App Service, SQL, and Blob storage in your own tenant's subscription. No separate servers to manage.
Are there Azure hosting costs on top of the license?
Yes, and that's by design. AccessPoint runs in your own tenant, so the Azure resources it uses — App Service, Azure SQL, and storage — bill directly to you through Microsoft, starting at about $175 per month for a standard configuration and scaling with your size and usage. You pay Microsoft's cost with no vendor markup and control the sizing yourself, unlike SaaS tools that bundle marked-up hosting into per-user fees. It's a fraction of the flat license, and a rounding error next to legacy ATIP software. Optional capabilities bill the same way, in your own subscription: Azure AI Speech transcription per audio hour, Document Intelligence per page or video frame, and a scale-to-zero media processing job that costs nothing while idle.
Is AccessPoint available in multiple languages?
Yes. The entire interface ships natively in 11 languages — English and French out of the box for Canadian government requirements, plus Danish, Dutch, Finnish, German, Italian, Polish, Portuguese, Spanish, and Swedish. Case content such as scope, correspondence, and closure summaries can also be translated per record, with the original always one click away.