Administration & Security
MeraUdyog Administration gives a 50-person business the access governance normally reserved for 500-person enterprises: role-based access control, field-level rules, branch and center hierarchy configuration, user provisioning, audit trail and custom field and module configuration.
Why it matters
Governance is enforced uniformly across every module, which is why a branch manager's visibility is consistent whether they are looking at leads, attendance, payroll cost or support tickets. Sensitive fields like salary can be restricted to HR alone.
Because Administration & Security shares one data core with every other module, the work it produces is immediately usable everywhere else: scoped by branch, center and owner, visible in Analytics, and available to Workflow Automation as a trigger.
| Role | Data scope | Can view salary | Can delete leads |
|---|---|---|---|
| Founder / CEO | All branches | Yes | Yes |
| Regional Manager | Assigned region | No | Yes |
| Branch Manager | Own branch only | No | On request |
| HR Manager | All branches (HR) | Yes | No |
| Telecaller | Own leads only | No | No |
Every change is attributable in the audit trail: actor, object, field, old value, new value, timestamp.
Everything in Administration & Security, by sub-category.
Access governance
Organisational hierarchy
Platform administration
What each capability does. And the problem it removes.
Features are only worth listing if the business problem behind them is named.
| Feature | What it does | Problem solved | Business benefit |
|---|---|---|---|
| Role-Based Access Control | Assigns permissions through predefined roles | Ad hoc permissioning is inconsistent and risky | A new telecaller gets the right access instantly |
| Permission Management | Fine-tunes individual and role-level access | One-size-fits-all access fits no business | Only Finance can view invoices |
| Field-Level Access Rules | Restricts visibility of specific data fields | Sensitive fields like salary are over-exposed | Data privacy at a granular level |
| Branch Management | Configures and governs branch entities | No structured way to represent multiple locations | A new branch onboards with its own team and data scope |
| Center Management | Configures and governs center entities | Multi-center institutes lack real segregation | A new center gets its own lead pool |
| Owner / Team Hierarchy | Defines reporting and ownership structure | Unclear escalation and incorrect data rollup | A regional manager sees every branch below them |
| Lead Sharing Rules | Defines who can view or edit shared records across teams | Cross-team leads get lost or duplicated | Controlled collaboration without data leakage |
| User Provisioning & Deactivation | Adds and removes system users and access | Former employees retain system access | Access revoked on the last day, not weeks later |
| Audit Trail / System Logs | Records who did what and when | No accountability trail for data changes | Compliance-ready traceability |
| Custom Field & Module Configuration | Lets admins tailor fields and modules | Rigid systems do not fit unique processes | Industry-specific fields without a dev ticket |
IT / Admin Manager
Often the only person responsible for access, configuration and audit readiness.
- Pain today
- Manual, error-prone user and access management; no audit trail when something goes wrong.
- What they want
- Centralised, auditable administration that scales without headcount.
- Features that deliver it
- RBAC, Field-Level Access Rules, Audit Trail, User Provisioning
- Business value
- Lower security risk and materially easier compliance audits.
Use cases
Three ways teams put Administration & Security to work in week one.
Role-based onboarding of new users
A new telecaller is assigned the Telecaller role and inherits exactly the right permissions: no per-user permission setting, no over-privileged accounts.
Branch and center hierarchy configuration
Adding a location is a configuration step, not a project: the new unit gets its own data scope, team and rollup into the regional view.
Audit trail for an unauthorised record change
Every change is attributable, which turns “who deleted this lead” from an argument into a lookup.
Industries where Administration & Security carries the most weight.
Administration & Security FAQs
Three levels. Role-based access control bundles permissions into roles for fast, consistent onboarding. Permission management fine-tunes at role or individual level. Field-level access rules restrict specific fields. So only HR sees salary on an employee profile. All three are enforced uniformly across every module.
Yes, and consistently so. Because branch, center and owner are core primitives, a branch manager's scope applies identically to leads, attendance, payroll cost and support tickets. Lead sharing rules then allow controlled cross-team collaboration. For example HQ sharing a lead with only the nearest branch. Without opening up the wider data set.
SSO (Google and Microsoft) and MFA are on our near-term roadmap, alongside formal security certifications such as ISO 27001 and SOC 2, and scoped per-assistant permissions for MCP access. Role-based access control, permission management, field-level rules and a full audit trail are available today. If certification timelines are part of your procurement process, raise it with our team early and we will share current status.
Start with Administration & Security. Add the rest when you are ready.
Same data core, no migration, no implementation partner. Most teams are live within days.
No credit card required · Live in days, not months · 10,000+ leads processed monthly