Workspace Settings guide

Workspace Settings controls shared policy and configuration. It is separate from Account Settings, which controls the signed in user's profile, preferences, personal security, personal integrations, and AI usage.

Open Settings as a Super Admin or Manager. Access can also be delegated narrowly for supported Access Rights administration. Settings for one module can also be reached from that module, for example Inventory → Settings for the supply chain menu switches.

#Search and navigation

The centralized shell contains these domains:

Use Search workspace settings to find a setting by label or description. Search results respect your role, modules, and platform scope, so unavailable settings are not advertised.

Use arrow keys to move through domain tabs. Home selects the first visible tab and End selects the last.

#General

Company controls the core workspace name used on supported documents and reports.

Branding controls application identity, logos, colors, and supported email presentation.

Localization holds the fiscal country configuration. Agaro serves the United States: finance localization installs the United States chart, tax, and statutory configuration.

#Plan and Billing

Review plan name, status, period, payment method, and installed modules. The detailed Subscription page is Super Admin controlled and opens hosted provider checkout or billing portal actions.

Add ons are managed through Subscription. The Apps catalog remains the operational catalog for adding and removing modules. See Apps catalog and modules.

#Finance

The Finance domain includes:

• Workspace tax defaults and jurisdiction rates
• Expense, income, and payment method lists
• Fiscal year
• Fiscal localization
• Cash rounding
• Exchange rates
• Invoice and vendor bill sequences
• Payment terms
• Invoice terms
• Invoicing options
• Discount accounts

Availability depends on installed modules and role. Configure numbering before production documents are issued. Changing a sequence does not rewrite existing document numbers.

The customer payment provider under Settings → Payments is restricted to Super Admin and belongs to tenant customer payments, not the agaro platform subscription.

#Document layout

The Document layout tab, at /settings?tab=document-layout, controls how invoices, quotes, receipts, statements, and packing slips print: the letterhead, the logo and its size and position, the style and font, the colors, the spacing, the invoice table columns, the document text, and the footer, with a live preview beside the controls. It needs the Invoices module and is for SUPER_ADMIN and MANAGER. See Document layout.

#Communications

Inbound Email shows the workspace BCC dropbox and unmatched queue.

Digest Emails manages supported scheduled workspace KPI digests.

Email Templates manages reusable workspace content when Marketing is available.

Authentication Emails controls safe invitation, activation, reset, verification, and login alert content.

Delivery Diagnostics shows bounce, retry, and delivery health evidence. Use it before resending a business communication manually.

#Integrations

Workspace integrations store shared organization credentials and provider application configuration. Shipping carriers holds the FedEx, UPS, USPS, DHL Express, and Shippo connections, the same ones shown on the Delivery Carriers page. Personal Gmail and Google Calendar connections belong under Account Settings.

See Workspace and personal integrations.

#Devices

Barcode settings include software activation, nomenclature, readers, rules, hardware, and troubleshooting when Inventory is available. Printers can be registered and assigned for supported reporting paths.

Device configuration does not replace network security. Use trusted device addresses and restrict administrative access.

#Security

The Security tab has the Security Policy, Access Rights, Single Sign-On, Settings Audit, and Workspace Privacy sections. Review workspace two factor policy, Access Rights, settings activity, and privacy requests. Only a Super Admin can change the workspace two factor policy, although a Manager can review it.

Access Rights can control groups, apps, data model actions, record scope, rules, fields, and menus. Test a new group with a nonadministrator account before broad assignment.

#Product improvement

The Security tab has a Product improvement card, in the Workspace Privacy section. It is one decision for the whole workspace, and only a Super Admin can change it. Everyone else sees the card with the switch disabled and the line "Only a Super Admin can change this."

The card reads:

Share how your team uses Agaro, including page views, clicks and the steps people take in the product, so we can see what's confusing and make it better. Passwords, payment details and anything typed into fields are hidden and never collected.

So what is collected is how your team uses the product: page views, clicks, and the steps people take. What is always hidden, and never collected, is passwords, payment details, and anything typed into fields. Learn more opens the privacy policy.

The switch is on when the workspace shares, and sharing is on by default. Turning it off:

• stops capture in your current browser at once, before the save finishes;
• is saved for the whole workspace and written to the activity log;
• also asks that each member's name, email, and workspace details be removed from the analytics provider.

Turning it on waits for the save, and the next page load decides, because a person's own earlier opt out can still keep capture off for them. Your browser's Do Not Track preference also stops capture in that browser, and the card says so when it is on. If the choice cannot be read, the card asks you to reload the page, and a save that fails offers Retry.

This card replaces the two switches that each person used to have in their own Security and Privacy settings, for product analytics and for recording their screen.

#AI

The AI tab has three sections: Budget and usage, Configuration, and Workspace knowledge. The default model is no longer a workspace setting.

Configuration holds the App Builder switches, which an administrator sets for the whole workspace:

• Web search for the App Builder lets the builder search the web for current information while it works. It is on by default. When it is off, no build searches the web, whatever a project's own settings say.
• Multi agent builds splits large builds between several agents that work at the same time. When it is off, every build runs as a single pass.

Changes take effect on the next message or build. See Build a website with App Builder.

Data and Privacy has one switch, Improve the model for everyone. It reads: "Let Agaro use this workspace's AI prompts and answers to make Agaro Agent better for everyone who uses it. Your AI data improves the model for everyone while this is on." It is a workspace decision that applies to everyone in the workspace, and only a Super Admin can change it. Everyone else sees "Only a Super Admin can change this."

While it is on, prompts, answers, and tool data are sent to the product analytics provider, PostHog, after common credential, token, card, and account number formats are redacted. Other sensitive text in a prompt can still be included. Zero Data Retention covers the AI model providers, not product analytics. When it is off, AI analytics keep only usage and cost metrics, without prompt or answer text. Turning it off does not delete the conversation history needed to provide your service. A product analytics opt out stops AI analytics for all of that person's activity, and Do Not Track stops them for requests from that browser. See Product improvement. This section is shown where the Agaro Agent is available.

Budget and usage is the one place for AI and App Builder credits, what the team used this month, and each member's budget.

Workspace knowledge shows what your team has shared with Agaro Agent, and needs the Knowledge Base app.

API keys and AI assistant connections are not in this tab. They have their own tab, described next.

Platform AI configuration is visible only in the canonical platform owner workspace.

#API and MCP

The API and MCP tab, at /settings?tab=api-mcp, is for a Super Admin only, because API keys can carry owner authority. It needs the AI Assistant capability. It has two blocks, in this order.

Connect an AI assistant (MCP) lets Claude, ChatGPT, Cursor, or another AI app work in Agaro as the person who connects it. It shows the Connector URL with a copy button, the steps for each AI app, and a Connected apps list of the AI apps people in the workspace approved, each with Disconnect. No key is needed: you add the URL in the AI app and sign in with Agaro. See Connect an AI assistant (MCP).

API keys is for your own code and systems that call the Agaro REST API. You create a key that acts as a chosen Super Admin or Manager, and you can rotate or revoke it. See API overview and request format.

API and MCP access is included in Scale and Enterprise with no seat to buy. A trial, the Free plan, and Essentials do not include it. On a workspace that has not paid, the tab asks you to subscribe, and existing keys stay listed as inactive until the workspace pays.

#Save and audit behavior

Settings forms use explicit Save actions and display validation or read only errors. Successful supported settings changes are recorded in the Settings Audit or broader activity system.

Do not change several unrelated settings at once during an incident. Make one bounded change, verify the result, and preserve the audit trail.

#Troubleshooting

#A settings domain is missing

Visibility depends on role, installed modules, access rights, and platform owner scope. Search does not show settings you cannot open.

#Save returns read only

Restore the workspace subscription under Subscription. Personal profile reads can remain available while workspace mutations are blocked.

#A setting moved

Use centralized search. Older routes redirect to the current workspace domain or operational module where possible.

#A Manager can view but cannot change a setting

Some sensitive controls, including platform billing, Stripe customer payments, API keys, and two factor policy changes, require Super Admin.