Admin Account Setup
What this domain covers
Admin Account Setup tests whether you can stand up a Freshdesk account correctly: company profile, subdomain, time zone, plan entitlements, admin ownership, and the account-level security baseline that every later configuration inherits.
Core rules and concepts
- The account URL is the subdomain chosen at signup (for example, acme.freshdesk.com). Treat it as a permanent identifier: changing it later breaks bookmarks, email links, portal URLs, and integrations.
- Company Profile stores account name, logo, locale, time zone, date/time format, and default language. Time zone is operational, not cosmetic: business hours, SLA timers, Supervisor rules, and report buckets all evaluate against it.
- Plan entitlements decide which admin features exist. Custom roles, sandbox, multiple portals, advanced SLA, skill-based routing, and audit-log retention vary by plan. Confirm entitlements before designing a workflow that depends on them.
- Account Admins have full configuration rights. Keep at least two active Account Admins, use named accounts rather than shared logins, and document who owns billing and security settings.
- Account-level security includes password policy, two-factor authentication, SAML or Google SSO, and session controls. Set these during setup, not after agents are invited.
- Decide the support address and portal domain early. Email verification and DNS ownership affect deliverability and portal branding, and they take longer than most admins expect.
Worked example
A company opens support for London and New York. The admin sets the account time zone to the primary support hub, creates business-hour sets for each region, then builds SLA policies that reference those calendars. If the time zone stayed at the signup default, an 8-business-hour SLA would be measured against the wrong working day, and Friday-evening tickets would appear to breach early. The reasoning is simple: every timed feature derives from account time zone and business-hour sets, so configure them before rules, not after.
Traps that cost marks
- Changing the subdomain after agents, portal links, and integrations exist.
- Assuming a feature is included without checking the plan.
- Leaving one Account Admin and no recovery path.
- Setting locale or time zone after SLA and automation testing, then wondering why timers shifted.
- Inviting agents before roles and groups are designed, creating cleanup work.