Key Highlights
Motadata ServiceOps MSP Edition scopes each record to its company and secures all logins with platform-level controls, so requesters see only their own company's data and any access stays provable to an auditor.
Each child company gets its own Support Portal, with no path to another company's data.
A requester signing in sees only their company's requests.
Plus the ones they're personally involved in or that are unassigned.
Their company's knowledge base, and the announcements configured for their company.
The company boundary holds throughout the whole service lifecycle, extending well beyond the ticket list.
Associate companies with Request, Problem, Change, Release, Asset, and Project.
Plus User Survey, Reports, Dashboard, Automation, and Support Channels.
Per-company workflows, SLAs, and company-specific report generation.
The same company scope bounds CMDB records and API access, not only module records.
The same enforcement protects each company.
Two-factor authentication via email OTP or authenticator app.
2FA for all users, only requesters, or only technicians.
IP Address Restriction by range or comma-separated list, per user type.
A configurable password policy, session timeout, and concurrent-login control.
Attribute-based custom scopes control which companies each technician can view and update.
User roles, permissions, and reporting access are defined per company.
SSL encrypts data in transit between the application and the database.
Database replication supports disaster recovery for standalone and high-availability site configurations.
Privacy controls and audit trails activate from settings, so compliance is provable, not assumed.
Privacy Regulations to auto-mark PII fields.
PII fields: name, email, contact numbers, logon name, and profile image.
Capture user consent and turn on a PII Audit.
Configuration, Operation, Email, and Download Audits record who changed what.
Full audit trail of user sessions with login times, IP addresses, and activity history.
Intelligence
A managed service provider's reputation rests on a boundary the client can't see but trusts absolutely. Their tickets, assets, and knowledge stay theirs. One requester glimpsing another company's request is a breach of contract and confidence, not a cosmetic bug. An auditor or client security review asks a harder question than "is the data separated?" It asks whether that separation can be shown, with the controls proven to have been on. Lacking per-company scoping and a real audit trail, both answers are guesswork.
ServiceOps MSP Edition answers both. Company-scoped visibility keeps each client’s data siloed by design, and platform-level security controls plus audit logs make all access provable, backed by recorded evidence.
How It Works
Enable Managed Services Provider mode in the license.
Create each child company as a Company under Admin > Organization.
Custom fields extend the company record where needed.
Create and associate a Support Portal to each company, with its own branding and URL.
The portal displays that company's knowledge base and announcements.
Requesters signing in to a company's portal view only that company's requests.
Plus requests they are involved in or that are unassigned.
Cross-portal access:Technicians work between portals from the single Technician Portal, with reach set by their access.
Associate companies with Request, Problem, Change, Release, Asset, and Project.
Plus User Survey, Reports, Dashboard, Automation, and Support Channels.
Build per-company workflows, SLAs, and reports on top.
Apply platform-wide security under Admin > Organization > Security.
Two-factor authentication, IP Address Restriction, password policy, session timeout, and concurrent-login control.
Turn on Privacy Regulations under Admin > Organization > Privacy Settings.
Auto-mark PII fields, enforce user consent, and activate PII Audit (a one-time, permanent activation).
Read the audit trail under Security: Configuration, Operation, Email, Download, Scheduled Operation, and PII audits.
Plus a User Sessions audit trail.
Role-Based Value
The promise each contract makes is enforced by the platform: each company sees only its own requests, knowledge, and announcements.
The promise each contract makes is enforced by the platform: each company sees only its own requests, knowledge, and announcements.
The company boundary holds throughout the whole service lifecycle rather than only the ticket list, so isolation does not depend on process discipline.
The company boundary holds throughout the whole service lifecycle rather than only the ticket list, so isolation does not depend on process discipline.
Each child company has its own Support Portal with no path to another company's data, so working with clients cannot leak between them.
Each child company has its own Support Portal with no path to another company's data, so working with clients cannot leak between them.
Access is provable, configuration, operation, email, download, and PII audits make all access defensible in a client compliance review.
Access is provable, configuration, operation, email, download, and PII audits make all access defensible in a client compliance review.
From Visibility to Control
Client data stays siloed. Each company sees only its own requests, knowledge, and announcements: the isolation that earns client trust.
Access is auditable. Configuration, operation, email, download, and PII audits make any access provable for compliance reviews.
Privacy is configured, not bolted on. PII marking, user consent, and PII auditing activate from settings, supporting obligations under regulations such as GDPR.
Explore More