Admin / Settings

What this page is for

Admin is the control plane for business profile, security, staff access, CRM masters, scheduling masters, integrations, commerce masters, communications, reports, GST/accounting, waivers, trials, forms, retail masters, and system notifications.

Who should use it

Owner, manager, platform admin

Where to find it

/admin

Before you start

• Admin settings flow completion gate: Admin setup is complete only when every live workflow has a matching configured master, provider, permission, and tested operational path.
• Settings catalog is grouped into Business Setup, Plans & Payments, Schedule & Attendance, People & CRM, Communications, Migration & Reports, and Advanced / Later.
• The simplified Admin categories shown in Staff app are Business Setup, Plans & Payments, Schedule & Attendance, People & CRM, Communications, Migration & Reports, Advanced / Later, and Integration.
• Business Setup owns branch settings, company info, tenants, field configurations, staff, permission templates, password policy, IP policy, audit trail, safe mode, and announcements.
• Plans & Payments owns plans, add-ons, charges, payment modes, taxes, GST invoice settings, commerce workspace, Razorpay, POS terminals, freeze reasons, and coupons.
• Schedule & Attendance owns class categories, appointment categories, rooms, trial definitions, tags, attendance automation, staff availability, and biometric devices.
• People & CRM owns task taxonomy, lead sources and channels, CRM board configuration, opportunity settings, document folders, form templates, waivers, and organizations.
• Communications owns email, SMS, WhatsApp, push templates, provider accounts, sender accounts, notification preferences, and provider-specific setup.
• Integration owns Razorpay Setting, POS Terminal Setting, Email Setting, MSG91 Setting, WhatsApp Setting, Facebook Leads Setting, and Biometric Setting.
• Configure branch/business identity before invoice, signup, and communication launch.
• Configure provider-specific settings from the dedicated cards: Razorpay, MSG91, Email, WhatsApp, Facebook Leads, POS terminal, biometric/access device, and other channel accounts.
• Admin provider setup uses dedicated Razorpay, MSG91, Email, WhatsApp, Facebook Leads, POS terminal, and Biometric cards instead of one generic provider dropdown.
• Admin provider setup uses dedicated Razorpay, MSG91, Email, WhatsApp, POS terminal, and Biometric cards instead of one generic provider dropdown.
• Gateway/device onboarding checklist for terminal and provider readiness must be completed before front desk can use hosted checkout, payment links, terminal collection, WhatsApp/SMS/email sending, Facebook lead sync, or biometric gate actions.
• Razorpay setup drawer fields are Account name, Merchant reference, Webhook secret, Key ID, Key secret, Test mode, Checkout, Payment links, Mandates, and Refunds.
• Razorpay setup requires provider, account name, merchant reference, key ID, key secret, webhook secret, test mode, checkout, payment links, mandates, and refunds.
• Channel provider setup selects channel type first, then limits provider choices to MSG91 or Exotel for SMS, Amazon SES or SMTP for Email, Meta WhatsApp for WhatsApp, and Facebook Leads for lead capture.
• Channel provider setup selects channel type first, then limits provider choices to MSG91 for SMS, Amazon SES or SMTP for Email, and Meta WhatsApp for WhatsApp.
• Channel provider drawer fields are Channel type, Provider, Account name, external account id label for that provider, credential/token field, and Safe/fake provider mode.
• Commerce device drawer fields are Location, Linked Razorpay account, Type, Provider, Name, Code, provider-specific external device id, and Serial number.
• Sender accounts must link to a provider account before templates, campaigns, Inbox, or profile activity messages can send.
• Sender account fields are Provider account, Channel, Label, Sender value, and Default sender.
• Message template fields are Channel, Event key, Sender account, Provider account, External template ID, Name, Subject template, Body template, and Description.
• Payment mode category derives behavior for offline manual, online gateway, terminal device, or internal credit and hides raw provider flags from staff.
• Offline payment method fields are Name, Code, Description, and Method type. Method type options shown in the drawer are Offline manual and Internal credit.
• Tax group setup records Name, Code, Description, Tax inclusive pricing, and Rate %.
• Tax group setup records code, name, inclusive pricing, tax line code, tax line name, rate percent, effective from, and optional effective to.
• Branch settings control quick barcode check-in, auto check-in for class and appointment, backdated billing days, future subscription start limit, retry frequency, dunning outcomes, and invoice title.
• Security settings control password minimum length, lowercase, uppercase, number or symbol, reset interval, IP policy mode, centre CIDRs, and staff CIDRs.
• Staff creation captures full name, email, phone, numeric employee ID, designation, default gym, grace late minutes, one role template, access scope, gym access, attendance enabled, roster notes, and weekly working days.
• Staff table columns are Staff name, Email, Phone, Employee ID, Designation, Role Template, Joined date, and Actions. Actions include editing staff details, role template, roster timing, invite links, and delete/terminate when the actor is not deleting their own active profile.
• Creating staff can generate an invite link. The latest invite link must contain the secure token before copying; regenerate if the link is missing the token.
• Staff invitation acceptance fields are Locale, Timezone, Create password, and Confirm password. Password must satisfy the current password policy and the invite must still be pending and unexpired.
• Deleting a staff profile is a terminate/revoke workflow, not a hard data erase. It revokes permissions, gym access, pending invitations, and active brand access where applicable.
• Permission Template fields are Code, Name, Description, and Permission keys. Save a template only after checking the pages/actions that should be visible for that role.
• Password Settings fields are Minimum length, Require lowercase, Require uppercase, Require number or symbol, Reset interval days, IP policy mode, Centre IP CIDRs, and Staff IP CIDRs.
• IP policy should be rolled out in audit-first or allowlist-tested form before enforcement, otherwise staff may be locked out from legitimate gym networks.
• Announcements & Safe Mode is one operational-control setting: Safe Mode suppresses risky outbound/provider actions, while announcements tell staff what is changing and when.
• Safe Mode actions are Enable and Disable. Use provider-specific test mode plus Safe Mode when testing payments, campaigns, automations, message providers, terminal devices, access devices, or worker jobs.
• Announcement fields are Title, Body, Severity, Show from, Show until, Audience targeting, Target gyms, Target permission templates, Target staff, Pinned, Require acknowledgement, and Publish now. Show from and Show until control the visible date window for staff.
• Support impersonation is time-limited, audited, and support-only. It should be used only with a support reason and ended after the support task is complete.
• Class category fields include Category name, Code, Duration minutes, Cancellation cutoff, eligibility, color, booking opening minutes, level, description, tags, things to carry, class logo, restrict sessions per user, accessible on member app, mark trainer busy, and room mandatory.
• Appointment category fields include Category name, Code, Duration minutes, Cancellation cutoff, eligibility, color, description, tags, things to carry, accessible on member app, mark trainer busy, and room mandatory.
• Class category and appointment category setup control duration, cancellation cutoff, trainer requirement, room requirement, eligibility behavior, trial acceptance, levels, and subtypes.
• Room fields are Location, Room name, Code, and Capacity.
• Trial definition setup controls code, name, trial type, max validity days, max sessions, and online signup availability.
• Profile form templates define code, title, description, status, and pipe-delimited fields as key, label, type, required, and options.
• Email provider readiness means Amazon SES or SMTP is saved, verified, healthy, and connected to sender/template setup before email buttons are used.
• WhatsApp provider readiness means Meta WhatsApp business account, phone identity, credential reference, and template sync are configured before WhatsApp buttons are used.
• Use allowed gender, source, channel, task type, board/stage, and field configuration masters to keep front-desk forms simple.
• Only trusted staff should manage integrations, tax, invoice sequence, security, permission templates, and credit-note rules.

Daily workflow

• Before first gym launch: configure brand profile, location, GST, invoice sequence, security, staff, permissions, CRM masters, scheduling masters, payment modes, gateway/devices, templates, and reports.
• For integrations, save provider account first, verify/sync it, create sender/device mapping, test a real low-risk workflow, and only then train staff to use that button.
• During operations: verify provider health, update masters, manage staff invitations, run imports, and audit sensitive controls.

Watch out

• Changing tax, invoice, gateway, or permission settings after go-live can affect live workflows. Make changes deliberately and verify with a test transaction.
• Admin changes that touch providers, tax, invoice identity, permissions, access devices, or billing rules need owner approval and a test workflow before go-live.

Related help

• Use the left menu to open related pages in Integrations.
• Use Ask Docs for questions that are already covered in this public documentation.