Workspace settings
Configure the global defaults that every Nomow feature and integration inherits.
Workspace settings control the baseline behavior of the whole account — locale, email delivery, activity types, and which team member owns unclaimed submissions. Only owners and admins can access this screen.
Go to Settings in the sidebar (Settings section, bottom of the nav).
General
| Field | Purpose |
|---|---|
| Workspace name | Displayed in the sidebar header and in email footers |
| Timezone | Used when displaying timestamps across the app and for scheduling booking availability |
| Default currency | The currency label used in deal values and pipeline KPIs |
| Default language | Sets the locale for system-generated microcopy on public forms and booking pages |
The Email tab controls how Nomow sends transactional messages (form notification emails, booking confirmations, and invite emails).
Choose your sending method:
- Brevo — paste your Brevo API key and select the verified sender. Recommended for most workspaces.
- SMTP — enter host, port, username, and password for any standard SMTP server.
- Amazon SES — enter your SES region, access key, and secret key.
Regardless of the method, set:
| Field | Purpose |
|---|---|
| From name | The display name recipients see in their inbox |
| From address | Must be verified with your chosen sending service |
| Reply-to | Where replies go; can differ from the from address |
| Default footer | Plain-text footer appended to every outgoing email |
Activities
The Activities tab defines what kinds of activities your team logs on deals and contacts.
- Built-in types: Call, Meeting, Task.
- Click Add type to create custom types (e.g., "Demo", "Site visit").
- For each type, set the default duration and default reminder — these pre-fill the activity modal so reps log faster.
Activities are shared across the whole workspace. Deleting a type does not delete existing logged activities of that type.
Default owner
Every form submission and booking that arrives without a signed-in user context is attributed to the default owner. This controls which user's queue anonymous submissions land in.
Next steps
After configuring the workspace, invite your team and set up integrations.
Was this article helpful?