Fabric Client Portal Publishing and Link Analytics (Delivery)

Fabric Client Portal Publishing and Link Analytics (Delivery)

1. 01

   Confirm the client workspace is on a plan that supports portal publishing

   Pro at $18 monthly (annual billing) includes premium data connections and up to 10 scheduled AI agents; Plus at $8 monthly caps at 50GB storage and 5x AI usage. Portals with heavy file streaming need the 250GB ceiling in Pro.

2. 02

   Move all client deliverables into a dedicated Fabric folder before publishing

   Fabric streams files instantly across devices, so the folder becomes the single source for the portal. Keep intake documents, meeting transcripts, and final assets in separate subfolders so the portal link exposes only what the client should see.

3. 03

   Publish the password-protected client portal from the Fabric workspace

   Set a unique password per client rather than a shared agency password. Fabric does not publish a white-label program, so the portal carries Fabric branding; tell the client that before the link goes out, not after.

4. 04

   Verify engagement analytics are recording before sending the link

   Open the portal in an incognito window, click through two or three files, then check that the link analytics register the visits. If nothing logs, the client will see a dead portal and the retainer conversation gets harder.

5. 05

   Attach a scheduled AI agent to summarize client calls and update project tasks

   Fabric agents run across 50+ integrations including Slack, Notion, Google Drive, Salesforce, and HubSpot. Schedule the summarizer to post into the client's Slack channel or Notion page so the portal and the task board stay in sync without manual copying.

6. 06

   Send the portal link with a one-paragraph access note

   State the password, the folder structure, and what the analytics will show the agency. Clients who know their file opens are visible tend to engage with the portal instead of emailing for copies.

7. 07

   Review link analytics at the end of the first week and log the result

   Record which files were opened and by whom. Use that data in the next retainer review: a portal nobody opens is a delivery problem, not a client problem.