<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Novaza Office on Novaza Docs</title><link>https://docs.novaza.ai/office/</link><description>Recent content in Novaza Office on Novaza Docs</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.novaza.ai/office/index.xml" rel="self" type="application/rss+xml"/><item><title>Records &amp; Data</title><link>https://docs.novaza.ai/office/records/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/records/</guid><description>&lt;h1 id="records--data"&gt;Records &amp;amp; Data&lt;a class="anchor" href="#records--data"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Records are the individual data entries stored within a module — the equivalent of rows in a database table. Every record belongs to exactly one module and conforms to that module&amp;rsquo;s field definitions. Novaza Office provides a rich set of tools for viewing, searching, editing, and managing records at scale.&lt;/p&gt;
&lt;h2 id="viewing-records"&gt;Viewing Records&lt;a class="anchor" href="#viewing-records"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Records are displayed in the &lt;strong&gt;Record List&lt;/strong&gt; view by default. You can switch to a &lt;strong&gt;Grid view&lt;/strong&gt; (spreadsheet-style), &lt;strong&gt;Kanban board&lt;/strong&gt;, &lt;strong&gt;Calendar&lt;/strong&gt;, or &lt;strong&gt;Map view&lt;/strong&gt; depending on what field types the module contains. The active view preference is saved per user per module.&lt;/p&gt;</description></item><item><title>Modules &amp; Namespaces</title><link>https://docs.novaza.ai/office/modules/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/modules/</guid><description>&lt;h1 id="modules--namespaces"&gt;Modules &amp;amp; Namespaces&lt;a class="anchor" href="#modules--namespaces"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Modules are the data schemas at the core of Novaza Office. Each module defines a set of fields that describe one type of business entity — for example, a Contact, a Support Ticket, or an Invoice. Namespaces group related modules together into a cohesive application and provide security isolation between different teams or business units.&lt;/p&gt;
&lt;h2 id="namespaces"&gt;Namespaces&lt;a class="anchor" href="#namespaces"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A &lt;strong&gt;namespace&lt;/strong&gt; is a self-contained application environment within your workspace. It has its own set of modules, pages, workflows, and roles. Examples of namespaces you might create:&lt;/p&gt;</description></item><item><title>Workflow Automation</title><link>https://docs.novaza.ai/office/workflows/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/workflows/</guid><description>&lt;h1 id="workflow-automation"&gt;Workflow Automation&lt;a class="anchor" href="#workflow-automation"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Novaza Office includes a visual workflow editor that lets you automate business processes without writing code. Workflows respond to events in your data — such as a record being created or a field value changing — and execute a sequence of actions in response.&lt;/p&gt;
&lt;h2 id="workflow-concepts"&gt;Workflow Concepts&lt;a class="anchor" href="#workflow-concepts"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;A workflow consists of three parts:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Trigger&lt;/strong&gt; — the event that starts the workflow&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conditions&lt;/strong&gt; (optional) — logical filters that must be true for the workflow to proceed&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Steps&lt;/strong&gt; — an ordered list of actions to execute&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Workflows run server-side and are fully audited. Each execution is logged with its trigger event, condition results, step outputs, and final status (success, failed, or skipped).&lt;/p&gt;</description></item><item><title>Pages &amp; Page Builder</title><link>https://docs.novaza.ai/office/pages/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/pages/</guid><description>&lt;h1 id="pages--page-builder"&gt;Pages &amp;amp; Page Builder&lt;a class="anchor" href="#pages--page-builder"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Pages in Novaza Office are the user-facing screens where team members interact with records, charts, and forms. The Page Builder provides a drag-and-drop canvas to design fully custom layouts without writing HTML or CSS. Pages are published within a namespace and are accessible to users who have been granted the appropriate role.&lt;/p&gt;
&lt;h2 id="page-types"&gt;Page Types&lt;a class="anchor" href="#page-types"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Record List page&lt;/strong&gt; — displays a filterable, sortable list of records from a module&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Record Detail page&lt;/strong&gt; — shows the full detail view of a single record with all its fields&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard page&lt;/strong&gt; — a free-form canvas for combining charts, KPIs, and record widgets&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Form page&lt;/strong&gt; — a standalone form that creates or updates a record when submitted&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Chart page&lt;/strong&gt; — dedicated to a single visualization (useful for TV dashboards or embedded views)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="drag-and-drop-canvas"&gt;Drag-and-Drop Canvas&lt;a class="anchor" href="#drag-and-drop-canvas"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Open the Page Builder by clicking &lt;strong&gt;Edit&lt;/strong&gt; on any page or by creating a new page. The canvas is divided into a grid. Drag blocks from the &lt;strong&gt;Block Panel&lt;/strong&gt; on the right into any grid cell. Resize blocks by dragging their edges. Reorder blocks by dragging from the block&amp;rsquo;s handle.&lt;/p&gt;</description></item><item><title>Report Builder</title><link>https://docs.novaza.ai/office/reports/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/reports/</guid><description>&lt;h1 id="report-builder"&gt;Report Builder&lt;a class="anchor" href="#report-builder"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The Report Builder in Novaza Office lets you turn module data into visual charts, summary tables, and scheduled reports. Reports can be embedded in dashboard pages, exported as CSV or PDF, or delivered automatically to a list of recipients on a schedule.&lt;/p&gt;
&lt;h2 id="creating-a-report"&gt;Creating a Report&lt;a class="anchor" href="#creating-a-report"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Go to &lt;strong&gt;Office → Reports → New Report&lt;/strong&gt; within your namespace. Give the report a name, then select the &lt;strong&gt;data source&lt;/strong&gt; (a module). From there you can:&lt;/p&gt;</description></item><item><title>Administration</title><link>https://docs.novaza.ai/office/admin/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/admin/</guid><description>&lt;h1 id="administration"&gt;Administration&lt;a class="anchor" href="#administration"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;The Office Administration panel gives workspace administrators full control over system settings, user access, namespace configuration, and data governance. Most administrative tasks are performed here or in Novaza SSO.&lt;/p&gt;
&lt;h2 id="system-settings"&gt;System Settings&lt;a class="anchor" href="#system-settings"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Access system settings via &lt;strong&gt;Office → Admin → System Settings&lt;/strong&gt;. Key options include:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Workspace name and logo&lt;/strong&gt; — displayed in the top navigation bar&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Default language&lt;/strong&gt; — English or Vietnamese (can be overridden per user)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Default timezone&lt;/strong&gt; — used for scheduled reports and workflow timestamps&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Record deletion policy&lt;/strong&gt; — choose between hard delete (permanent) or soft delete (records are archived and can be restored within 30 days)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File storage limits&lt;/strong&gt; — set a maximum total attachment storage per namespace&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;API rate limits&lt;/strong&gt; — configure per-token request limits for the REST API&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="user-management"&gt;User Management&lt;a class="anchor" href="#user-management"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;While user accounts are created and deactivated in Novaza SSO, the Office Admin panel lets you manage &lt;strong&gt;namespace-level membership&lt;/strong&gt;:&lt;/p&gt;</description></item><item><title>Record Revisions</title><link>https://docs.novaza.ai/office/revisions/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/revisions/</guid><description>&lt;h1 id="record-revisions"&gt;Record Revisions&lt;a class="anchor" href="#record-revisions"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Novaza Office automatically tracks every change made to records, giving teams a complete history of who changed what, when, and what the value was before the change. Revisions are essential for compliance, audit, and for recovering from accidental edits.&lt;/p&gt;
&lt;h2 id="enabling-revisions"&gt;Enabling Revisions&lt;a class="anchor" href="#enabling-revisions"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Revisions are configured per module. A namespace administrator can toggle revision tracking from &lt;strong&gt;Module → Settings → Revisions&lt;/strong&gt;. When enabled, each field update produces a revision entry alongside the main record.&lt;/p&gt;</description></item><item><title>Import &amp; Export</title><link>https://docs.novaza.ai/office/import-export/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/import-export/</guid><description>&lt;h1 id="import--export"&gt;Import &amp;amp; Export&lt;a class="anchor" href="#import--export"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Novaza Office includes a built-in importer and exporter for moving record data in and out of any module. This is useful for onboarding existing data, producing snapshots for offline analysis, and exchanging data between namespaces.&lt;/p&gt;
&lt;h2 id="supported-formats"&gt;Supported Formats&lt;a class="anchor" href="#supported-formats"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CSV&lt;/strong&gt; — Comma-separated values, with a header row for field mapping&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;JSON&lt;/strong&gt; — Line-delimited or array-based JSON, preserving nested structures and typed values&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;CSV is typically used for data produced by spreadsheets and legacy systems. JSON is preferred when field types are complex (multi-value fields, record references, JSON blobs).&lt;/p&gt;</description></item><item><title>External Data Sources</title><link>https://docs.novaza.ai/office/data-sources/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/data-sources/</guid><description>&lt;h1 id="external-data-sources"&gt;External Data Sources&lt;a class="anchor" href="#external-data-sources"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Novaza Office can connect to external data sources so that pages, reports, and workflows can read and display data that lives outside of a namespace&amp;rsquo;s native records. This is useful when teams need to blend Office data with an existing data warehouse, an analytics database, or a line-of-business system.&lt;/p&gt;
&lt;h2 id="supported-connections"&gt;Supported Connections&lt;a class="anchor" href="#supported-connections"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;External data sources are configured as read-only connections from the namespace. Office supports:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Relational databases&lt;/strong&gt; — connect to an existing reporting database using a connection string and service account credentials&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;HTTP / REST endpoints&lt;/strong&gt; — pull JSON data from an authenticated external API at request time&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File drops&lt;/strong&gt; — periodically ingest structured files (CSV, JSON) from a shared storage location&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Connections are defined per namespace and require administrator privileges to create or modify.&lt;/p&gt;</description></item><item><title>Email Notifications</title><link>https://docs.novaza.ai/office/notifications/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.novaza.ai/office/notifications/</guid><description>&lt;h1 id="email-notifications"&gt;Email Notifications&lt;a class="anchor" href="#email-notifications"&gt;#&lt;/a&gt;&lt;/h1&gt;
&lt;p&gt;Novaza Office can send automated emails when records change, workflows execute, or scheduled events trigger. Notification templates centralize the subject line, body, and recipient logic so that automated mail stays consistent across namespaces.&lt;/p&gt;
&lt;h2 id="template-anatomy"&gt;Template Anatomy&lt;a class="anchor" href="#template-anatomy"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Each notification template contains:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Name and description&lt;/strong&gt; — internal identifiers for the template&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Subject&lt;/strong&gt; — a single-line template that can interpolate record fields&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Body&lt;/strong&gt; — an HTML body with support for a plain-text fallback&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Recipients&lt;/strong&gt; — one or more addresses or recipient expressions (see below)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Locale&lt;/strong&gt; — used when the workspace has users on different default languages&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Templates support field interpolation using &lt;code&gt;{{ record.fieldName }}&lt;/code&gt; placeholders, which are replaced at send time with values from the triggering record.&lt;/p&gt;</description></item></channel></rss>