General
Configure workspace-level account defaults: company name, timezone, same-domain joining, and Save.
Use this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Learn the system by following the product states.
Use the screenshots as the primary map: start with the full context, trace the connected workflow, inspect the focused UI, then compare against the completed operating state.
Visible controlAccess or policyOperational effectUse this settings state to understand which workspace behavior, access rule, credential, usage signal, or data-model surface the control changes.
Summary
Configure workspace-level account defaults: company name, timezone, same-domain joining, and Save.
Concepts covered
Step breakdown
- Open GeneralStart in the General section of the Admin control center.
- Inspect the real controlsIdentify the visible fields, buttons, switches, tables, and menus before changing configuration.
- Connect the setting to operationsUnderstand which user access, customer memory, developer access, usage, billing, or data-model behavior this setting affects.
What this screen does
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 General as part of the Frontline Admin General operating loop: inspect the current product state, confirm the source context, and decide what should happen next.
The goal is not to memorize screens. The goal is to understand how the product surface supports repeatable work, AI assistance, and accountable handoff.
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.
Prefer narrow, inspectable setups over broad automation. Teammates should be able to explain why the system took an action from the visible product state.
Troubleshooting
If the result does not match expectation, check the source context first, then permissions, connected integrations, required fields, workflow logs, and any AI-generated output used by downstream steps.
When in doubt, compare the latest product state with the related record, activity, or workflow execution so debugging starts from evidence rather than guesswork.
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.