inveazy how-to series: Blog, assistant & files

Part 7 of the inveazy how-to series. How to publish content and use the shared hub tools that sit beside CRM and SCM.

Series: ← Previous: Supply chain & store · Next → Accounting & integrations

Write once in the hub. Approve when it should appear on the public home. Keep secrets in Integrations — never in the chat box.

What you will do

Operations can move stock (Post 6). This guide covers the collaboration and content apps most teams open daily.

• Blog hub — compose, publish, public placement
• Workspace assistant — scopes, premade prompts, HTML reports
• Files, notifications, and calendar — short tour

Hub → Blog

Blog hub

Open Hub → Blog (or Apps → Blog). The hub is a three-column workspace: post list, Quill composer (including HTML source), and metadata (slug, audience, category, tags, featured image, SEO, landing options).

Practical flow:

1. Create a post and set title, slug, excerpt
2. Paste or write the body (HTML source for pasted guides)
3. Set audience to Public when guests should read it
4. Save draft, then Schedule or Publish
5. Request or approve public home placement when it should appear on the marketing home

Public site branding (Post 3) controls whether guests see the public blog frame. Authored posts still live in this hub for signed-in users.

Tip: Stick to simple headings, paragraphs, and lists in Quill. Avoid HTML tables — the editor often flattens them.

Workspace assistant

Open the Assistant app when it is enabled for your role. Pick a module scope on the left (General, CRM, PM, Blog, Inventory/SCM, Accounting, Dashboard, Files, and others your admin enabled), then send from the Message tab.

TenantAdmins configure the Assistant under Admin → Integrations:

• Applications tab — turn Assistant on
• AI assistant tab — built-in model or bring-your-own key (BYOK)
• Allow read-only workspace data — so reports can cite live MODULE SCOPED DATA

Never paste API keys into chat — use Integrations

Tip: Without read-only data and a real module scope (not General), the assistant must not invent pipeline or inventory numbers — turn data on before you run reports.

Premade prompts and HTML reports

On the assistant right rail, open the prompts / Built-in area. Locked templates shape answers when you ask for a report or blog draft. Premade prompt chips fill the message box with a ready ask — swap placeholders like project or account names, then send.

When you ask for a report, status summary, or executive summary, the assistant can return formatted HTML (not plain chat): title, date, numbered table of contents, four KPI cards, status badges, tables first, short prose after each table, and numbered recommendations. Say quick report or one-pager for a shorter version. Print or copy the HTML into email; mark uncertain cross-module guesses with [VERIFY] in the built-in rules.

Premade prompts by scope (labels as they appear in the app):

• PM — Project status, Phase progress, Risk & dependency, Resource & capacity, Weekly standup, Quick one-pager
• CRM — Pipeline & forecast, Activity & follow-up, Account health review
• SCM — What to pick today, PO receive queue, Backorder status, Reorder / low stock, Operations report, Quick one-pager, Web orders queue, Returns (RMA), Reorder alerts, Throughput KPIs, Mobile pick/ship guide
• Accounting — AR collections, AP due review, Finance snapshot
• Blog — Draft a new post, Review & improve a post (Quill-ready HTML)
• Dashboards — Portfolio health, Weekly leadership priorities, Quick one-pager
• Products — Catalog health, Store publish readiness, Inv# brief
• Files — Attachment audit (and related file prompts)
• General — Comparison / decision matrix, Executive summary

Built-in locked formats also include Report / export — rich HTML output and Blog draft — Quill-ready HTML. Workspace rules (tone, terminology, boundaries) sit next to those and apply to every user in the tenant.

Pick scope → choose a premade prompt → send

Files, notifications, calendar

From the hub or workspace shortcuts:

• File manager — shared folders and attachments for quotes, packing lists, and brand assets
• Notifications — inbox for what needs attention; compose when you message teammates
• Calendar — dates alongside CRM activities and PM work when those modules feed it

Each of these must be enabled under Integrations → Applications and allowed on the user’s role — same two-layer rule as Post 4.

What’s next

Continue with Accounting & integrations — invoices and bills, then where Stripe, QuickBooks, email, and API keys live.

For in-app reference anytime after you sign in, open Help from the hub.