Settings and roles
Settings has two scopes. Account-wide sections apply to everything; per-site sections (brand, working hours, module toggles, channels, widget) are edited for one site at a time, chosen in the site picker. Owners and Admins manage settings; some sections are Owner-only and carry an Owner badge.
Account
Section titled “Account”Account name, slug (read-only after creation; it is your help.rolchat.com/{slug} path), default dashboard language and date format, account time zone. Legal entity: legal name, region (EU, US, UK, CA, other), tax ID and postal address. The postal address is required before any campaign can be sent, because it is appended to every marketing e-mail.
Transfer ownership is a wizard for the Owner: pick an Admin, they accept within 7 days, the change is audited and can be undone within 24 hours. Delete account (Owner, password plus two-factor plus typing DELETE) schedules a purge after a 90-day grace period during which everything is read-only and the deletion can be cancelled.
Each site has a name, domain, brand (logo, favicon, accent colour, default language, time zone, date format) and working hours: a weekly grid with several segments per day, holidays, and per-integration behaviour outside hours (auto-reply text, hold or assign anyway, pause SLA timers, voicemail or an IVR branch, defer marketing sends).
Members, invitations, teams and roles.
| Role | Scope |
|---|---|
| Owner | Everything. Only role that manages billing, white-label, deletes the account or transfers ownership. |
| Admin | Everything except the Owner-only items. |
| Manager | All conversations, tickets and reports of their teams; assign work; publish articles; supervise calls. No system settings. |
| Agent | Own conversations and tickets; notes, tags, drafts. |
Module visibility by role: Agents do not see Visitors (by default), Marketing, Automation, Reports or Settings; Managers additionally do not see Automation or Settings.
Custom roles start from a system role as a template and add or remove individual permissions in a grid grouped by module. The server enforces two ceilings: a custom role can only include permissions an Admin could hold (never Owner-only or staff-only ones), and only permissions the author holds. Nobody can edit or delete their own role, and every role change is audited with the difference.
Permissions can carry a scope: conversations.read:own, :team or :all.
Modules
Section titled “Modules”Switch modules on or off per site: Chats, Visitors (with who can see), Tickets, Phone, Marketing, Knowledge base, Automation, Reports, Privacy. Switching off hides the module and keeps its data.
Security
Section titled “Security”A hub with a security score and cards: Two-factor authentication (optional, mandatory for Owner and Admin, or mandatory for all; TOTP apps, with backup codes), Single sign-on (Google Workspace, Apple; off, SSO plus password, or SSO enforced with one break-glass account; available on every plan; SAML 2.0 is planned and not available yet), IP restrictions (CIDR allow-list, per role), Sessions (idle timeout 120 minutes and hard limit 30 days by default; a device list with forced sign-out), Password policy (12 characters minimum, no forced rotation, breach check), and the Activity log of security events with JSON and CSV export. Members who sign in through SSO are not challenged for a second factor again.
Notifications
Section titled “Notifications”An account policy sets which events notify whom and on which channel (in-app, e-mail, push, browser), with forced entries that members cannot switch off, quiet hours and digests. Every member overrides the rest in their profile.
Billing (Owner)
Section titled “Billing (Owner)”Plan, seats, invoices, payment method, balance, VAT details, trial state, add-ons such as telephony and a consent licence for each site that uses the Privacy module ($5 a month per site; no site is included in a plan). Downgrades take effect at the end of the period.
Translations
Section titled “Translations”Per-account overrides of interface strings in any of the 40 languages, drafted and published separately, so that your team can call things what they call them.
Plugins and API keys
Section titled “Plugins and API keys”Connected plugins, the catalogue and RolChat API keys live under Settings → Plugins. See Plugins and Authentication.