English

Initial setup — API base URL, Azure deploy and update, Update now for the SharePoint package, notifications, licence status, the read-only state when a subscription lapses, and the first-run sequence

Last updated: November 10, 2026 by Steve

Initial Setup

Settings > Setup is the first screen you configure after deployment. It connects the SharePoint web part to your Azure back end, launches the Azure deploy/update flow, keeps the SharePoint package current, and controls how notifications reach users. You must have the Administrator role to open it.

AccessPoint for Microsoft 365 only. Hosted AccessPoint has no Setup row: Realizer runs the service, sends its e-mail and keeps it current. Hosted administrators find the plan in Subscription and the organization's e-mail in Organization.

Setup panel

API base URL (usually automatic)

The API base URL is the address of your AccessPoint API service in Azure. The web part normally discovers it on its own: the API self-registers its public URL with the Realizer platform when it validates its license (within minutes of the App Service starting), and the web part fetches it from there — usually there is nothing to do here.

To pin the URL manually instead (for example, a custom domain):

  1. API URL — Enter the App Service URL of your AccessPoint API (for example, https://app-accesspoint-contoso.azurewebsites.net). It must use HTTPS.
  2. Click Save. AccessPoint validates that the URL uses HTTPS before storing it, and a manual URL takes precedence over discovery.

Azure deploy and update

The Setup screen is also the entry point for provisioning and updating the Azure back end:

  • Deploy to Azure opens the Azure portal with the AccessPoint deployment form: a guided wizard with four pages — Basics, Features, Security and compliance and Advanced. Each question says what it does and, for the optional components, what it costs; follow-up questions appear only when you turn their feature on. It provisions the App Service, SQL database, and storage into your own subscription.
  • Deploy update to Azure opens the same form in Upgrade existing installation mode against an existing deployment to apply new versions. The form does not read back your earlier choices, so answer every question the way the installation was set up.

Both are covered end to end in the Deployment Guide; use it for the full step-by-step, including SPFx and Teams app installation.

First install of the SharePoint package

At the end of Finish Setup — the publisher's page that grants the Microsoft Graph permissions the deployment needs — an install page signs you in to Microsoft 365 in your own browser, checks Realizer's signature on the SharePoint package and installs it into your tenant app catalog with your own SharePoint permissions. There is no file to download or upload, and your Microsoft sign-in is never sent to Realizer. Until the application identity has its permissions, Setup shows a Finish Setup link.

Update availability

AccessPoint tells you when a newer version is available — nothing to subscribe to or poll manually. During routine license validation, the Realizer Platform reports the latest published AccessPoint version (no usage or case data is involved), and Setup shows the result:

  • Update available — shown here (and on the dashboard) when the published version is newer than the one your API is running, with the current and latest version numbers.
  • "Your AccessPoint API is up to date." — shown when you're already current, or running a pre-release build newer than the published release.

When an update is available, click Deploy update to Azure to open the same deployment form, pre-set to Upgrade existing installation — see Updating AccessPoint in the Deployment Guide for the full procedure.

Update the SharePoint package without the admin center

Setup also shows the SharePoint package version and flags a newer one — in particular when the web part is older than the API it talks to, because features added since stay hidden until the package is updated.

An AccessPoint administrator whose Microsoft 365 account may add files to the tenant app catalog's Apps for SharePoint library sees Update now. AccessPoint checks that right with your own SharePoint session when Setup opens; if you do not have it, the button is not offered and Setup says why.

  1. Choose Update now. Your AccessPoint API downloads the package for that version from Realizer and verifies it before anything else happens: Realizer's signature over the release and over the package, the package's checksum, and that it is AccessPoint at the version you asked for. A package that fails any check is refused with the reason and never reaches your browser or SharePoint.
  2. A confirmation says plainly what will happen: the AccessPoint package in your tenant app catalog is replaced with the new version and deployed to all sites at once, and people get it the next time they refresh the page. If your catalog holds the copy acquired from the SharePoint Store, the Store copy is replaced. If the new version asks for new Microsoft 365 permissions, they are listed with what each one enables.
  3. Confirm. Your browser uploads the verified package to the app catalog and deploys it with your own SharePoint permissions — AccessPoint gains none. Each step is shown as it runs.
  4. When it reports Updated to the new version, choose Reload the page.
  5. If the version declares new permissions, a SharePoint or Global administrator approves them in SharePoint admin center > Advanced > API access.

Every update is written to the audit trail. If it stops part-way, a failure at Upload usually means SharePoint refused your account; a failure at Deploy or Confirm may leave the new package in the catalog without being deployed, so run Update now again. Releases published before release signing existed (2.1.0 and earlier) cannot be updated this way.

Two more options sit beside it:

  • Ask your SharePoint administrator (offered to everyone) opens a ready-made message saying what is out of date, why it matters and both ways to update. Choose Copy, or Open as email.
  • Advanced: reinstall a previous version of the SharePoint package installs a published version through the same verified path, to go back after a problem. An older web part against a newer API hides the features added since, and the confirmation warns when that is the case.

You can always update by hand by uploading accesspoint.sppkg to Apps for SharePoint; see the Deployment Guide.

Microsoft 365 permissions waiting for approval

Setup (and, for administrators, a card on My Day) lists any Microsoft Graph permissions that the installed package asks for and your tenant has not approved yet, each with the feature that does not work until it is. A SharePoint or Global administrator approves them under SharePoint admin center > Advanced > API access.

Optional AI capabilities

The deploy/update flow also exposes four optional capabilities, none required to run AccessPoint. Three — AI Assist, AI Search, and Document Intelligence — are off unless you turn them on at deploy time; the Copilot capture permission is granted by default but can be opted out. They are covered in full in the Deployment Guide.

  • Deploy AI Assist — provisions an Azure OpenAI resource in your own Azure subscription and region (managed-identity auth, no API keys). Billing is pay-per-use, so an idle tenant pays about $0. Deploying it enables the AI Assist features, each of which stays individually switchable under Settings > Features. Every AI output is a suggestion or an editable draft — a person always decides.
  • Deploy AI Search — adds Azure AI Search, enabling full-text search of document content and, when AI Assist is also deployed, semantic search. If documents predate the resource, run the Administrator-only Index existing documents sweep under Settings > Setup > Document content search.
  • Deploy Document Intelligence — adds Azure AI Document Intelligence for OCR: scanned, image-only documents get their text read so they participate in content search, duplicate detection, AI summaries, and redaction suggestions. Pay-per-page billing.
  • Copilot capture permission — the tenant-wide AiEnterpriseInteraction.Read.All Graph permission is granted by default so custodians can capture Copilot interaction history out of the box. Least-privilege tenants can opt out with -DisableCopilotCapture on the deployment script (or grantCopilotCapturePermission=false on the ARM/Bicep template), and can revoke the app role in Entra ID at any time.

Licence, announcements and banners

Setup shows your licence, and administrators (only administrators) see banners about it and about Realizer news:

  • Announcements from Realizer — short notes about release news, planned maintenance on a Realizer service and "action recommended" items appear under any security advisories, in your language when Realizer has translated the note. A dismissed note stays dismissed in that browser until Realizer corrects its text. Other users never see them, and they are not e-mailed. There is nothing to set up.
  • Subscription suspended — Microsoft has suspended your AccessPoint subscription because of a payment problem. AccessPoint keeps working and nothing is blocked. Resolve the payment in your Microsoft billing account; the banner clears at the next licence check after Microsoft reinstates the subscription. Microsoft cancels a subscription that stays suspended for 30 days.
  • License revoked — Your AccessPoint license was revoked by Realizer on … AccessPoint keeps working through the grace period the banner counts down (7 days by default). After it, AccessPoint becomes read-only — it no longer stops (see When the subscription lapses). Nothing is deleted. Contact Realizer. When the subscription is restored, the next licence check clears it; an administrator can choose Check again.
  • Modules not in your subscription — a feature whose module your subscription does not include (AI Assist, Public portal, Media, Repository connectors, AccessPoint Learning) shows its switches locked with Not included in your subscription. Contact Realizer to add the … module. The same message appears on the Public portal, Payment providers, Repository connectors and AI suggestions pages. Nothing already created is deleted; it comes back when the module is licensed again.

The core product and its modules

A subscription always includes the core product: the five case registers, the documents and redaction workspace, reviews, correspondence, reports, jurisdiction packs, Lab mode and learning — the How we decide coach and coach notes, My learning, the jurisdiction packs' modules and learning paths, and completion records. Five modules sit beside it: AI Assist, Public portal, Media, Repository connectors and AccessPoint Learning (writing your own learning modules in the Studio, learning path settings, your organization's blocks on pack modules, and audience rules). Today's Microsoft Marketplace plans include all five; Hosted AccessPoint sells AccessPoint Learning as an add-on.

A module works when your licence includes it, its Azure resource is deployed where it needs one, and it is switched on in Settings → Features. When the licence leaves AccessPoint Learning out, the Studio opens on its Coach tab only and its other tabs say the module is needed, and audience rules stop enrolling and withdrawing people; published modules, learning paths, enrolments and completion records stay, and learners keep taking what they were given.

When the subscription lapses

Since 2.6.0, a subscription that has expired beyond its grace period (7 days by default) — or that Realizer revoked, after the grace period counted from the revocation — no longer stops AccessPoint. It becomes read-only, indefinitely, so your organization can always reach its own records:

  • Everything you can read keeps working: lists, case pages, documents and their preview, search, reports and dashboards, My Day, audit history, exports (response packages, evidence packages, the Settings export workbook, survey and report exports) and downloads.
  • Lab mode keeps working, fully — its changes go to the training copy — but uploading your own files into it is off.
  • Your own settings keep working: saving, renaming or deleting your own private view, your own private saved report and your own notification preferences. Anything shared with others — a shared or default view, a report shared with the organization, another person's preferences — is a change like any other.
  • Every other change is refused: no new request is recorded, no case changes, no letter is sent, and no configuration, invitation or role changes. A change refused while someone was typing shows the same sentence — nothing was saved; repeat it after the renewal.
  • Sending and outbound features pause: e-mail and Teams notices (what comes due still shows on My Day — nothing is sent late in a burst), reminders and digests, the follow-up sweep, the automatic acknowledgement, the public portal's intake (it shows is not accepting online requests right now with your contact details; deliveries made before stay downloadable until they expire, and no payment is taken), repository connectors and AI Assist. Media processing waits.
  • Sign-in, the licence refresh and the licence diagnostics keep working.

Everyone sees the banner AccessPoint is read-only: your subscription expired on . You can still view and export your cases and practice in Lab mode. (after a revocation: Realizer revoked this subscription on . Contact Realizer.). Administrators get Renew the subscription (Microsoft Marketplace — Contact Realizer after a revocation) and Check again, which asks Realizer at once (at most once a minute) and reloads AccessPoint when the subscription is valid again; Still expired — checked just now means Realizer has not seen the renewal yet. Everyone else reads Ask an administrator to renew, with the names of your Administrators. Renewing restores everything at the next licence check — nothing was deleted, and paused work resumes on its own.

What does not change:

  • Within the grace period AccessPoint works fully, with the grace banner.
  • With no subscription yet, AccessPoint opens on Finish setting up AccessPoint: subscribe through Microsoft Marketplace (Open the Marketplace offer), run Finish Setup from the e-mail Microsoft Marketplace sends after you subscribe, then select Retry. An administrator who sees Complete setup instead has a subscription, but the deployment's identity has not been granted its licence permission yet: select Complete setup, then stop and start the App Service. A subscription that has lapsed never shows this page.
  • A deployment that cannot reach Realizer keeps full access, with the administrators' banner, for as long as the offline allowance lasts — an outage never makes AccessPoint read-only.
  • On a shared-services deployment, a served organization whose licence expired or was revoked is read-only for its own users alone; the other organizations are untouched.

Rolling back below 2.6.0 while a subscription is lapsed. A version older than 2.6.0 stops on a lapsed licence instead of becoming read-only. Renew before rolling back, or roll forward again.

In Hosted AccessPoint, the plans decide what is read-only — see Read-only, never hidden.

System health and other checks

The Setup panel also carries System health, which tells you whether the database is keeping up, plus the Teams meeting transcripts check, document content search, and the Group-based roles check. Check group-based roles runs a live membership probe for your own account and reports whether the feature is on, whether Microsoft Graph is configured and whether the managed identity can read group membership; see Roles & Permissions.

Notification settings

Notification configuration

Email notifications

  • Enable/disable email notifications — Toggle email on or off for the whole system.
  • Notification sender mailbox — Set the address notifications are sent from. This must be a shared mailbox or user mailbox in your Microsoft 365 tenant (for example, noreply@contoso.com).
  • Click Validate Mailbox to confirm live against Microsoft Graph that the API service principal can send from the specified mailbox.

Teams activity feed notifications

Teams activity-feed notifications are on by default. When enabled, users receive notices in their Microsoft Teams activity feed in addition to (or instead of) email. Toggle them off in this panel if you don't want them.

Run the Teams setup validation check to confirm the app is registered, the activity-send permission is granted, the publisher API is reachable, and the app is present in your catalog.

Set the app link that powers the "Open in AccessPoint" button in notification emails. It is auto-detected when an administrator opens the app; override it here if you want the button to target a specific page. When neither an auto-detected nor a manual link is set, the link line is simply omitted from emails.

Notification delivery health

A notification delivery health strip shows sent / failed / skipped counts for the last 7 days, with the most recent attempts listed — so a silent mail failure is visible without leaving the panel.

Required permissions

These Microsoft Graph permissions must be granted to the relevant service principals for notifications to work.

API service principal

Permission Purpose
Mail.Send Send email as the mailboxes AccessPoint uses: notifications from the sender mailbox, and correspondence from the sender mailbox, an intake mailbox or the officer's own. Restrict it with an Exchange Online application access policy (see E-mail through Exchange Online)
User.ReadBasic.All Resolve basic user information and validate the sender mailbox
TeamsAppInstallation.ReadForUser.All Check Teams app installation status
Application.Read.All Read application registrations
AppCatalog.Read.All Read the Teams app catalog
User.Read.All Find disabled accounts in the nightly directory check (granted by Finish Setup by default; opt-out)
GroupMember.Read.All Resolve membership of the Entra groups that roles are bound to (same default and opt-out as User.Read.All)

Realizer multi-tenant enterprise app

Permission Purpose
TeamsActivity.Send Send Teams activity feed notifications
AppCatalog.Read.All Read the Teams app catalog
User.Read Read basic user profile

These permissions are configured during the deployment process, and the Finish Setup page grants them in one step. After granting GroupMember.Read.All, restart the App Service so the identity picks it up.

First-run sequence

Once Setup is saved, complete these steps to make AccessPoint usable:

  1. Import a jurisdiction pack. Go to Jurisdiction Packs, choose the pack for your jurisdiction (for example, Canada ATIA, US FOIA, or EU GDPR), and click Import. This seeds request types, statuses, exemptions, legal authorities, notification and correspondence templates, calendars, and translations in one step.
  2. Assign user roles. The first user to open AccessPoint is bootstrapped with the Administrator role — the only built-in role. Importing a jurisdiction pack seeds the other roles your office needs (such as Request Coordinator; the Universal baseline also ships a Privacy Officer role). In Manage Users, add users from your directory and assign roles — at least one more Administrator for continuity and at least one coordinator to process requests; custodian, contributor, reviewer, and reader access follows automatically from assigned work.
  3. Verify calendars, languages and localization. Confirm your Calendars have the correct weekend days, jurisdiction, and statutory holidays that drive due-date math, and that your Languages list has the right active languages and default. The pack sets sensible defaults, but these determine your deadlines and every translatable field, so check them before going live. Also set the organization's English spelling and time zone under Localization & Formats.

AccessPoint is now ready for use.