English
Frontline Admin · General · Interactive walkthrough

General

Configure workspace-level account defaults: company name, timezone, same-domain joining, and Save.

Interactive walkthrough5 min
General account settings with company name, timezone, same-domain joining, and Save
Screen guideGeneral

Check which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.

What General settings are for

General manages account-level settings and preferences. The real screen includes Company Name, Time Zone, a same-domain joining policy, and Save.

These are workspace defaults, not agent prompts. They define how the account identifies itself and how user access behaves at the organization boundary.

What each control changes

Company Name controls the workspace account name. Time Zone controls scheduling context and account time interpretation. Allow users with the same email domain to join this account controls whether same-domain teammates can enter the workspace automatically. Save persists the configuration.

Review timezone before configuring meeting prep, follow-up windows, billing review, usage analysis, or scheduled workflows.

Operational outcome

General settings make the workspace coherent: the right company name, correct time context, and a deliberate account-join policy.

Operational playbook

Use this page to identify what the control changes, which source context it uses, who owns the result, and where to verify it.

Use the page to identify the trigger, source data, owner, visible result, and review point before changing production behavior.

Best practices

Start with the operational job before changing configuration. Name the owner, define the trigger or source context, and decide how the result should be reviewed.

Start with one workflow, message, record update, or Max task before expanding. The team should know what changed, who owns it, and how to pause or adjust it.

Troubleshooting

If the result is wrong, debug in this order: source data, permissions, connected tools, required fields, workflow logs, then any generated output used later.

When debugging, open the related CRM record, Max activity, workflow run, or integration log first. Fix the source data or rule before adding more automation.

FAQs

What does General control?

Configure workspace-level account defaults: company name, timezone, same-domain joining, and Save.

Who should use this page?

Workspace admins, implementation owners, and operators responsible for configuring access, account behavior, developer integrations, or the data model.

How should this page fit into onboarding?

Use it to understand the product surface, inspect real UI states, and connect the concept to daily operating workflows before configuring production behavior.

What should I verify before using this in production?

Verify ownership, permissions, source context, failure behavior, and the handoff path so teammates can trust what the system does next.