Settings
Configure workspace, team access, billing, domains, notifications, finance, apps, API, imports, and modules.
Settings control how the workspace behaves. Owners and admins should review settings before inviting the full team or sending public links to clients.
Treat settings as production configuration. A small change to modules, roles, mailboxes, payment gateways, domains, or templates can affect many users and customer-facing pages.
Workspace Settings
General settings control workspace identity, business details, modules, the General settings page, appearance, language, regional settings, translation overrides, SMTP sender settings, and profile information.
Access Control
Access control defines who can view or manage each module. If a user reports missing navigation or denied access, check module status first, then role permissions.
Billing
Billing settings show the current plan, subscription status, usage limits, and billing portal access. Usage limits can affect modules such as docs, files, calendar connections, and other plan-gated features.
Domains
Domain settings let a workspace use custom domains. Configure DNS records with your DNS provider, then verify the domain in Agiled. HTTPS availability depends on domain verification and certificate issuance.
Notifications
Notification settings control user preferences, notification channels, email templates, system emails, Slack delivery, and related communication behavior. SMTP sender settings are managed from Settings > General > SMTP when a workspace needs to send through a custom mail server.
Finance Settings
Finance settings control taxes, finance templates, payment gateways, number sequences, and finance defaults used by invoices, estimates, payments, recurring invoices, and credit notes.
Apps, Mailboxes, and API
Apps connect external providers. Mailboxes connect Gmail or Outlook for customer communication. API settings control API keys, public API access, and webhook configuration.
Imports
Import settings and import run history help teams move existing data into Agiled, review failures, and rerun corrected records.
Settings Review Order
For a new workspace:
- General workspace identity and regional settings.
- Modules and access control.
- CRM, HRM, finance, and time-tracking defaults.
- Mailboxes, calendars, payment gateways, and apps.
- Domains, public links, notifications, API, and webhooks.
For an active workspace, test one affected record or public page after changing settings instead of assuming the save action is enough.
Change Safety
For settings that affect customers or automation, make one change at a time and test the affected workflow. This matters for payment gateways, SMTP, finance templates, domains, modules, roles, API keys, webhooks, workflows, and connected apps.
Record who changed a critical setting and why. That context helps the team debug later if emails, invoices, public links, imports, or permissions behave differently.
Ongoing Admin Routine
Review settings monthly or after major team/process changes. Check inactive users, role assignments, enabled modules, billing usage, domains, notification channels, finance defaults, connected apps, API keys, webhooks, imports, and templates.
For each critical area, confirm there is an owner. Settings without ownership become hard to troubleshoot when a payment, email, public link, or automation starts failing.