Help & Documentation

What is AppHub?

AppHub is a lightweight, single-install hub for the applications most small businesses use every day. Install once, onboard a tenant, and access CRM, projects, content, files, and team coordination without juggling separate products.

Signing in

Navigate to your organization's AppHub URL and sign in with the email and password set up by your administrator. If you forgot your password, use the "Forgot password" link on the sign-in page.

Your workspace

A workspace (tenant) is an isolated environment for your team or organization. Each workspace has its own data, users, roles, and enabled modules. Users can belong to multiple workspaces.

Hub overview

After signing in you land on the Hub — a launcher showing all the modules enabled for your workspace. Click any module tile to open it. The top navigation bar provides quick access to Admin, Hub, CRM, PM, and other menus depending on your enabled modules.

Enabling modules

Tenant administrators can enable or disable modules from Admin → Applications. Only enabled modules appear in navigation and the hub launcher. Some modules (like Inventory) implicitly enable others (like Products).

AppHub is built for multiple organizations on one install. Each tenant (workspace) is an isolated environment with its own data, users, modules, and settings.

One install, many workspaces

A single AppHub deployment can host many tenant workspaces. Data is scoped by TenantId on operational tables. Users sign in once and work inside the workspace they were invited to.

Tenant vs workspace

In the UI you will see workspace and tenant used interchangeably — both mean the same isolated organization context.

Provisioning workspaces

• TenantAdmin users can create additional workspaces from Admin → Tenant workspaces.
• Each workspace gets its own module selection, roles, company profile, and integrations.
• CRM accounts are customer companies inside a workspace — not the same as a tenant workspace.

Security & isolation

• Row-level security (RLS) can restrict read-only SQL logins to a single tenant's rows.
• Module RBAC controls which apps each role can open within a workspace.
• Optional read-only database access for Power BI, Excel, or SSMS is provisioned per tenant under Admin → Integrations.

The CRM module helps you manage your sales pipeline and customer relationships.

• Accounts — companies or organizations you do business with. Each account has a status, industry, address, and linked contacts.
• Contacts — individual people associated with accounts. Contacts have roles, email, phone, and activity history.
• Leads — potential new business. Track source, status, and convert qualified leads into accounts and opportunities.
• Opportunities — active deals in your pipeline. Set stages, expected revenue, probability, and close dates. View them on the pipeline board or as a list.
• Activities — calls, emails, meetings, and tasks linked to any CRM record. Log interactions and set follow-up reminders.
• Products & pricing — product catalog with pricing tiers for quoting and ordering.

Plan, track, and deliver work across your team.

• Projects — group work items by initiative. Each project has a start/end date, status, and assigned team members.
• Work items — tasks, bugs, or user stories. Assign priorities, phases, statuses, and due dates.
• Board view — Kanban board for visual workflow (see Kanban boards).
• Schedule view — timeline and calendar views to see workload distribution.
• Statuses, priorities & phases — fully customizable per workspace. Define your own workflow stages.

AppHub uses Kanban-style boards to visualize work and sales pipeline stages. Drag cards between columns to update status.

Project management board

• Open PM → Kanban Board (or a project's board view) to see work items as cards grouped by status.
• Drag a card to another column to change its status.
• Filter by project, assignee, sprint, or phase depending on your workspace setup.
• Use the schedule view when you need a timeline instead of columns.

CRM pipeline board

• Open CRM → Pipeline for an opportunity board organized by sales stage.
• Drag deals between stages as they progress toward close.
• Toggle closed/won/lost columns when you need to review terminal stages.
• Card details link back to the opportunity, account, and activities.

Tips

• Statuses and stages are configurable per workspace under PM or CRM settings.
• Board layout preferences (such as showing closed items) may persist in your browser for convenience.

Back-office operations: define products, buy from vendors, sell to customers, move stock in warehouses, and match bills to receipts. This is AppHub's operational core module.

Products vs full SCM

Two module tiers are available:

• Products — catalog-only for storefront use (SKUs, categories, pricing).
• Inventory (SCM) — full supply chain; automatically enables Products.

Open the Supply Chain megamenu in the top bar, or go to /inventory for the hub launcher. Navigation is grouped into Purchasing, Sales, Warehouse, and Inventory.

Purchasing

• Vendors — supplier records linked to organizations in your contact directory.
• Purchase orders — create POs, track status, and receive goods against lines.
• Vendor bills — AP bills with three-way match (PO, receipt, invoice).

Sales

• Quotes — customer quotes that convert to sales orders.
• Sales orders — fulfill customer demand; drives picking and shipping.
• Invoices — customer billing tied to shipped orders.

Warehouse & inventory

• Warehouses & locations — multi-warehouse stock with bin/location tracking.
• Receipts & put-away — receive POs and place stock into locations.
• Shipments & pick lists — pick (FEFO by expiration), pack, and ship with packing slips.
• Transfers — move stock between warehouses or locations.
• Cycle counts — physical inventory counts and adjustments.

Document numbers

PO, SO, quote, receipt, shipment, transfer, invoice, bill, and cycle-count documents use tenant-scoped sequences (e.g. PO-2026-0001) via Site_NumberSequence.

Many SCM screens are still being built; hub pages and APIs are rolling out phase by phase. See About AppHub for the current roadmap.

Author and publish content from your workspace.

• Compose — write posts using a rich-text editor or switch to HTML source mode for full control. Save drafts and preview before publishing.
• Categories — organize posts by topic.
• Publishing — set status to Draft, Published, or Archived. Published posts appear on your public site's blog section.
• AI review — use the "Review in assistant" link to get AI-powered feedback on your post in the Workspace assistant.
• Public blog — published posts are available at your organization's public URL under the blog section.

Manage files, folders, and attachments for your workspace.

• Folders — create nested folder structures to organize files by project, department, or topic.
• Uploads — drag-and-drop or browse to upload files. Supports images, documents, and general file types.
• Attachments — link files to CRM records, projects, and other entities across the hub.
• Stock assets — shared image library available to all workspace users for blog posts and content.

Stay informed with the in-app notification system.

• Inbox — all your notifications in one place. Unread items show a badge in the top navigation bell icon.
• Compose — administrators can send notifications to workspace users. Choose recipients and write your message.
• Email delivery — notifications can optionally be delivered via email using the configured SMTP settings.

A shared hub calendar for your workspace.

• Events — create events with title, date/time, description, and color coding.
• Views — switch between month, week, and day views.
• Reminders — set alerts for upcoming events.

The Workspace assistant (Hub → Workspace assistant or /apps/assistant) is an AI chat scoped to your organization. It can answer questions, draft content, and generate formatted HTML reports from live workspace data.

Getting started

• Configure AI under Admin → Integrations → AI assistant — built-in model or bring your own key (BYOK).
• Enable Allow read-only workspace data when you want the assistant to query your tenant database for MODULE SCOPED DATA.
• Pick a module scope (CRM, PM, Blog, etc.) in the assistant panel — not General — so scoped data loads on send.

Module scopes

Scope tells the model which module context and data snapshot to use. Examples: summarize open opportunities (CRM), draft a project status narrative (PM), or review a blog post (Blog). Blog compose also offers Review in assistant after you save a draft.

Report generator

Use preset prompts or ask in your own words for structured HTML reports — executive summaries, tables, KPI-style sections, and narrative analysis. Built-in templates include:

• PM — project status report, phase progress report.
• CRM — pipeline & forecast report, activity & follow-up report.
• General — comparison / decision matrix reports.

Reports output as HTML suitable for pasting into email or rich editors. The assistant marks uncertain facts with [VERIFY] when data is incomplete. It does not silently create or change records — review before acting on recommendations.

Safety & limits

• Do not paste passwords, API keys, or payment card numbers into the chat.
• Answers are based on configured scope and available data — if MODULE SCOPED DATA is empty, enable read-only data and select a module scope.
• Rate limits and token usage may apply per tenant AI settings.

Admin → Integrations connects your workspace to external services. Secrets are stored encrypted and are not shown again after save.

Applications

Choose which hub modules appear in navigation and the launcher (CRM, PM, Blog, Inventory, etc.). Disabled modules return 404 if opened by URL.

Email (SMTP)

Override system email with tenant SMTP — host, port, SSL, credentials, and from/reply addresses. Used for notifications and system mail when enabled.

AI assistant

Built-in AI endpoint or BYOK, optional read-only SQL access for MODULE SCOPED DATA, and toggles for which modules the assistant may query.

Read-only database

Provision a per-tenant SQL login for Power BI Desktop, Excel, Tableau, or SSMS. Row-level security limits results to that tenant's TenantId. Copy the connection string from the Integrations tab when active.

Coming soon

• QuickBooks Online — OAuth connect, sync products, vendors, customers, invoices, and bills.
• Stripe — platform billing and payment webhooks.
• Carrier APIs, maps, and additional provider keys as modules ship.

The public home page at / is edited under Admin → Public site branding (TenantAdmin only). One profile controls the marketing site for the AppHub instance.

Enable or disable the landing page

On the General tab, Use landing page controls whether / shows the public marketing home or redirects visitors to sign in and the hub launcher. Public blog URLs still follow the separate Use blog setting.

Landing theme & hero

• Home hero — theme skin, color mode, navbar style, and hero image for the stock AppHub landing layout.
• Upload a hero image (JPEG, PNG, WebP, GIF, or SVG) or restore the stock illustration.
• Use Preview home after saving to confirm appearance.

Custom landing page

When Use custom landing page is enabled, you can replace the stock layout with your own HTML content (mission/about blocks, calls to action, etc.) while still using the shared theme controls.

Footer & contact

Contact and About & social tabs configure footer text, inquiry email routing, social links, and rich mission content shown on the public site.

Branding separates your public marketing site from signed-in hub appearance and from document letterhead.

Public site branding

Admin → Public site branding — landing theme, hero, footer, public blog toggle, PWA manifest hints, and social links. This is what anonymous visitors see at / and /blog.

My organization (letterhead)

Admin → My organization — legal company name, logo, address, phone, and tax ID used on purchase orders, sales orders, invoices, and other generated documents. This is per-tenant workspace data, not the global landing editor.

Brand & PWA tab

• Public logo and favicon-style assets for the marketing site header.
• Theme color and PWA-related metadata for add-to-home-screen experiences.
• Preview the home page after changes to verify logo and colors.

Hub vs public

Signed-in users see the hub topbar and module chrome. Public visitors see the organization header on the landing page and blog. Configure each area in the appropriate admin screen so marketing and operations stay consistent.

Configuration and management tools for tenant administrators. See also dedicated help for Multitenancy, Integrations, Landing page editor, and Site branding.

Tenant workspaces

Create and manage isolated workspaces, switch context, and provision new organizations on the install.

User manager & roles

Invite users, assign roles, and set per-module permissions. Roles control access to CRM, PM, Admin, and other modules independently.

My organization

Company letterhead for operational documents — distinct from the public marketing site editor.

Dashboards

Summary widgets for home, CRM, projects, and (when enabled) inventory — available from the Admin megamenu Dashboards section.

These modules are on the roadmap and will be added in future releases:

• Commerce & POS — public storefront, shopping cart, checkout, and point-of-sale for events and services.
• Accounting — general ledger, accounts receivable/payable, invoices, vendor bills, and financial reporting.
• Assets & field service — asset registry, maintenance schedules, service history, work orders, and technician appointments.
• Human resources & payroll — employee records, time tracking, timesheets, leave management, and payroll export.
• QuickBooks Online — sync products, vendors, customers, invoices, and bills with QuickBooks.
• Stripe payments — platform billing and tenant commerce via Stripe Checkout, webhooks, and Customer Portal.

Visit About AppHub for the full feature list and roadmap.

Glossary

Term	Definition
Tenant	An isolated workspace with its own data, users, and configuration. One AppHub install can host many tenants.
Workspace	Another name for a tenant — the working environment a team signs into.
Module	A functional area of the app (CRM, PM, Blog, etc.) that can be enabled or disabled per workspace.
Hub	The signed-in area of AppHub where all enabled modules are accessible from a central launcher.
Scope	In the workspace assistant, the module context that shapes which data and prompts the AI uses.
RBAC	Role-based access control — permissions assigned to roles, which are assigned to users.
BYOK	Bring your own key — tenants provide their own AI API key for the workspace assistant.
MODULE SCOPED DATA	Read-only snapshot of tenant data the assistant loads for the selected module scope when sending a message.
TenantAdmin	Workspace administrator role — can manage users, integrations, public site, and tenant provisioning.