Account settings and security
| Item | Details |
|—|—|
| Who it is for | Administrators |
| Menu location | Settings → Account settings; Settings → Security |
| Plan dependency | Enterprise sign-in such as SAML requires enablement |
Manage the workspace name, language, time zone, privacy-related switches and enterprise single sign-on. Personal passwords and MFA are under Profile and notifications.
—
1. Account settings (general)
Typically includes:
| Item | Description |
|—|—|
| Workspace name | Shown in the sidebar, email subjects, etc. |
| Default language | Used by members who have not chosen a personal language |
| Time zone | Defines the “day” for reports, business hours and delayed automation |
| Workspace ID | For support or API use — not a password |
| IP geolocation | Whether to tag contacts by IP region; privacy-sensitive, often off by default |
| Request workspace deletion | Irreversible — see Billing |
Changing time zone does not rewrite stored historical timestamps; it only affects future day-based stats and business-hours logic. Prefer a quiet period and tell agents when you switch.
Auto-resolve and required fields live under Conversation workflows; some builds may also show those blocks on the account page.
—
2. Security (SAML, etc.)
If SAML is enabled:
-
Create an application in your identity provider (for example Azure AD, Okta).
-
Paste Chatips’ ACS URL / Entity ID into the IdP.
-
Paste the IdP metadata / SSO URL / certificate back into Chatips.
-
Walk through sign-in with a test user.
-
Confirm that if SSO fails, at least one administrator can still use a password entry (per whether you enforce SSO).
Emails must match the IdP assertion. Test in a maintenance window before changing domains or certificates.
Without SAML this page may only show an explanation or upgrade prompt. If Google sign-in is enabled by the platform, members can use Google on the sign-in page without per-user setup here.
—
3. Recommendations
– Turn on MFA for members in production (enforce in profile or by policy).
– Do not lend administrator accounts to contractors — use custom roles.
– Review sensitive changes in Audit logs.
—