Settings

Settings controls how Auditmark is configured for your organization, plus a few preferences that are yours alone. Open it from the main navigation. It shows a grouped rail on the left with a search box at the top. Type in the search box to filter sections by name. Click any section in the rail to load it on the right. Most changes take effect as soon as you save or select a value.

Your name and theme live in Account, not here.

---

Organization group

General

This section sets the identity and primary contact for your workspace. It holds four controls.

To rename the organization, edit the Organization name field and click Save. The name appears across the admin interface.

To set the primary contact, pick any active admin from the Organization owner dropdown. The change saves as soon as you select a name.

To route report replies, type an address into Reply-to email for reports and tab out of the field. When Auditmark sends a report by email, replies go to this address. Leave it empty to fall back to the sender's address. If you type something that is not a valid email, Auditmark shows an error and does not save until you fix it or clear the field.

To set your logo, upload a PNG, JPEG, or WebP file up to 2 MB. The logo appears on forms and generated reports. Click Upload to pick a file. Once a logo is set, the button reads Replace, and a Remove button appears next to it. Removing asks you to confirm before the logo is deleted.

Localization

This section sets how dates, times, and weeks display throughout the organization. Every selection saves as soon as you make it.

Select a Region preset to set date format, time format, week start, and weekend days together. This is the fastest way to configure localization correctly.

Select a Timezone to control how timestamps display and are recorded across the organization.

Click Advanced overrides to expand per-setting controls that override the region preset:

The placeholder text on each override select shows the value derived from the current region. Setting an override replaces only that one value; the region preset supplies the rest.

Vertical

The vertical sets terminology and defaults for everyone in your organization. Changing it relabels the whole app for all users, so this section is shown in a warning-tinted card.

The current vertical is shown in the selector. To change it:

1. Click the selector to open the Change vertical dialog.
2. Review the available verticals. Each shows a name and description, and the current one is marked.
3. Select the vertical that fits your work.
4. Click Apply.

For background on what a vertical is and how it differs from a pricing tier, see Concepts.

---

Branding group

Report design

This section opens the report themes tool, where you manage color palettes, fonts, and PDF layout presets that apply to generated reports. It opens full-width with a Back to Settings link at the top. See Report design for the full reference.

---

People & access group

People & access

This section manages your organization's team members: invite new admins, view active and pending members, and adjust roles. See Team for the full reference.

---

Authoring defaults group

Field defaults

This section sets the configuration that new fields start with, per input type. Existing fields are not changed. To update fields already in a template, use the Apply field defaults action inside that template (see Templates).

Field types are grouped into Common and Advanced sections. Click any field type to expand its settings.

For each field type that captures an answer, you can set a Default required mode using a three-way toggle: No default, Required, or Optional. When set to Required or Optional, every new field of that type starts in that mode. Display-only field types, such as headings and dividers, have no required toggle.

For single-select and multi-select types, a Default response set picker lets you choose one of your response sets. New select fields of that type start with that set pre-assigned.

For other types, the expanded row shows the same per-type configuration you see in the template builder for that field type.

A field type shows a Customized badge when you have set at least one override. Click Reset to system default inside the expanded row to remove all overrides for that type.

When you finish editing, click Save field defaults. The button is enabled only when there are unsaved changes.

Template defaults

This section sets what every new template starts with: default Start fields, flow layout, and completion settings. Existing templates are not changed. To apply these defaults to a template you already have, use the Apply template defaults action inside that template (see Templates).

Three groups are available:

Default Start fields edits the intake fields captured before an inspection begins, using the same controls as the template builder's Start tab.

Default flow sets how the form is laid out and navigated on the inspector's device.

Default completion and access controls who can start an inspection and what happens to answers after submit. It covers correction mode, the sign-off requirement, the approval requirement, and whether inspectors can initiate an inspection themselves.

Click Save template defaults to apply changes. Click Reset to none to clear all defaults so new templates start with nothing pre-configured.

---

My preferences group

Notifications

This section sets which in-app notifications you receive. The setting is yours alone and does not affect other people in your organization. Each row has a switch; turn one off to stop receiving that kind of notification, and the change saves as soon as you toggle it.

---

Developer group

API keys

This section is where you create and revoke API keys. An API key lets an external system act on your organization's behalf through the Auditmark API. Treat it like a password: anyone who holds a key can act as your organization.

For the full authentication protocol, see Authentication.

The keys table shows one row per key:

To create a key:

1. Click Create key.
2. Enter a Name.
3. Choose Access: Read only, or Read & write.
4. Choose Expires: Never, 30 days, 90 days, or 365 days.
5. Click Create.
6. Copy the key. It is shown once and cannot be retrieved again. Use the Copy button, then close the dialog only after you have it.

To revoke a key, click Revoke on any active key's row. A confirmation dialog warns that apps using the key stop working immediately and that revocation cannot be undone. Confirm to revoke. Revoked keys stay in the table with a Revoked status, and the Revoke button no longer appears on them.

Webhooks

This section is where you register endpoints that Auditmark notifies in real time when events happen in your organization. Auditmark sends a signed HTTP POST to each endpoint URL, so you can verify every request came from your organization.

For the full protocol including payload shapes, signature verification, and available event types, see Webhooks.

When you have no endpoints yet, this section shows an empty state with an Add endpoint button. Once you add one, the button moves to the top right.

Adding an endpoint

1. Click Add endpoint.
2. Enter the Endpoint URL. It must be a public HTTPS URL.
3. Optionally add a Description to identify the endpoint.
4. Select the Events to subscribe to. Check individual events, or use Select all to subscribe to everything (it switches to Clear all once all are selected). The form shows a running count of selected events, and at least one event is required.
5. Leave Active on to start delivering events right away, or turn it off to add the endpoint without sending yet.
6. Click Add endpoint.
7. Copy the signing secret shown after creation. It is shown once. Use Reveal to read it and Copy to copy it, then store it in your system to verify incoming requests. Click Done to close.

Signing secrets

Every delivery includes an X-Auditmark-Signature-256 header: sha256= plus the HMAC-SHA256 of the raw request body, keyed by the signing secret. This follows the same scheme as GitHub webhooks and verifies in one step on Make, Zapier, n8n, and any standard receiver. A replay-protected X-Auditmark-Signature header is also sent. The secret panel includes a How to verify deliveries section with a short code sample.

To rotate the secret, select Regenerate secret from the endpoint's action menu and confirm. The current secret stops working immediately, so update any system that verifies signatures. The new secret is shown once in the same Reveal-and-Copy panel.

Managing endpoints

Each endpoint row shows a status dot, its URL, its subscribed events (up to three, with a count for the rest), an optional description, and the date it was added. An inactive endpoint shows a Disabled badge, and if it was turned off for a reason that reason appears beneath the row.

Each row has a Send test button plus a More actions menu:

Auto-disable

If an endpoint returns repeated failures, Auditmark disables it automatically. The endpoint row then shows a Disabled badge with the reason. Re-enable it by editing the endpoint and turning Active back on after you fix the receiving system.

Delivery log and replay

Open View deliveries to see recent attempts for an endpoint. The table lists each delivery's status (Pending, Delivered, or Failed), event type, HTTP response code, number of attempts, latency, and creation time. Click Replay on any row to re-send that delivery without waiting for the next event; Auditmark confirms the replay was queued.